Did the parse order of plugins change in 2.0?
Development and Programming
In 1.6, I use a wymeditor and used urldecode() on the data before it’s saved, so {exp:page_url entry_id='4'} would be saved as a non-encoded string, and thus it would actually parse without needing the allow_ee_code plugin.
I’m converting these to 2.0, and page_url works fine if I print it in a template, but if I do the same urldecode() on {exp:page_url entry_id='4'}, and it’s saved properly, but it doesn’t parse at all in the template, thus it leads me to believe that the parse order was changed… and not in a good way.
So did the parsing order change? I understand that, by default, EE will encode all EE tags when saving a field, but if I create a plugin/fieldtype and choose to bypass this, it should be allowed.
Moved to Plugins by Moderator
This is probably going to be moved to the plugins forum, we don’t provide direct support for coding plugins or fieldtypes. I’ve asked the dev team for clarification, Thanks in advance for your patience.
Moving to Plugins forum..
No- there shouldn’t have been a significant change in parse order. I’m not up on the plugin and having a little trouble following how it breaks down- but if you var_dump, that give any hints as to what’s up?