Tagged: super admin privileges, warning
- This topic has 44 replies, 2 voices, and was last updated 4 years, 5 months ago by Syam Mohan.
-
AuthorPosts
-
May 15, 2020 at 4:41 pm #99227Gerald MenzelSpectator
Any news, Syam?
May 18, 2020 at 10:56 pm #99303Syam MohanKeymasterThis reply has been marked as private.May 20, 2020 at 3:27 pm #99353Gerald MenzelSpectatorThis reply has been marked as private.May 21, 2020 at 10:19 pm #99386Syam MohanKeymasterHi Gerald,
Please give me a few days.
Thanks
Syam
May 28, 2020 at 2:39 pm #99630Syam MohanKeymasterThis reply has been marked as private.May 29, 2020 at 5:33 pm #99666Gerald MenzelSpectatorThanks, Syam!
I have installed the new beta. The ‘super admin privileges’ message is gone again. But there are still a lot of noticed being generated. The log file grows maybe 10 MB per minute. I usually turn off the logging of notices. But on the dev server I leave it on for debugging purposes.
It’s always the same type of notice, e.g.
Notice: Trying to get property '_builtin' of non-object in /wp-content/plugins/wpfront-user-role-editor-personal-pro/includes/custom-post/class-customize-capabilities.php on line 105 Timestamp: 2020-05-29 11:56:56 UTC Stack Trace ----------- 1. WPFront\URE\Custom_Post\WPFront_User_Role_Editor_Custom_Post_Customize_Caps->is_cpt_user_visible(null) /wp-content/plugins/wpfront-user-role-editor-personal-pro/includes/ppro/custom-post/class-customize-capabilities-pro.php:105 2. WPFront\URE\PPRO\Custom_Post\WPFront_User_Role_Editor_Custom_Post_Customize_Caps_Pro->register(null) /wp-content/plugins/wpfront-user-role-editor-personal-pro/includes/ppro/custom-post/class-customize-capabilities-pro.php:75 3. WPFront\URE\PPRO\Custom_Post\WPFront_User_Role_Editor_Custom_Post_Customize_Caps_Pro::instance(WPFront\URE\Custom_Post\WPFront_User_Role_Editor_Custom_Post_Customize_Caps) /wp-includes/class-wp-hook.php:287 4. WP_Hook->apply_filters(WPFront\URE\Custom_Post\WPFront_User_Role_Editor_Custom_Post_Customize_Caps, Array(1)) /wp-includes/plugin.php:206 5. apply_filters('wpfront_ure_internal_c...', WPFront\URE\Custom_Post\WPFront_User_Role_Editor_Custom_Post_Customize_Caps) /wp-content/plugins/wpfront-user-role-editor-personal-pro/includes/custom-post/class-customize-capabilities.php:60 6. WPFront\URE\Custom_Post\WPFront_User_Role_Editor_Custom_Post_Customize_Caps::instance() /wp-content/plugins/wpfront-user-role-editor-personal-pro/includes/custom-post/class-customize-capabilities.php:70 7. WPFront\URE\Custom_Post\WPFront_User_Role_Editor_Custom_Post_Customize_Caps::init('') /wp-includes/class-wp-hook.php:287 8. WP_Hook->apply_filters(null, Array(1)) /wp-includes/class-wp-hook.php:311 9. WP_Hook->do_action(Array(1)) /wp-includes/plugin.php:478 10. do_action('wpfront_ure_init') /wp-content/plugins/wpfront-user-role-editor-personal-pro/includes/go-pro/class-go-pro.php:88 11. WPFront\URE\Go_Pro\WPFront_User_Role_Editor_Go_Pro->initialize() /wp-content/plugins/wpfront-user-role-editor-personal-pro/includes/ppro/go-pro/class-go-pro.php:96 12. WPFront\URE\PPRO\Go_Pro\WPFront_User_Role_Editor_Go_Pro->initialize() /wp-content/plugins/wpfront-user-role-editor-personal-pro/includes/go-pro/class-go-pro.php:81 13. WPFront\URE\Go_Pro\WPFront_User_Role_Editor_Go_Pro::init('') /wp-includes/class-wp-hook.php:287 14. WP_Hook->apply_filters(null, Array(1)) /wp-includes/class-wp-hook.php:311 15. WP_Hook->do_action(Array(1)) /wp-includes/plugin.php:478 16. do_action('plugins_loaded') /wp-settings.php:403 17. require_once('/www/htdocs/w01174e1/w...') /wp-config.php:112 18. require_once('/www/htdocs/w01174e1/w...') /wp-load.php:37 19. require_once('/www/htdocs/w01174e1/w...') /wp-blog-header.php:13 20. require('/www/htdocs/w01174e1/w...') /index.php:17
May 30, 2020 at 1:35 pm #99706Gerald MenzelSpectatorHi Syam,
Could I simply add
if (!is_object($post_type_object)) return false;
to the top ofis_cpt_user_visible()
inclass-customize-capabilities.php
, or would this cause side-effects? It seems, this would at least stem the flood for now. I did this on my dev server and all seems to work as it should.May 30, 2020 at 3:19 pm #99707Gerald MenzelSpectatorPerhaps I’m reading the code wrong, but shouldn’t line 75 in
class-customize-capabilities-pro.php
be
self::$_instance->register($post_obj);
instead of
self::$_instance->register($post_type_obj);
?
This seems to be connected to the notice problem.May 31, 2020 at 10:45 pm #99737Syam MohanKeymasterHi Gerald,
You are right, it should be $post_obj. Thanks for catching it.
After this change, do you see other notices?
Thanks
Syam
June 1, 2020 at 3:21 pm #99751Gerald MenzelSpectatorThis reply has been marked as private.June 1, 2020 at 11:14 pm #99759Syam MohanKeymasterHi Gerald,
I’ll take a look and let you know.
Thanks
Syam
June 5, 2020 at 11:06 pm #99932Syam MohanKeymasterThis reply has been marked as private.June 8, 2020 at 4:03 pm #99986Gerald MenzelSpectatorHi Syam,
Looks good. Only have it deployed on the dev server right now, but so far didn’t get any new notices. I will push it to the live site with the next maintenance. I’ll keep you posted.
June 8, 2020 at 4:06 pm #99987Gerald MenzelSpectatorThis reply has been marked as private.June 8, 2020 at 11:35 pm #100000Syam MohanKeymasterHi Gerald,
Thanks for the update and help.
I took care of the email address.
Syam
-
AuthorPosts
- You must be logged in to reply to this topic.