Persistent "warning" message.

  • Hello.

    I have this:

    “Warning: Creating default object from empty value in F:\xampp\htdocs\members\wp-content\plugins\rich-text-sidebar-widget\rich-text-sidebar-widget.php on line 52”

    * * *

    Is there a fix for this?

    I would hate to have to contend with this message displaying on the page when I go to deploy my WordPress installation.

    This is from a “localhost” running copy. I like to preview and “test-drive” my web content before I deploy them.

    https://www.ads-software.com/extend/plugins/rich-text-sidebar-widget/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Dragons Eye

    (@dragons-eye)

    To add:

    Half of the functions will not display.

    I can not pick font size, etc.

    Plugin Author Tim Carr

    (@n7studios)

    An update to remove the warning message will appear soon.

    Meantime, you can ensure that on your live environment you’re not outputting these warnings by ensuring error_reporting is set to E_ALL ^ E_NOTICE:

    error_reporting(E_ALL ^ E_NOTICE);

    Which half of the functions do not display? The widget doesn’t advertise that it provides a “font size, etc” option, and this isn’t included in the WordPress Editor by default.

    Hi, I do have this message too.

    Warning: Creating default object from empty value in /wp/wp-content/plugins/rich-text-sidebar-widget/rich-text-sidebar-widget.php on line 52.

    I could of course ajust my error level, but I wont, because I need to know what’s wrong on my website. An error, even a notice, should be traited, not hidden.

    Thread Starter Dragons Eye

    (@dragons-eye)

    ** Meantime, you can ensure that on your live environment you’re not outputting these warnings by ensuring error_reporting is set to E_ALL ^ E_NOTICE:

    error_reporting(E_ALL ^ E_NOTICE); **

    I like the thought, but I would not recommend this action. I say this because if the folks who develop PHP, one day, decide to make some of those conditions “critical errors”, due to deprecating certain methods, this would become a “stopper” instead of just a “warning”.

    Also, to add to “Lorem Ipsum’s” thoughts above, I would rather not disable the error-level warnings because I use those messages to help me clean up my own code.

    As to the non-implementation of a font-select option, I know this can be done through PHP and HTML on the widget side. This may become a desired feature, based on the feedback from other users. This would have little effect as far as the WordPress install is concerned. It was just a “floating of ideas”. Also, the Tiny MCE portion does, in fact, support font-selection.

    Anyway, I have found the plugin that best suits my purposes. All projects evolve over time, so I look forward to what features will become in future releases. ??

    – Jim

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Persistent "warning" message.’ is closed to new replies.