Priority not set properly (was Priority not showing up)

I see the same problem on the 4.7 version (my family site continues to use 4.6 as I'm too busy to upgrade, so I missed this. I don't use the latest version of my own module. :( ).

Thanks for reporting this. I'll work to get it fixed as quickly as I can.

In case you haven't looked at it yet ...

... It appears that item_priority is always being set to 0 when an item is inserted or updated. If I change the item_priority in the database by hand to, say, 1, the correct priority text for such a value ("I really want this") is displayed properly. If I go to the edit page, change nothing, and submit, the value is changed back to 0.

I had seen that and appreciate your having taken a look. What I have not worked out yet is the right and proper way to pull the value from the form. I've been unable to find an example in any of the modules I use of a drop down list where the underlying value was stored off as an integer.

My apologies on not having the time to address what should be a simple fix. I'm about a week away from my self-selt production deadline on http://www.folkjam.org, which is a fairly heavily customized Drupal site where I've been stretching some new boundaries (for me) on Drupal. Obviously forms API knowledge is not an area it stretched enough. :) This site has been taking up all of my outside of work development time for several weeks. Once it is live I owe a number of wishlist module changes.

I was able to get it to work by commenting out the line

'#multiple' => TRUE,

in wishlist_form. It doesn't function as a multiple-selection list box anymore, but it looks like only the first item selected was ever used anyway.

That makes sense - I must have had multiple select on in the 4.6 module and never noticed it. The automatic form translater just translated what it saw...

Great. The fix is in both 4.7 and head. I've spot tested, if you see further problems with the priority reopen this issue.