-
Posts
-
We are on the latest Version, but we have problems with the footer after updating the page.
We get a bug with the footer after changing and saving the page.
After deleting a space between to shotcodes, the footer works normally, but if we want to update the page again the bug comes again.Hey Innovie,
The login token you posted doesn’t work, please renew it or post regular login details. If you could explain the problem you are having a bit further then that would be helpful as well.
Best regards,
Rikard@Rikard please try the link again!
As you can see in the demo video we save the page but after saving the page the html structure changes, so that the footer is not in the #wrap_all container anymore. this is what we can replicate (see the demo video).
there is an issue with the avia editor for sure. because if we remove a space between to shotcodes it works again. after updating something again in the avia editor the error appears again.
an extension on that topic:
we also recoginzed that sometimes enfold updates the page but not the avia editor in the backen (which jumps back to the version before), changes in the frontend are seen but after updating the avia editor again, the changes of the last frontend version are gone again. This doesnt appear if i use the classic editor instead for changing the content. I think the avia editor doent load the latest version of the page in all cases.This extension on the issue also appears on a completly different environment here:
from time to time clients complain about that issue. which happens on several sites.
Hi,
Thanks for the update, the login token works now. I can’t reproduce the problem which is shown in your clip though. I selected the second from last option (unten, ohne ramen), but the footer widgets are still stacking after that on my end. Is there something I’m missing in regards to reproducing the problem in your clip?
Best regards,
RikardWe found out that it was the https://de.wordpress.org/plugins/wp-typography/ plugin which struggles, because the html markup of the content builder isn’t clean in the frontend.
we switched it of and it now works, but is that the solution?
Hi,
Thanks for the update, I’m glad that you found the source of your problems. Are you asking for a solution to get the plugin working? If so then I’m not sure we have one unfortunately, maybe you could try reaching out to the plugin developers or try to look for an alternative to that plugin?
Best regards,
Rikard
- You must be logged in to reply to this topic.