Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #672001

    The problem:

    • I make changes to a page using the Advanced Editor and press “Update”.
    • The page reloads and the Advanced Editor shows my changes correctly
    • However, when I visit the page on the front-end, it’s still showing the old layout

    Debugging:

    I have discovered that:

    • In the wp_postmeta table, the meta value of ‘_aviaLayoutBuilderCleanData’ contains the new, correct shortcodes for the post I’ve been editing
    • HOWEVER: In the wp_posts table, the column ‘post_content’ contains the OLD shortcodes

    This leads me to the following conclusions:

    • The Advanced Builder loads the content from the _aviaLayoutBuilderCleanData value
    • The front-end loads the content from the post_content field

    The question:

    Why doesn’t post_content get updated? What could be causing this?

    Environments where it happens:

    This has been an ongoing, intermittent problem with Enfold for almost 2 years across different hosts, domains and setups.

    Hosting setups include:

    • Ubuntu, CentOS, Windows, Linux Mint
    • LAMP – PHP 5.5, MySQL
    • LAMP – PHP 5.6, MySQL
    • LAMP – PHP 7, MySQL
    • LEMP – PHP 7, MariaDB 10

    Browsers and OS’s have included:

    • Firefox, Safari, Chrome, Internet Explorer, Edge, Pale Moon
    • OSX, Windows 10, Windows 8, Linux Mint

    This implies it is a server side issue (or javascript issue) rather than a browser issue.

    It’s become such a routine issue that I have trained staff in how to copy and paste from _aviaLayoutBuilderCleanData to post_content when it happens.

    I’ve also read many many posts on this forum of people experiencing the same problem.

    This is a major hiccup and I’d love to help you get to the bottom of what is causing it, for everyone’s sake.

    #672098

    Hey scottybowl,

    did you check if it’s a caching issue? ask your host if they are using some kind of caching and make sure you do not have any caching activated yourself.

    Please post us your login credentials (in the “private data” field), so we can take a look at your backend.

    Login credentials include:

    • The URL to the login screen.
    • A valid username (with full administration capabilities).
    • As well as a password for that username.
    • permission to deactivate plugins if necessary.

    Best regards,
    Andy

    #672393

    Definitely not a caching issue.

    I’d rather not give out details to our production server but can do a screenshare –

    #673479

    Hi,Un

    I’m sorry but we won’t be able to help if we can’t access the site. And we can’t reproduce the same issue on our own installation. Where is the site hosted?

    Best regards,
    Ismael

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.