Topic Title: Issue with Avada Live Builder and WP-Optimize – Cache Conflict

  • Resolved ralfdigitalagency

    (@ralfdigitalagency)


    3 months, 2 weeks ago

    Hello,

    I’m experiencing an issue where the Avada Live Builder is not working when the WP-Optimize plugin is activated on my website. As soon as I disable WP-Optimize, the Live Builder functions correctly. After troubleshooting, I found that the caching settings of WP-Optimize might be causing this issue.

    Here’s what I’ve tried so far:

    • I’ve excluded the specific page URL (where the Live Builder is used) from caching.
    • I’ve configured WP-Optimize settings to serve cached pages to logged-in users, but the issue persists.

    Has anyone experienced similar conflicts between WP-Optimize and Avada? Any guidance on resolving this or adjusting settings would be greatly appreciated.

    Thank you in advance for your help!

    Best regards,
    Alex

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support vupdraft

    (@vupdraft)

    Hi,

    You will need to configure the plugin so it does NOT serve cache for logged in users. Can you try this?

    Thread Starter ralfdigitalagency

    (@ralfdigitalagency)

    Thanks for the suggestion. The ?“Serve cached pages to logged in users”, is already UNCHECKED. Is this the setting you are referring too? If so it is not working.

    how can the issue solved?

    thanks a lot

    Plugin Support vupdraft

    (@vupdraft)

    Can you try turning off any minification on merging to see if the issue persists?

    Thread Starter ralfdigitalagency

    (@ralfdigitalagency)

    Yes, already did that, still persist the error, I tried everything. it seems to be a bug that need to be solved at a code level from the WP Optimize team I guess.

    Plugin Support vupdraft

    (@vupdraft)

    It looks like the Avada plugin does caching as well. If you are using WPO can you ensure the caching in Avada is off?

    Thread Starter ralfdigitalagency

    (@ralfdigitalagency)

    I checked the issue and found that disabling WP-Optimize caching didn’t resolve it. While troubleshooting the server, Avada released two updates. It’s unclear whether the problem was caused by permissions, a firewall setting, or an Avada bug. However, the issue now seems resolved.

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