This question may be related to a resolved thread.
Hello,
I know this is already in the tracker but it has been there since October with no update at all. We cannot upgrade existing sites to newer versions of Expression Engine because they rely on this 1st part add-on to be working. Also, we can’t develop our new sites that require this because it is still not working.
Maybe for some this plugin doesn’t matter, but for many people, it is critical for the functionality of their websites. Since it is a 1st party addon, why has it not been addressed yet?
From the bug tracker, it seems that this was not even looked at past the initial addition by Sue. If I am mistaken, a status update on the tracker would be appreciated.
I know there are many priorities, but do we need to do a petition to have this bug get some attention? I’m frustrated right now because we planned for a week now for this new project thinking that allow_eecode would be working and now it isn’t. So instead of continuing work, I have to write this and then go back and rethink our entire approach. The worst part is we setup the system already with this in mind, argh.
Since it seems the problem is in EE and not the plugin itself I doubt this would be possible, but if there is a simple fix we can implement ourselves until a newer version resolves this, that would be greatly appreciated.
Thank you and I apologize if my tone seems harsh.
P.S. this is a new EE account, we’ve been using EE for years though so please disregard my low post count number 😊