Issue with websubmit_engine (when mbpages>1)

2012-10-22 Thread Theodoros Theodoropoulos

Hello everyone,

When submitting using the web forms and only if a document has more than 
1 page, when you navigate from one page to another:


If an element already has a value[*] in pg1 and you edit it, then go to 
pg2, everything is OK :)
If an element already has a value[*] in pg1 and you DELETE THE VALUE 
COMPLETELY, then go to pg2, and then BACK to pg1, you see the old value!
This means that the FILE in the disk that corresponds to this element is 
NOT updated IF the new value is "" (although the system checks of the 
page see the 'new', empty value).


This results in users not being able to 'empty' old values when moving 
from one page to another. One can only change them into something else!


I can verify that it appears in a snapshot of master branch taken from 
git 3 weeks ago, but i believe it appears in earlier/later releases. Can 
you verify it? If yes, I think it's a bit important and needs fixing...


Best regards,
Theodoros Theodoropoulos


[*] either by continuing a previously-incomplete submission, or by 
entering a value, going to another page and then back


Typo in bibconvert help file

2012-10-22 Thread Theodoros Theodoropoulos

Hello everyone,

I just found a typo in the bibconvert help file (-h) that seems important...

One reads,
[...]
 -C_s_,  alternative to -c when config split to 
several files, _*target*_
 -C_t_,  alternative to -c when config split to 
several files, _*source*_


Where i believe the last two entries should probably be:
 -C*s*,  alternative to -c when config split to 
several files,*source***
 -C*t*,  alternative to -c when config split to 
several files,**target*

*
because the description seems more fit to the switches...

It exists in all branches (master,maint, etc) and probably even in old 
releases.


Best regards,
Theodoros


ps. Apologies if this was the intended use of switches/description. It 
just seemed odd :)