-
AuthorPosts
-
October 28, 2014 at 8:36 pm #342401
Versions
Wordpress: 4.0
Enfold: 3.0.2 (running child theme)After updating both WordPress and Enfold, we’ve noticed the following bugs occurring:
1) Updates to an existing page built with Advanced Editor are often not saved and can result in content disappearing from the page. I was able to consistently reproduce this by replacing/adding images on select existing pages of ours. If the images are separated from other content with a color section though, this appears to be okay..or at least not as bad.
Related Posts: https://kriesi.at/support/topic/big-issue-with-enfold-3-0-1-wp4-avia-breaks-up/
https://kriesi.at/support/topic/lost-changes-in-advanced-editor/2) Color Sections do not properly close – if background color is not selected for the section, it will continue until the next color section starts
Note: I’ve noticed this happening with existing pages… I have not tested by building a brand new page yet.
Related posts: https://kriesi.at/support/topic/editing-page-in-advanced-editor-breaks-color-sections/3) Buttons that include “>” in the text field appear to be completely independent from the styles selected. Its as if the symbol closed an incomplete tag that came before it. This never used to happen before.
In all three of these instances, it appears tags are either not being properly closed or closing other existing tags inadvertently. Looking into this further, specifically #1 that I mentioned, I discovered that images added via Advanced Layout now come with a separate closing tag [/av_image] which was never there before. Aside from rebuilding countless pages of content, is there any solution or update that is coming that would resolve this sort of thing?
Hope this info is descriptive enough. Please let me know if I can provide any additional info.
October 29, 2014 at 9:02 pm #342978Following up on this, as its a major issue for our website – we’re currently unable to make any image changes on existing pages. If there is no solution at the moment, could you please let me know the best way to revert to the previous version of Enfold?
Thanks.
- This reply was modified 10 years ago by seanogee.
October 29, 2014 at 9:25 pm #342993I am running with the same problem with the Color Section.
What I noticed in the back end is that when a color section is activated, it closes the #wrap_all div, breaking everything that falls bellow it, and keeping the color section going until the end of the page, unless another another color section is added.
And from my understanding, all content produced in the advanced editor, should be inside the #wrap_all div, and I can’t figure out what’s breaking all the elements.
October 30, 2014 at 1:56 am #343149Ditto. I can’t even get forms to work using the code field.
October 30, 2014 at 7:31 pm #343576As a temporary workaround for issue #1 (updating existing images breaks page), I enabled debug mode for Advanced Layout Editor. Now when adding/updating images on existing pages, we simply remove any instances of [/av_image] before saving and all is well.
This a pretty ridiculous workaround to say the least, so hopefully the lovely Kriesi developers are able to offer a real fix shortly.
For anyone interested in the mentioned workaround, see this link: http://kriesi.at/documentation/enfold/enable-advanced-layout-builder-debug/
November 3, 2014 at 4:30 am #345050Hey!
Thank you for using Enfold.
1.) I was not able to reproduce the issue with the Image element. Did you add any html codes on this page? Debug mode turned on, removing the shortcode closing tag [/av_image] doesn’t necessarily fix or break the layout.
2.) Can you please create a test page with this issue?
3.) Please try use the html entity code of the greater than symbol. http://dev.w3.org/html5/html-author/charref
Best regards,
IsmaelNovember 3, 2014 at 7:25 pm #345461Thanks for getting back to me Ismael. To be clear, the image issue only occurs when editing existing pages. If I create a new page, all is well…unless I import a saved template. No HTML codes were added by us to the page.
November 5, 2014 at 8:09 am #346387Hey Guys!
Please also add a link to your site as well as the login credentials (in the “private data” field) , so we can take a look at your backend.
Cheers!
November 5, 2014 at 9:20 pm #346759This reply has been marked as private.November 5, 2014 at 9:55 pm #346776Hey!
Just checking before I edit anything else: You are currently running 63 plugins which is really quite a lot. Since you are having an issue that others do not have my best bet is that we are facing a plugin conflict. Have you at any time tried to disable your plugins to see if that solves the problem?
Regards,
KriesiNovember 5, 2014 at 11:44 pm #346854This reply has been marked as private.November 6, 2014 at 1:36 am #346904This reply has been marked as private.November 8, 2014 at 12:26 am #348002Hi @kriesi , where you able to log in/reproduce the issue?
November 9, 2014 at 8:58 pm #348442Hi @seanogee!
I think the problem was that some of the Image elements were missing their closing tag ([/av_image]) while the affected one had it, i fixed that via debug mode and the issue seems to be resolved now.
Regarding the button label, you’d need to use the entity version of the greater than sign because that symbol is reserved for closing HTML tags – http://dev.w3.org/html5/html-author/charref
Cheers!
JosueNovember 19, 2014 at 2:22 am #353432@josue –
You’re absolutely right, but until the update, images never had this closing tag ([/av_image])…so that means any images added/modified within our pages that have existing image elements would be missing that closing tag and therefore have problems. As noted in my previous comment, I have been doing this workaround you’ve mentioned however its unrealistic to have to continue doing this for all edits going forward… We never had any issues like this prior to the update, even though there was never an image close tag.Also, we had been using the greater than sign on many buttons prior to the update, again, without any issues. Totally understand that that symbol is also used for closing HTML tags, but since it worked before, we used it in multiple buttons and now its broken in the many places it exists. Not sure what was changed in the theme that caused this to happen…
November 20, 2014 at 9:26 am #354144Hey!
We tested this on our end and the Image element is not causing any issues whether you close the shortcode or not. We turned on debug mode to manually edit the shortcode and remove the [/avia_image] closing tag, updated the page and all contents below are still intact. This is probably a plugin conflict since you’re using a real lots of plugins. And out of thousands of Enfold users, you’re the only one who reported this issue. The related post that you mentioned, turns out to be the user’s fault.
https://kriesi.at/support/topic/big-issue-with-enfold-3-0-1-wp4-avia-breaks-up/#post-337721
Regards,
Ismael -
AuthorPosts
- The topic ‘Page updates to elements in Advanced Editor often breaks code’ is closed to new replies.