wp_register_style was called incorrectly

  • Resolved horgster

    (@horgster)


    3 years, 11 months ago

    Hi!

    I have noticed when running my wordpress site in Debug Mode, that I get following error messages generated by the “Login with vipps” plugin:

    ================= Error message in debug mode ====================
    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. This notice was triggered by the login-with-vipps-button-block-editor handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/1/o/oslokiteklubb/www/wp-includes/functions.php on line 5229

    Warning: Cannot modify header information – headers already sent by (output started at /home/1/o/oslokiteklubb/www/wp-includes/functions.php:5229) in /home/1/o/oslokiteklubb/www/wp-includes/functions.php on line 6274

    Notice: WP_Block_Type_Registry::register ble kalt feil. Blokktypen “login-with-vipps/login-with-vipps-button” er allerede registrert. Vennligst se Feils?king i WordPress for mer informasjon. (Denne meldingen ble lagt i versjon 5.0.0.) in /home/1/o/oslokiteklubb/www/wp-includes/functions.php on line 5229
    ================= STOP ====================

    If I disable the plugin, the error goes away.

    I have upgraded WooCommerce to version 4.8 from 4.7.1.
    I was already running these versions of vipps plugin, before upgrading WooCommerce:
    – Checkout with Vipps v1.6.7
    – Logg inn med Vipps v1.1.0

    Can we try to fix this?

    Thanks for your kind support!
    Best Regards
    Horgster

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Iver Odin Kvello

    (@iverok)

    Thank you for the report; I should have spotted that myself.

    The error is in new code supporting Gutenberg blocks; it should not have any other effect other than when Debug mode is on, but I will of course fix it. The new version (v1.1.1) should be live shortly.

    The error does not involve WooCommerce or the payment gateway at all.

    Thread Starter horgster

    (@horgster)

    Happy new Year @iverok

    Thanks for quick response and fix!
    Confirms that this issue is now resolved!

    Best Regards
    Horgster

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