redwolfmendoza

I am getting the ‘ID3’ error on all my sites. It sounds like this issue has been reported in the past and “resolved”, but I don’t see this to be the case in WordPress v5.5.

Discussion: https://core.trac.www.ads-software.com/ticket/49499
Ticket: https://core.trac.www.ads-software.com/changeset/48278

I’ve also tried using their official htaccess guide to try to block access to /wp-includes/ID3/module.audio.ac3.php and tried someone else’s tweak but no success:

https://www.ads-software.com/support/topic/official-htaccess-rules-not-working-to-block-wp-includes/

• This reply was modified 4 years, 3 months ago by redwolfmendoza.

Hi Mateusz, thanks for the quick reply!

After some investigation, you are correct – the main class file ‘app/AcfBetterSearch.php’ is corrupt/missing. Please consider this issue resolved and close/remove this topic. Thanks!

To mod: please remove this topic

Hey Yani, I spoke to our Network Security team about the false positive mentioned above, they would like a bit more info. Can you give a brief technical explanation as to why you think these are false positives? Thanks again!

Thanks for the quick reply Yani,

I will notify our network security team that this is an unlikely scenario. Thanks again!

• This reply was modified 5 years, 1 month ago by redwolfmendoza.

Thanks for the quick reply Vasyl! AAM is now working for us (at least for the moment). I’m adding this comment in hopes that it may help others:

It seems that completely deleting and then reinstalling the AAM plugin by itself – as opposed to bundling it with other plugin updates through an automated deployment – works most of the time. We still see the error above occasionally when re-deploying, but it is difficult to reproduce in our staging environment and does not happen at all in our local dev environments. It’s possible that our continuous integration server (Bamboo) may be caching certain parts of our repo during the build phase, but I don’t know if that is even a feature.

• This reply was modified 5 years, 3 months ago by redwolfmendoza.
• This reply was modified 5 years, 3 months ago by redwolfmendoza.

Hi Vasyl,

After updating AAM plugin, we are seeing the ‘The site is experiencing technical difficulties’ message. PHP logs show the following:

Uncaught Error: Class ‘AAM_Core_Config’ not found in /var/www/html/wp-content/plugins/advanced-access-manager/aam.php:122

Deleting/ReInstalling the AAM plugin (as has been suggested in several forums) is not a realistic solution for us because we have continuous integration setup on our websites (scheduled core/plugin updates). We’ve also seen this problem come back a few hours/days after deleting/reinstalling.

Can you suggest a more permanent solution?

• This reply was modified 5 years, 3 months ago by redwolfmendoza.
• This reply was modified 5 years, 3 months ago by redwolfmendoza.

Thanks for the quick reply! We will try to exclude the Cookiebot consent button from this event handler (by ‘id’) going forward.

We’ve also have had some success using the ‘defer’ setting on the Consent banner script tag (Cookiebot > Settings > ‘Add async or defer attribute
Consent banner script tag’).

It is possible that our EU visitors are experiencing some issues with the load order of their scripts when visiting the site(s) and that also may be interfering with the consent button functionality. So, deferring the script seems to help.

Thanks again!

• This reply was modified 5 years, 7 months ago by redwolfmendoza.

Thanks, I will try disabling my other plugins.

I’m pretty sure it was stated clearly:

“Also, if you’re adding this plugin to a site that’s been around for a while, your existing media files will not be copied or served from S3.”

That’s why we have documentation! Hope that helps. ??