WPIntell

Source evidence

Fatal Error, Please Help!

Custom Sidebars – Dynamic Sidebar Classic Widget Area Manager · support · 2025-03-04T01:47:00+00:00

Custom Sidebars – Dynamic Sidebar Classic Widget Area Manager plugin evidence original source source API
neutralsentiment
highseverity
0.58relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 27 rows with source links

14.8% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

23 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
murdoch1810 resolved
My site appears fine and the sidebar is working properly but the error is affecting the backend of my site. Any idea what happened and how to fix this? WordPress version 6.7.2 Active theme: Hestia Pro (version 3.2.8) Current plugin: Custom Sidebars (version 3.37) PHP version 8.2.18 Error Details ============= An error of type E_ERROR was caused in line 148 of the file /home2/cbdfacil/public_html/wp-content/plugins/custom-sidebars/customsidebars.php. Error message: Uncaught Error: Class “CustomSidebars” not found in /home2/cbdfacil/public_html/wp-content/plugins/custom-sidebars/customsidebars.php:148 Stack trace: #0 /home2/cbdfacil/public_html/wp-includes/class-wp-hook.php(324): {closure}(”) #1 /home2/cbdfacil/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(true, Array) #2 /home2/cbdfacil/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /home2/cbdfacil/public_html/wp-admin/admin-header.php(303): do_action(‘admin_notices’) #4 /home2/cbdfacil/public_html/wp-admin/index.php(137): require_once(‘/home2/cbdfacil…’) #5 {main} thrown This topic was modified 1 year, 2 months ago by murdoch1810 . We’re aware of the issue and should have an update out today.

Comments

1 shown
Gordan 2025-03-04T07:35:00+00:00

We’re aware of the issue and should have an update out today.