werremeyer

That worked, thanks!

Walter thanks for the response! I actually figured out it was some sort of caching issue. Had to use ?nocache=1 at the end of the url in the address bar to fix it. (mydomain.com/?nocache=1) Thanks again!

I’ve been experiencing similar issues. A P3 Plugin Profiler scan shows that Yoast Plugin uses 24% of plugin runtime. Thoughts? Thanks in advance.

That worked thank you!

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.

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!

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’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!

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.