Hi @epas
Thank you for bringing this to our attention.
Can you please confirm if you are currently using Beaver Builder on your site?
Best regards,
Victor
Thread Starter
epas
(@epas)
Hello,
No. Beaver Builder is not used. The plugin list:
Advanced Woo Search
Version 3.67 | By ILLID
CookieYes | GDPR Cookie Consent
Version 3.5.3 | By CookieYes
Elementor
Version 4.2.0 | By Elementor.com
Elementor Pro
Version 4.2.0 | By Elementor.com
Filter Everything — WordPress & WooCommerce Filters
Version 1.9.4 | By Andrii Stepasiuk
GTranslate
Version 3.1.1 | By Translate AI Multilingual Solutions
Secure Custom Fields
Version 6.9.2 | By WordPress.org
WooCommerce
Version 10.9.4 | By Automattic
@epas Can you please send us the link to the page where you are trying to add filters? Also, please provide a description of how the plugin is breaking the site so we have more details to investigate.
This is quite an unusual situation, especially considering that it is only a warning rather than a fatal error that would normally cause the site to break.
Maybe there are other errors in the debug.log file, including fatal ones, along with this warning. Could you please check and let us know if you find anything else? Or attach the data from the debug.log file
Best regards,
Victor
Thread Starter
epas
(@epas)
I added filtering via shortcode to the Elementor Theme Builder Products archive page: [fe_widget]
There is also an Archive Products widget on the page.
There are no fatal errors, but around 31 warnings are generated, and they break the site in some places. Turning off PHP error output would probably hide the issue, but as a temporary solution I used Claude to fix it, and the fix works:
private static function detect_builder_from_html($html)
{
if (!is_string($html) || $html === '') {
return null;
}
foreach (self::$builders as $builder => $signatures) {
if (isset($signatures['classes'])) {
foreach ($signatures['classes'] as $class) {
if (!empty($class) && strpos($html, $class) !== false) {
return $builder;
}
}
}
if (isset($signatures['data_attrs'])) {
foreach ($signatures['data_attrs'] as $attr) {
if (!empty($attr) && strpos($html, $attr) !== false) {
return $builder; // buvo return $attr — bug
}
}
}
}
return null;
}
We have tried to recreate the warning using the same setup, but without success.
We will continue to monitor this situation to see if we receive any similar reports. This will help us determine whether the warning is related to a specific environment or configuration. Once we are able to reproduce the issue on our end, we can identify the root cause and apply a proper fix to prevent any further issues.
Best regards,
Victor
Thread Starter
epas
(@epas)
If there’s a way to provide you with the credentials securely, just let me know. I’d be happy to do it.
The forum guidelines do not allow that. If you would like, you can contact us through our official website instead. We also have a chat available there.
Best regards,
Victor
