• Resolved Starhorsepax2

    (@starhorsepax2)


    Every time we do a site edit, we have to clear cache just to preview the page before saving. Is this normal? Is there a setting we need to turn off or on to prevent this?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Saurabh – WPMU DEV Support

    (@wpmudev-support7)

    Hello @starhorsepax2

    Hope you’re doing well today! I am sorry to hear about the issue you’re facing.

    Ideally, Hummingbird Cache should be excluded when the user is logged in and the preview should not be cached.

    However, such an issue could occur in case you have the “Include logged-in users” option enabled in the Hummingbird >> Caching >> Page Cache >> Settings.

    Ref: https://monosnap.com/file/H6xaXkbh3b4Tz1wlpRmzyXszDdWNoE

    Could you please check if you have it enabled? If yes, you can disable it, save the settings, clear all caches and check if you still notice the issue. Let me know if that helps.

    Also, could you please confirm if you are using any other cache probably any server caches or Cloudflare maybe?

    Awaiting your response.

    Kind Regards,
    Saurabh

    Thread Starter Starhorsepax2

    (@starhorsepax2)

    The option doesn’t have cache logged in user. I do see an option for lightspeed caching on the Cpanel, but I’m not sure if it’s being used. It does say enabled. We do not have a plugin for it in WordPress though.

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @starhorsepax2,

    If the “Include logged in users” option isn’t enabled, there isn’t anyway Hummingbird could cache the pages while logged in.

    Do you have the “Clear full cache when post/page is updated” option enabled as shown in the previous screenshot? If not, could you please check and see how it behaves once “Clear full cache when post/page is updated” is enabled?

    If the issue is till the same even after that then please do let us know whether you have Asset Optimisation enabled?

    If yes, please check whether you could replicate the same issue if Asset Optimization is temporarily disabled under Hummingbird > Asset Optimization > Settings > Deactivate

    ?I do see an option for lightspeed caching on the Cpanel, but I’m not sure if it’s being used. It does say enabled. We do not have a plugin for it in WordPress though.

    Even after the above previous suggestions, if you still notice the same issue then there might be a high chance the issue might be more specific within the server side as you have pointed out.

    Please do check and see whether you could replicate the same behaviour if you temporarily disable the Hummingbird plugin as a whole.

    The above steps would help in ruling out where exactly to look further.

    Please do let us know how that goes.

    Kind Regards,

    Nithin

    Thread Starter Starhorsepax2

    (@starhorsepax2)

    Clear full cache when post/page is updated is enabled.
    I tried disabling Asset optimization and it didn’t help.
    Then I tried disabling the plugin itself and it still didn’t show preview changes.
    One thing I wonder about: when I made a new post just to test, it would not only not preview but didn’t find the page. It would not until I save the draft. And it’s previewing before we save a live page (in case the changes break something) that is specifically not working.

    I wonder..could modification to wp heartbeat cause this? That might’ve been done in the past.

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @starhorsepax2

    I hope you are doing well.

    In case the plugin is disabled and the changes are not showing up then it is a different variable causing the problem.

    What you can do:

    – Check the header response for any caching HIT, like Cloudflare or hosting cache https://stackoverflow.com/questions/4423061/how-can-i-view-http-headers-in-google-chrome
    – Run a full plugin conflict test: https://wpmudev.com/docs/getting-started/getting-support/#conflict-test

    Best Regards
    Patrick Freitas

    Thread Starter Starhorsepax2

    (@starhorsepax2)

    I think we might’ve found it. Someone had modified the WP heartbeat, even in the back end. Once I set it to default it seems to have helped.

    Thanks for your help! It ruled out some things.

    Plugin Support Zafer – WPMU DEV Support

    (@wpmudevsupport15)

    Hi @starhorsepax2,

    Thanks for the update. We are glad to hear that the information provided has been helpful for you and we are marking this thread as resolved accordingly. Please let us know in case you need further help.

    Kind regards,
    Zafer

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