Asset Optimization – The link you followed has expired

Hi @crancherry

I hope you’re well today!

Such issues are usually related to expired or in other way invalid nonce. Nonce are a special “method” to provide additional security of requests in WordPress (more information here).

If you have already tried number of things (such as clearing cache and similar) it’s quite possible that there might be some conflict on site. Is it the only case (publishing Asset Optimization settings in Hummingbird) when you’re experiencing such issue or did you notice similar issues at other areas of site’s back-end too?

Are you using on site currently:

– other plugin or external tools (like hosting or CloudFlare or other CDN feature) for asset (css/js) optimization? if yes – what are they?

– additional security plugins (other than our own Defender) and if yes – what are they?

– is everything on site (WordPress core, active theme and all active plugins) on site up to date?

– what’s the site’s PHP version?

Let us know, please.

Kind regard,
Adam

Hi, thanks for the help! I needed a quick fix for a client so I had to go ahead with another plugin. However, to answer the questions, the site is hosted on GoDaddy’s managed WordPress and uses their CDN. Framework is Elementor; using security plugin Limit Login Attempts Reloaded; everything is up to date; PHP 7.4.

Hi @crancherry

Thank you for response!

The PHP version shouldn’t be an issue then but host’s CDN may be, depending on its configuration. If it’s “offloading” the assets (essentially “moving” JS/CSS out of the site to the CDN) then it would be conflicting.

A workaround could be to disable it temporarily, then set asset optimization in Hummingbird, then enabling that CDN again and clearing its cache if possible. But I admit I never tested it personally (as I’m not GoDaddy’s user).

If that doesn’t help, then a full conflict test would have to be performed to identify what’s breaking nonce in this case. Such test means:

– disabling all caching and CDN
– switching site default Twenty Twenty-Two theme
– disabling all the plugins except Hummingbird
– then if the issue no longer happens start enabling theme and plugins back one by one after each one checking for the issue; when it starts to happen again, it means that the last enabled plugin (or theme) right before it is causing some sort of “clash” and that we can investigate further on our end.

I understand that at this point you cannot do such test on the site in question (as you switched to another plugin) but if you decide to give it another shot or you can conduct such test on some staging/dev site where the issue is also happening, we’ll be around to assist you so just notify us about test results at any suitable moment and we’ll get back to the case.

Kind regards,
Adam

Hello @crancherry ,

We haven’t heard from you for several weeks now, so it looks like you don’t need our assistance anymore.

Feel free to re-open this ticket if needed.

Kind regards
Kasia