04 related to bc-v3.min.html (cookiebot)

marketing

• February 04, 2022 14:48

hi

from january 27 we have so many 404 error, after performing a first debug I found that the 404 error is related to the bc-v3.min.html file which is from cookiebot. how to solve?

0

• 

  marketing

  • February 04, 2022 15:15

  I'm investigating into the problem, it seems related to a siteground caching setting

  0
• 

  KP

  • February 16, 2022 08:30
  • Edited

  Same issue here. bc-v3.min.html get status code 404 on most subsites!!! Widget is not loading!

  0
• 

  marketing

  • February 16, 2022 08:40

  do you have any caching system enabled?

  0
• 

  KP

  • February 16, 2022 08:44

  Yes, I'm using wp Rocket. Which js file do I have to exclude to get it work?

  0
• 

  marketing

  • February 16, 2022 08:53

  the official support can say which js file you have to exclude

  i think that can be 

  uc.js 

  the file bc-v3.min.html is, probably, the SDK 

  try for small steps, disable the JS minification and try this for every settings in wp rocket 

  0
• 

  KP

  • February 16, 2022 08:57

  excluding uc.js is working! Thanks

  0
• 

  marketing

  • February 16, 2022 09:04

  perfect :-) 

   

  Elvis

  0
• 

  yuloi

  • February 17, 2022 10:52

  We are dealing with the same problem. Most subsites return 404 errors for bc-v3.sec.html! There is no widget to display!

  0
• 

  Emmafrem

  • February 20, 2022 12:23

  I'm looking at the issue, and it appears to be tied to a siteground caching option. If you haven't yet funded your solution, go here for more information.

  0
• 

  marketing

  • February 21, 2022 07:39

  have you tried to exclude uc.js from the caching?

  in the javascript section on siteground optimizer 

   

  0
• 

  Tony Wilke

  • May 26, 2022 09:19
  • Edited

  The WP Plugin development team will be returning to us about the release ASAP but in the meantime, the warning should be harmless and you may disable the debugging mode.

  To disable debugging mode in WordPress, follow these steps:

  1. Log into your hosting account and launch File Manager.
  2. In the public_html folder, find and open wp-config.php.
  3. In the wp-config file, you’ll find the following line of code –

  define(‘WP_DEBUG’, true);

  The WordPress debug mode is now enabled. To disable it, you’ll have to replace ‘true’ with ‘false.’ It looks like this –

  define(‘WP_DEBUG’, false);

  Save the changes and exit the editor. You have now disabled WordPress debugging mode and the reported error should not be visible anymore.

  0

Please sign in to leave a comment.