New to the community? Start here

[Hummingbird Pro] Hummingbird with Elementor Pro

Dear Support!

We have an issue with Elementor Pro and Hummingbird cache running at the same time: when we turn on Hummingbird cache, Elementor Pro admin area slows down painfully.

Could you help us with this issue?

Thank you!

Mon, 12 Apr 2021 9:39:08
More Hummingbird Pro discussions
Hummingbird Pro
  • Rakib Hossain
    • Support FLS

    Hi Zoltán ,
    I hope you’re well today and thank you for contacting us!
    I’m really sorry to hear that you are facing some issues with Hummingbird Pro.

    It would be great if you please could provide support access for checking this issue further. For granted support access please follow this URL https://wpmudev.com/docs/getting-started/getting-support/#enabling-support-access

    Once you have granted support access please leave a comment/reply here, so we can follow up with you, we do not get notifications when members grant us support access.

    Kind Regards,
    Rakib

  • Rakib Hossain
    • Support FLS

    Hi Zoltán ,

    Thanks for the support access.
    Could you please check now? Hummingbird cache is now enabled also Elementor admin area loading fine, seems like your issue solved now.

    [attachments are only viewable by logged-in members]

    Please do let us know if you have any further queries. Have a nice day ahead.
    Kind regards,
    Rakib

  • Rakib Hossain
    • Support FLS

    Hi Zoltán ,
    Thanks for your response back with additional info.

    I have just tried to replicate this issue in my lab site but seems Hummingbird Pro working with Elementor perfectly with the page caching feature enabled. So, seems like some sort of issue with your theme or other plugins.

    [attachments are only viewable by logged-in members]

    It would be great if you could perform basic troubleshooting by disabling your other plugins, switch to the default WP theme, and see if the saving issue is gone after that.
    If it is, reactivate them back one by one until the issue is back and that should tell us where the issue is coming from so we can debug it further from there.
    For better understand you can follow this flowchart https://wpmudev.com/wp-content/uploads/2015/09/Support-Process-Support-Process.gif

    I suggest doing this test on a staging site, or if you don’t have one make sure to have full site backup ready before doing the test on the live site.

    Best regards,
    Rakib

  • Arjay Lazaro
    • Acccounts and Billing - BL

    Hi Zoltán,

    I hope you are doing well.

    The next best course of action is that I recommend you set up a staging site that you can use for further troubleshooting. It will be a complete and exact copy of your site that will be set into another location/folder in the same server, using a separate database, and perform the conflict test in there instead without worrying about the live site.

    So either on the staging site (if applicable), or if not, then on the Live site, it is suggested to run a conflict test when the site starts misbehaving to figure out which one is causing the error.
    Proceed by following the steps below.
    – Create a manual backup from your current Hosting
    – Make sure not to visit the Plugins panel in WP admin while doing the test
    – Access your site files via SFTP/SSH, you can use your Hosting’s File-Manager or FileZilla to do this.
    – Navigate to public_html/wp-content/ folder and inside that create new folder named plugins_disabled
    – Go to public_html/wp-content/plugins/ folder and simply drag and drop your plugins to public_html/wp-content/plugins_disabled/ folder – except for Elmentor and other Elementor-related Plugins.
    – After that, the site should with some missing Layout or Features since the plugins would be disabled,

    — While all the rest of the plugins are disabled, can you try creating a new page for testing purposes and save it, check to see if it makes any difference.

    If the overall speed with updating or saving pages becomes more acceptable, drag the rest of Plugins back to /plugins/ folder one by one until the issue is back and that should tell you which of the plugins is causing the issue.

    Best regards,
    Arjay L.