error message after wp update

  • Resolved ericshew

    (@ericshew)


    3 years, 8 months ago

    Hi there,

    I’m getting this message after uploading to the new version of WordPress. I have isolated the message to the SVG Support Plugin. Please let me know if I can help you resolve it. Thank you.

    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.

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

  • I am also experiencing this exact same notice. When does the Author expect to resolve the notice?

    @ericshew if you’re seeing this on your production site, consider disabling your wp_debug to both remove the notice and improve your site security ongoing. This notice, as with others, is likely not critical to your site. It’s highly likely the plugin author will resolve the issue now that it’s been brought to their attention.

    Plugin Author Benbodhi

    (@benbodhi)

    Hi there,

    Thanks for pointing this out!

    I will be working on this and a handful of other things very soon.

    Just dropping in to say we’re also experiencing this on websites with SVG Support installed.

    Any ETA on when this will be resolved?

    Plugin Author Benbodhi

    (@benbodhi)

    Hi everyone, sorry for the delay, I’m looking into this now.

    Plugin Author Benbodhi

    (@benbodhi)

    Ok, so I have a fresh install of the latest nightly build of WP with my plugin active, debug on, displaying and logging, but I don’t see the warning…

    How can I reproduce this issue?

    Hi @benbodhi,
    I am not certain if this will resolve the issue, but you call on functions/enqueue.php
    wp_localize_script( 'bodhi_svg_inline', 'ForceInlineSVGActive', $force_inline_svg_active );

    and $force_inline_svg_active is as I see is a string (‘true’ or ‘false’)

    Maybe turning this into a single array may fix it.

    • This reply was modified 3 years, 7 months ago by thepiweb.

    Hi @benbodhi,
    To reproduce the warning, I think you might have to also enable Advanced Mode in the Plugin Settings. For me at least, disabling Advanced Mode got rid of the warning…

    Thanks for looking into it, and thank you for the awesome plugin in the first place! I appreciate it must be tough to maintain a plugin over all the changes WordPress is constantly introducing, so Kudos to you!

    Plugin Author Benbodhi

    (@benbodhi)

    Thanks @thepiweb it does look like this is the issue actually. But I want to be able to see the warning to test it to be sure before editing and pushing out the update with this in it. If I can’t reproduce, I’ll go ahead and include it anyway as long as it’s not causing any other issues. Thanks for pointing it out!

    And thanks @schweinedog for your kind words!

    This issue still persists with the latest version.
    Can I provide information for debugging this issue?

    Just confirming that this is still an issue. Any chance of an update soon?

    Plugin Author Benbodhi

    (@benbodhi)

    Update coming this week!

    I’ve been trying to roll in a whole lot of new features, but it’s taking longer than expected, so I might just push out an update with a fix for this in it at least.

    Plugin Author Benbodhi

    (@benbodhi)

    I FINALLY pushed out an update with a fix for this in it. 2.3.19 should have it sorted.

    But please do let me know if you come across any issues by opening a new thread.

    I’ll mark this one as resolved now.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘error message after wp update’ is closed to new replies.