WPIntell

Source evidence

PHP Fatal error

Shinobi Reviews · support · 2022-05-11T04:04:00+00:00

complaintsentiment
highseverity
1.0relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

5 / 47 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

42 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
alx359 unresolved
Upon activation after a fresh install, got this showstopper: PHP Fatal error: Uncaught Error: Call to undefined method Shinobi_Reviews\App\Widgets\Widgets::_register() in \wp-includes\class-wp-widget-factory.php:102 Stack trace: #0 \wp-includes\class-wp-hook.php(307): WP_Widget_Factory->_register_widgets('') #1 \wp-includes\class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array) #2 \wp-includes\plugin.php(474): WP_Hook->do_action(Array) #3 \wp-includes\widgets.php(1854): do_action('widgets_init') #4 \wp-includes\class-wp-hook.php(307): wp_widgets_init('') #5 \wp-includes\class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array) #6 \wp-includes\plugin.php(474): WP_Hook->do_action(Array) #7 \wp-settings.php(587): do_action('init') #8 \wp-config.php(144): require_once('D:\\domains\\dev....') #9 D:\ in \wp-includes\class-wp-widget-factory.php on line 102 And these assorted: PHP Notice: Only variables should be passed by reference in \wp-content\plugins\shinobi-reviews\App\Widgets\Widgets.php on line 29 PHP Notice: Only variables should be passed by reference in \wp-content\plugins\shinobi-reviews\App\Widgets\Widgets.php on line 29 PHP Notice: Undefined property: Shinobi_Reviews\App\Widgets\Widgets::$name in \wp-content\plugins\admin-menu-editor-pro\extras\modules\tweaks\ameHideSidebarWidgetTweak.php on line 19 PHP Notice: Undefined property: Shinobi_Reviews\App\Widgets\Widgets::$id_base in \wp-includes\class-wp-widget-factory.php on line 97 Hey @alx359 Thank you for reaching out to me, and I feel sorry about that. As you said that, most of this errors are caused by Shinobi Reviews but I already figured out its cause thanks to you. So that I want you to wait for the next version (or later) of Shinobi Reviews to use without any errors. It will be run better. Plus, if you would like to reject this errors right now, you can do that by turning the strict mode of WordPress off in wp-config.php. Reference: https://codex.wordpress.org/WP_DEBUG Many thanks for your time and help. Hi @shinobiworks , glad the report was useful. Not sure fatal errors can be just masked, but can’t just turn wp_debug off as it’s a dev site I’m actively working atm though. If you wish, I may test the fix if you change it in trunk. Thanks. Thank you for replying. To be honest, I had been misunderstanding that I was developing with strict mode (which means turning wp_debug on). But, from now on I believe I develop my plugin properly. Anyway, I really appreciate you about this feedback. Thank you. Hi @alx359 , I’m not sure you already tried the latest version of Shinobi Reviews, I’ll note about recent activities of developing it, just in case. Firstly, I have released version 1.5.8 of it, after we discussed in here before. It includes some new features and solved some errors you mentioned. Secondly, unfortunately I couldn’t solve “Fatal Error” like below because of I couldn’t see it. PHP Fatal error: Uncaught Error: Call to undefined method Shinobi_Reviews\App\Widgets\Widgets::_register() in \wp-includes\class-wp-widget-factory.php:102 I’m sure this error is related “Widget” and I’ve tried to test it in different dev environments (eg: PHP version, WP version, MAMP, Local by flywheel, etc), but in the end it has never occurred. Lastly, if you can still see this error in your dev environment, I want you to share me about it that means how should I represent this error. Many thanks.

Comments

4 shown
Shinobi Works 2022-05-12T04:13:00+00:00

Hey @alx359 Thank you for reaching out to me, and I feel sorry about that. As you said that, most of this errors are caused by Shinobi Reviews but I already figured out its cause thanks to you. So that I want you to wait for the next version (or later) of Shinobi Reviews to use without any errors. It will be run better. Plus, if you would like to reject this errors right now, you can do that by turning the strict mode of WordPress off in wp-config.php. Reference: https://codex.wordpress.org/WP_DEBUG Many thanks for your time and help.

alx359 2022-05-12T04:39:00+00:00

Hi @shinobiworks , glad the report was useful. Not sure fatal errors can be just masked, but can’t just turn wp_debug off as it’s a dev site I’m actively working atm though. If you wish, I may test the fix if you change it in trunk. Thanks.

Shinobi Works 2022-05-13T06:10:00+00:00

Thank you for replying. To be honest, I had been misunderstanding that I was developing with strict mode (which means turning wp_debug on). But, from now on I believe I develop my plugin properly. Anyway, I really appreciate you about this feedback. Thank you.

Shinobi Works 2022-06-06T06:34:00+00:00

Hi @alx359 , I’m not sure you already tried the latest version of Shinobi Reviews, I’ll note about recent activities of developing it, just in case. Firstly, I have released version 1.5.8 of it, after we discussed in here before. It includes some new features and solved some errors you mentioned. Secondly, unfortunately I couldn’t solve “Fatal Error” like below because of I couldn’t see it. PHP Fatal error: Uncaught Error: Call to undefined method Shinobi_Reviews\App\Widgets\Widgets::_register() in \wp-includes\class-wp-widget-factory.php:102 I’m sure this error is related “Widget” and I’ve tried to test it in different dev environments (eg: PHP version, WP version, MAMP, Local by flywheel, etc), but in the end it has never occurred. Lastly, if you can still see this error in your dev environment, I want you to share me about it that means how should I represent this error. Many thanks.