Smush causing 403 error

  • Resolved fedupnonstop

    (@fedupnonstop)


    4 years, 4 months ago

    Hi,

    Tried looking for this problem but couldn’t find anything. Apologies in case there is help but I used the wrong keyword when searching. Will sort info in dates so it’s more clear.

    Tues 27/10 2020

    Sent following email to my theme support (Elementor Pro):

    I have up ’till now optimized my client’s site (perezterapi.se) in a staging environment (https://perezterapi.se/stg_e9de0/). When I transferred the staging site to the main domain, it looked good at first but now there are some things missing:

    – Video background (hero section)
    – Header logo (top left corner)
    – Image of logo
    – Google maps plugin (in contact section)
    – Elementor not showing in WordPress Admin Top bar.

    I have tried
    – Emptying cache in both WP backend and in browser.
    – Switched Elementor license to main site instead of to staging site.
    – Deactivate-Activate Elementor plugins. This worked a moment, then it went back to missing previously mentioned parts.

    I can access Elementor builder by going to Edit page, then pressing the button ”Edit with Elementor”. Then in the builder everything is back to normal. When I then preview the page most of the missing parts are back. Then I open a new tab and go to the site (perezterapi.se) and all the previously mentioned parts are missing.

    Wed 28/10 2020

    I received the following response from Elementor:

    “Upon inspecting your site I noticed some 403 error relating to these elements as shown here.

    And checking further the “Smush” plugin you have installed was causing this issue with the elements disappearing on the front end.

    I have currently deactivated this plugin and the content are showing up now and errors resolved, please refer to this screencast to see everything works.”

    This is my response

    “…when I logged in to WP backend and went to frontend it was the same as before. Same objects missing.

    I have tried?
    – Clearing page cache through Hummingbird plugin
    ?– Clearing browser cache?
    – Reaching out to web host (one.com) about clearing server cache. They responded earlier today that they have ”purged varnish cache”.
    ?– Looking at the site in incognito mode and on other browsers. It all looks the same (missing previously mentioned objects).

    Like before, I can only access Elementor editor by going through Edit Page -> Edit with Elementor. Then everything is back to normal in the editor and when I preview the page.

    Has anyone experienced similar problems? Or maybe someone can point me in the right direction? Any help is much appreciated!

    All the best,
    Christopher

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hi Christopher,

    It’s possible that the migration kept some of the old optimized files that is causing these issues so could you try going to wp-content/uploads/ folder on your server and delete /hummingbird-assets/ folder from there.
    That should remove any leftovers that might have gotten transferred over and hopefully it will be enough to resolve this issue.

    While in there I would suggest checking for other caching folders and emptying them as those would be recreated (as well as /hummingbird-assets/) automatically.

    Let us know if this helped.

    Cheers,
    Predrag

    Thread Starter fedupnonstop

    (@fedupnonstop)

    Hi,

    Thank you for your prompt response! I deleted the hummingbird-asset folder but that made the theme break. I panicked and created a new folder named hummingbird-assets and deactivated hummingbird. This ended up solving all of my previously mentioned examples.

    I haven’t tried activating it again, but it does seem like this was the culprit. In hindsight, maybe it’s a bad idea to optimize (Smush & Hummingbird) your website in a staging environment?

    I hope this doesn’t mean that I won’t be able to use Smush & Hummingbird!

    All the best,
    Chris

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @fedupnonstop

    I hope you are doing well.

    You can use Hummingbird and Smush on the staging.

    We only suggest flushing the Assets Optimization cache after pushing to the live, or disable this feature before pushing the live.

    I do like to flush all caches and re-check the assets to make sure the URLs are updated not causing this problem.

    Another feature that I do like is using the Elementor > Settings > Advanced > CSS and switch to internal printing, it will decrease the number of assets created by Elementor which means the plugin will use less resource to combine the files and the browsers won’t call an extra file.

    Let us know if you have any additional question on this.
    Best Regards
    Patrick Freitas

    Thread Starter fedupnonstop

    (@fedupnonstop)

    Hi,

    Thank you for your helpful advice.

    Regarding switching to internal printing, is it something that should always be on? And is there a downside to using internal printing?

    All the best,
    Chris

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @fedupnonstop

    The Elementor create a new CSS for every Post you have on the website.

    It makes the Hummingbird need to handle multiple files, another issue is that some CDN, for example, the Smush > CDN are not able to handle the images when it created external files.

    This can keep always on, there is a warning about it can increase the load time but from my tests, after using the internal option, my images went to CDN, the optmization plugin had fewer files to deal with and it increased the score instead of decreasing.

    However, we only use Elementor for tests and support, you can run an A/B test using the internal vs external option and see which fits better for you.

    Best Regards
    Patrick Freitas

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @fedupnonstop

    I hope you are doing well.

    We haven’t heard from you in a while, I’ll mark this thread as resolved.

    However, feel free to let us know if you have any additional question or problem.

    Best Regards
    Patrick Freitas

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Smush causing 403 error’ is closed to new replies.