Upgrade to 9.7.13 broke custom dropdowns

A bug was reported and fixed here: https://code.google.com/p/wordpress-custom-content-type-manager/issues/detail?id=545

If you can provide steps to reproduce I can reopen the issue.

I’m experiencing a similar issue with plugin version 0.9.7.13. I have a custom content type with 3 sets of dropdowns, one of which won’t re-display the chosen item upon coming back to the content in the admin area. I find it odd that only one of three dropdowns has this issue. The malfunctioning dropdown does have 21 items in it. The previously selected value will display on the frontend template however.

So, in terms of steps to reproduce:
1) select an existing custom content item from the list
2) in the admin edit window, one of dropdowns will be blank. This is the initial default selection. (on the frontend, the previously selected dropdown value will be displayed, ie: not blank)
3) select one of the dropdown elements and “update” the content

I can email you admin access to the website in question if this will help.

Thanks in advance!

ps: As a recap we’ve actually worked together in the past to build functionality into this plugin for this client. I thought however this would be the most appropriate place to post this particular issue.

I’m guessing the broken dropdown contains a character that is not converting to JSON and back, so the “is checked” test fails. It would be helpful to have a list of the dropdown options you are using. Did the fix outlined in https://code.google.com/p/wordpress-custom-content-type-manager/issues/detail?id=545 work?

I’ve posted a screenshot to this field data on Dropbox: https://bit.ly/1udGt00

I have the correct if test on line 224 as mentioned at the end of that Issue page. Anything else I might be missing?

Thanks!

Unfortunately the resolution of that image is not clear enough for me to spot any potentially problematic characters.

I’m not sure why Dropbox dorked the resolution of that image. I’ve uploaded a zip file with a jpg and png version inside: https://bit.ly/1ria3iC – Sorry for the inconvenience.

I would guess the problematic characters are the slashes or the parentheses.

Is it possible to allot for these characters in the plugin code? What would such an edit require in cost / time? Thanks for looking into this!

Those characters should work (in theory), however, the translations between json and serial data and printing into a form can make non alpha-numeric characters more likely to be converted to an entity that’s not recognizable and that (I think) is the root of the error. In general I recommend using simple alpha-numeric characters as the stored value for things like this and display whatever makes sense to see as the values. The important thing is to simplify the values that are stored — fewer moving parts.

If you’d like to discuss related work, then please send me an email. Thanks.

Hmmm. After some feedback from the client, there hasn’t been any issue with these same characters previously. According to them, they first noticed these issues only about a month ago. Thoughts? I can get you admin access to the site if that might help.

Any discussion of paid work needs to happen via email.