• Resolved jleung1994

    (@jleung1994)


    Notice: WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see Debugging in WordPress for more information. (This message was added in version 5.7.0.) in C:\xampp\htdocs\website\wp-includes\functions.php on line 5663

Viewing 6 replies - 1 through 6 (of 6 total)
  • Zohaib

    (@zohaibayub85)

    Hi,

    We are unable to reproduce the issue on our end. First can you please make sure you are using the latest version of the plugin. Secondly, I see you are using Xamp, we have not tested our plugin with Xamp. I suggest you try it on a live server.

    Plugin Contributor Pablo Pacheco

    (@karzin)

    Hi @jleung1994

    I hardly believe this notice is coming from our plugin because we’re not even using the localize function. Please check if it’s not coming from any other plugin.

    Thread Starter jleung1994

    (@jleung1994)

    The notice only appears when this plugin is activated. I deactivated other plugins and the message still shows when this plugin is activated.
    Also warning when I’m updating other woocommerce related plugin

    Warning: Trying to access array offset on value of type null in C:\xampp\htdocs\website\wp-content\plugins\woo-confirmation-email\woocommerc-confirmation-email.php on line 281

    Plugin Contributor Pablo Pacheco

    (@karzin)

    Hi @jleung1994 ,

    Maybe there was a confusion about the plugins.

    Our plugin is “Email Verification for WooCommerce”
    https://www.ads-software.com/plugins/emails-verification-for-woocommerce/

    The plugin you just mentioned on the warning is “User Email Verification for WooCommerce”
    https://www.ads-software.com/plugins/woo-confirmation-email/

    Can you please confirm it?

    Thread Starter jleung1994

    (@jleung1994)

    I got confuse with the 2 plugins. I’ll try this plugin later. The other one didn’t update, which should be the reason for the error.

    Plugin Contributor Pablo Pacheco

    (@karzin)

    Sure, no problem ??

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