WPIntell

Source evidence

Critical Failure

Ultimate Dashboard – Custom WordPress Dashboard · support · 2024-07-23T22:56:00+00:00

mixedsentiment
highseverity
0.94relevance
9replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

3 / 13 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

10 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
gems1508 resolved
The main plugin with 6.6 and 6.6.1 has created a critical failure. There is no way to contact directly Same here. Critical Error when logging in to the site with 6.61. After renaming the Ultimate dahsboard folder via FTP, everything works. Can confirm it. Same problem here. Typ E_ERROR in line 165 /plugins/ultimate-dashboard/modules/setting/class-setting-output.php Same here , critical error , after renaming ultimate dashboard plugin folder everything is back again It looks like the the WordPress Version 6.6.1 is causing the problem. After a Downgrade to 6.6 everything is fine. Same issue here. I face critical error on my websites, when I deactivate the plugin, everything is going back to normal. I managed to solve it by editing my plugin file that had an error Fatal error: Uncaught Error: Attempt to assign property “title” on null in ../ultimate-dashboard/modules/setting/class-setting-output.php on line 165 Before: /** * Change Howdy text. * * @param WP_Admin_Bar $wp_admin_bar WP_Admin_Bar instance. */ public function change_howdy_text( $wp_admin_bar ) { $settings = get_option( 'udb_settings' ); if ( empty( $settings['howdy_text'] ) ) { return; } $my_account = $wp_admin_bar->get_node( 'my-account' ); $my_account->title = str_ireplace( 'Howdy', esc_html( $settings['howdy_text'] ), $my_account->title ); $wp_admin_bar->remove_node( 'my-account' ); $wp_admin_bar->add_node( $my_account ); $my_account = $wp_admin_bar->get_node( 'my-account' ); } After: /** * Change Howdy text. * * @param WP_Admin_Bar $wp_admin_bar WP_Admin_Bar instance. */ public function change_howdy_text( $wp_admin_bar ) { $settings = get_option( 'udb_settings' ); if ( empty( $settings['howdy_text'] ) ) { return; } $my_account = $wp_admin_bar->get_node( 'my-account' ); if ( null !== $my_account ) { $my_account->title = str_ireplace( 'Howdy', esc_html( $settings['howdy_text'] ), $my_account->title ); $wp_admin_bar->remove_node( 'my-account' ); $wp_admin_bar->add_node( $my_account ); } } Fix my error Note the before and after in the code if it is the same error it will be corrected Check if this problem is the same on line 165 of the file class-setting-output.php This reply was modified 1 year, 10 months ago by Thomaz Montagnini . This reply was modified 1 year, 10 months ago by Thomaz Montagnini . This reply was modified 1 year, 10 months ago by Thomaz Montagnini . Reason: Missing a note Wow, it works! Thank you very much! Worked for me as well Thank you for the quick fix. P.S. Are there any big updates coming for Pro? Ultimate Dashboard version 3.8.1 addresses and fixes this issue. This was caused by a change in the most recent WordPress core release (6.6.1).

Comments

9 shown
likos73 2024-07-24T07:15:00+00:00

Same here. Critical Error when logging in to the site with 6.61. After renaming the Ultimate dahsboard folder via FTP, everything works.

diewelle 2024-07-24T07:50:00+00:00

Can confirm it. Same problem here. Typ E_ERROR in line 165 /plugins/ultimate-dashboard/modules/setting/class-setting-output.php

hakhakop 2024-07-24T09:25:00+00:00

Same here , critical error , after renaming ultimate dashboard plugin folder everything is back again

diewelle 2024-07-24T09:28:00+00:00

It looks like the the WordPress Version 6.6.1 is causing the problem. After a Downgrade to 6.6 everything is fine.

Vasilis 2024-07-24T10:27:00+00:00

Same issue here. I face critical error on my websites, when I deactivate the plugin, everything is going back to normal.

Thomaz Montagnini 2024-07-24T12:42:00+00:00

I managed to solve it by editing my plugin file that had an error Fatal error: Uncaught Error: Attempt to assign property “title” on null in ../ultimate-dashboard/modules/setting/class-setting-output.php on line 165 Before: /** * Change Howdy text. * * @param WP_Admin_Bar $wp_admin_bar WP_Admin_Bar instance. */ public function change_howdy_text( $wp_admin_bar ) { $settings = get_option( 'udb_settings' ); if ( empty( $settings['howdy_text'] ) ) { return; } $my_account = $wp_admin_bar->get_node( 'my-account' ); $my_account->title = str_ireplace( 'Howdy', esc_html( $settings['howdy_text'] ), $my_account->title ); $wp_admin_bar->remove_node( 'my-account' ); $wp_admin_bar->add_node( $my_account ); $my_account = $wp_admin_bar->get_node( 'my-account' ); } After: /** * Change Howdy text. * * @param WP_Admin_Bar $wp_admin_bar WP_Admin_Bar instance. */ public function change_howdy_text( $wp_admin_bar ) { $settings = get_option( 'udb_settings' ); if ( empty( $settings['howdy_text'] ) ) { return; } $my_account = $wp_admin_bar->get_node( 'my-account' ); if ( null !== $my_account ) { $my_account->title = str_ireplace( 'Howdy', esc_html( $settings['howdy_text'] ), $my_account->title ); $wp_admin_bar->remove_node( 'my-account' ); $wp_admin_bar->add_node( $my_account ); } } Fix my error Note the before and after in the code if it is the same error it will be corrected Check if this problem is the same on line 165 of the file class-setting-output.php This reply was modified 1 year, 10 months ago by Thomaz Montagnini . This reply was modified 1 year, 10 months ago by Thomaz Montagnini . This reply was modified 1 year, 10 months ago by Thomaz Montagnini . Reason: Missing a note

likos73 2024-07-24T14:34:00+00:00

Wow, it works! Thank you very much!

gems1508 2024-07-24T15:57:00+00:00

Worked for me as well Thank you for the quick fix. P.S. Are there any big updates coming for Pro?

David Vongries 2024-07-25T22:50:00+00:00

Ultimate Dashboard version 3.8.1 addresses and fixes this issue. This was caused by a change in the most recent WordPress core release (6.6.1).