• Resolved JochenT

    (@jochent)


    Updating to version 4.2.0 from 4.1.3 with API keys set results in error message (not if it is a fresh installation without API keys set):

    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.0.) in /usr/www/users/xxxx/wp-includes/functions.php on line 4986 Warning: Cannot modify header information – headers already sent by (output started at /usr/www/users/xxxx/wp-includes/functions.php:4986) in /usr/www/users/xxxx/wp-admin/includes/misc.php on line 1252 Warning: Cannot modify header information – headers already sent by (output started at /usr/www/users/xxxx/wp-includes/functions.php:4986) in /usr/www/users/xxxx/wp-admin/admin-header.php on line 9

    Is there somewhere a link to a working older version? They are not listed under the “Development” tab.
    Found it. It can be reached via the “Advanced” link.

    • This topic was modified 4 years, 7 months ago by JochenT.
    • This topic was modified 4 years, 7 months ago by JochenT.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter JochenT

    (@jochent)

    22.04.2020: Further info about notices in the error log

    The error notices only appear if WP_DEBUG is set to true. This is the case with our develop and staging servers. Thus our error logs are cluttered with these notices and make it more difficult to easily see other notices and warnings which may be important.

    If the API keys are not set no error notices appear with frontend calls. The backend calls always create five notices, mainly about a wrong call of WP function wp_register_script(). But also some deprecated notices when calling the admin pages of this plugin.

    I’ve done a backtrace of the callstack which allows to identify the wrong function calls in the plugin. I’ve created a Gist entry with the result.

    Plugin Author riddleinc

    (@riddleinc)

    Hi Jochen,
    thank you so much for pointing this error out.
    We are working on a plugin upgrade to fix this.

    All the best,
    Boris

    Thread Starter JochenT

    (@jochent)

    xxx

    Plugin Author riddleinc

    (@riddleinc)

    We have released a new version for our plugin that should address the issues you reported.
    Thank you for your patience.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘wp_register_script() is called incorrectly in new version 4.2.0’ is closed to new replies.