Child Theme Configurator finds errors with plugin

  • Hi there,
    I use the Child Theme Configurator to create and edit my Child Themes, and in a recent check of a theme that had been giving me issues, I came across these:

    Hi there,
    I use the Child Theme Configurator to create and edit my Child Themes, and in a recent check of a theme that had been giving me issues, I came across these:

    Notice: Undefined index: cb_p6_action in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/plugin_core/options_load_reset.php on line 7

    Notice: The called constructor method for WP_Widget in cb_p6_sidebar_author_widget is deprecated since version 4.3.0! Use __construct() instead. in /home/*****/public_html/wp-includes/functions.php on line 3894

    Notice: The called constructor method for WP_Widget in cb_p6_sidebar_site_widget is deprecated since version 4.3.0! Use __construct() instead. in /home/*****/public_html/wp-includes/functions.php on line 3894

    Notice: Undefined offset: 1 in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 111

    Notice: Undefined offset: 2 in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 112

    Notice: Undefined offset: 3 in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 113

    Notice: Undefined offset: 4 in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 114

    Notice: Undefined index: cb_p6_init in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 121

    Notice: Undefined variable: return in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 400

    Notice: Undefined index: cb_p6_frontend_init in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 121

    Notice: Undefined index: cb_p6_action in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 185

    Notice: Undefined index: cb_p6_append_to_content in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 121

    Notice: Undefined index: cb_p6_addstyles in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 121

    Notice: Undefined index: cb_p6_add_styles in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 121

    Notice: Undefined offset: 0 in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 110

    Notice: Undefined index: cb_p6_site_sidebar_widget in /home/*****/public_html/wp-content/plugins/patron-button-and-widgets-by-codebard/index.php on line 121

    Some of them repeat several times. I know they’re Notices, and not Fatal errors or anything, but should I be worried?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author CodeBard

    (@codebard)

    They are not errors, they are PHP notices for people who would make their code more strict (and C compliant).

    PHP by default allows using uninitialized variables, but some people prefer to initialize their variables first, hence there are notices for these in-built to PHP.

    Its for development.

    PHP Notices, Warnings, Error reporting should never be turned on for production servers.

    So, you dont have anything to worry about. There are around ~2500+ installations of the plugin despite the Wp org counter doesnt show it. Everyone seems happy with it, judging from mails and messages coming in.

    You can use the plugin without worries.

    I get the same warnings but it also breaks the whole backend. I needed to remove the plugin manually.

    Plugin Author CodeBard

    (@codebard)

    breaks the whole backend

    If there are these many notices, it naturally would fill out the backend.

    Why are the PHP notices on your production server is on?

    Why does that matter? It is my test server where I test plugins before I use them in production.

    Plugin Author CodeBard

    (@codebard)

    Since you have a production server and a test server, you are either a developer or sufficiently knowledgeable with PHP.

    Notices should not be turned on on production servers, and the notices on your development server wont affect the operation of your plugin or your wordpress on your production server.

    If there are any actual errors or issues that lead to anything in your wp admin becoming dysfunctional, please describe them in sufficient detail.

    +1 – Same error.

    Could you just add a isset() or something before those code error or indicate how we can contribute to fix those errors. It breaks some others plugins.

    Before ask why I am using Error reporting turned on, it is because I need to develop and test plugins and wordpress codes before deploy. So, I can not develop and use your plugin to make basic tests at the same time, without use more than one environment, to see wp and all other plugins working together.

    Plugin Author CodeBard

    (@codebard)

    The new version already has it. When it is published you wont get PHP notices.

    However, in the meantime you can use current version without hesitation. Debugging necessity is at a minimum, since the plugin is OOP code, totally isolated, and it uses only wordpress functions, hooks, filters.

    Plugin Author CodeBard

    (@codebard)

    Update: 2.0.0 fixes all these PHP notices.

    You can update through your WP admin.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Child Theme Configurator finds errors with plugin’ is closed to new replies.

Tags