-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling Front End Editing (EE6) kills some relationship field rendering #3035
Comments
@jcogs-design Can you send over the template code? And what fieldtypes are involved here (specifically interested in Grid, Fluid and Relationships) |
Might be easiest for you to poke around on the site directly - DM me if you want some access credentials. But roughly...
HTH. |
@jcogs-design can you try applying the change in this PR and see if that helps? (this is for v7 but the corresponding code is the same) |
Sure - will try and get to it later today and report back |
sorry - please hold off testing, I found an issue with that supposed-to-be-fix. I'll keep you updated |
OK - np |
@jcogs-design this should help - can you test and see? https://github.com/ExpressionEngine/ExpressionEngine/pull/3037/files#diff-a7429b2609d058d5df52b25e0197e0406aebb5850bd102e2fd9712512259aaf8R227-R235 |
…ates could cause some tags to be not parsed
…ates could cause some tags to be not parsed
…lex-templates-issue Resolved #3035 where enabling front-end editing on very complex templates could cause some tags to be not parsed
…ates could cause some tags to be not parsed
Description of the problem
Enabling 'Front End Editing' as an option in the EEPro add-on (licensed) in EE6 causes some relationship fields to fail to render.
See the before / after images attached.
How To Reproduce
Steps to reproduce the behavior:
Enable Front-End editing in EEPro add-on and reload page.
Environment Details:
The text was updated successfully, but these errors were encountered: