saving custom fields when exiting metadata page

Bug #899836 reported by Netsaver Paul on 2011-12-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Undecided
Unassigned

Bug Description

I've created multiple custom fields of type:
A) csv text visualized in tag browser
and one custom field of type:
B) text column visualized in tag browser

After filling data in metadata page, one can exit the page by pressing OK or NEXT.
Both types A and B are saved correctly after pressing OK.
Instead only fields of type A are saved after pressing NEXT, where fields of type B are not saved.

By the way, I add a question. Is it possible to have a simple text column non csv, not extended and not visualized in text browser?
The last for not having drop-down menu on the edit field.

Thanks and regards,
Paul Netsaver

Related branches

Charles Haley (cbhaley) wrote :

The value was being saved. The problem was that when using previous and next, the completion cache for the custom series and text widgets was not being updated, so new values were not in the cache. If one did a next then previous, this prevented edit metadata from initializing the widget, leaving it empty, causing the value to be removed on the next ok, next, or previous.

Changed in calibre:
status: New → Fix Committed
Charles Haley (cbhaley) wrote :

And for the question: no, there isn't a text field that does that. A comments field might get you what you are looking for.

Kovid Goyal (kovid) wrote :

@charles: To what have you committed the fix? Pulling from your branch yields no changes.

Charles Haley (cbhaley) wrote :

@kovid: sorry, forgot the push. :(

Fixed in branch lp:calibre. The fix will be in the next release. calibre is usually released every Friday.

 status fixreleased

Changed in calibre:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers