Notice: wp_register_style was called incorrectly

  • Hi,
    Reporting possible bug…

    With Debug mode on, and Change DB Prefix activated, I get the following messages on every page load, including front end and admin dashboard. When I deactivate CDBP, the notices go away.

    Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /Users/***/wp-includes/functions.php on line 3245

    Notice: wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /Users/***/wp-includes/functions.php on line 3245

    Thanks!

    https://www.ads-software.com/plugins/db-prefix-change/

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hello,

    It’s a bug, the developper should enqueue the plugin scripts using wp_enqueue_scripts, or admin_enqueue_script action hooks…

    I like this plugin’s simplicity, I’d be happy if developer could fix these small but annoying issues.

    I came here to report the bug, but it’s already done.

    Just in case someone needs the tip: activate the plugin, use it and the deactivate.

    Please developer: ask us a hand if you have no time for fixing it. It would be a waste if everybody would fix the plugin on his own and not be able to redistribute the patch.
    I took a look: I think the problem lies in lines 12-17 of db_prefix.php; I think they should be wrapped in a function and that function enqueued at the correct hook (I know the theory but never did it myself).

    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Notice: wp_register_style was called incorrectly’ is closed to new replies.