This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

Update and View Page impossible

Open 7 replies bug-reportpluginplugin-page-builder
Started · Latest reply by Andrew Misplon

Hello
After installing the latest version … wordpre press does not take into account the latest update on the page. Refresh, other browser … nothing … After deactivation of the plugin ()SiteOrigin Page Builder) all it’s Ok !
? Best regards
Pascal

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

7
  1. Andrew Misplon Staff

    Hi Pascal

    If changes are being successfully saved in the WordPress admin but not visible on the site front-end, caching is usually the issue. Either local browser caching or server-level caching. If you’re using a WordPress caching or optimization plugin, try clearing it, if that doesn’t help try clearing and then temporarily deactivating it to see if that resolves the issue.

  2. Pascal BAZZEA

    Hi,I don't use a cache, I wouldn't have bothered you for so little!

  3. Andrew Misplon Staff

    Please, send a link to an impacted page. Let us know which change should be reflecting on the page concerned. Thanks.

  4. Pascal BAZZEA

    The page was the contact page, the site has too many visitors to be left as is.

    I made the corrections and deactivate the 2 modules SiteOrigin Widgets
    Bundle, SiteOrigin Page Builde. Everything is operating normally.

    But I had never seen that …!?

  5. Andrew Misplon Staff

    I’ve seen instances of this but it has usually been related to browser or server caching so there isn’t a known troubleshooting process I can offer, we’re in the dark.

    If you could recreate the issue on a test page or any other page on the site and send me the link, it would be helpful. We could at least take a look at the markup and see if we spot anything.

  6. Pascal BAZZEA

    this has been reproduced on 3 or 4 browsers … including on smartphones.
    The browser cache had been emptied … it constantly took over a page it had kept … like that!

    I'm just going to call Fox Mulder ;)

  7. Andrew Misplon Staff

    Hahaha. Ok, thanks for the update.

    If you could recreate the issue on any page and send us the link, we’ll take a look and rule out anything we can see from the front-end and then go from there.

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread