Envira Lite error in WP 5.7 – “WP_Scripts::localize was called incorrectly”

  • Hello,
    I’m using Envira Gallery Lite v.1.8.3.4.
    I just updated to WP 5.7 and am now seeing a

    ” WP_Scripts::localize was called incorrectly”

    error on all front-end pages & posts that contain an Envira gallery.

    The error text appears either just above the gallery or, in one case, at the top of the page. The galleries themselves are displaying correctly.

    Disabling the Envira plugin removes the error, and also the gallery.

    Is this something Envira developers are aware of?
    Is it caused by the plugin, or somewhere else?
    Would rolling back Envira to an earlier version resolve this?

    Here is the full front-end error message:

    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 /homepages/44/d153290873/htdocs/wordpress/wp-includes/functions.php on line 5313

    Thank you very much.

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

  • Hi @joesciacca

    Thanks for contacting us!

    I apologize for the trouble. My team and I haven’t been able to replicate this error on our end yet. Can you please contact us at https://enviragallery.com/account/support/ so we can further investigate this for you?

    For the time being, we do recommend disabling WP_DEBUG on your production site.

    Looking forward to getting this resolved!

    @bmilligan15 I have the same error.

    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 /wp-includes/functions.php on line 5313

    This is with WP_DEBUG enabled. I suggest testing with the latest version of WordPress.

    Moderator James Huff

    (@macmanx)

    Hi there @designextreme I see you reported this thread to the moderators. Please note that we are just the folks who enforce the rules around all of www.ads-software.com.

    Reporting to moderators doesn’t get any faster support, instead it just kind of attracts attention from folks whose radar you probably don’t want to be on. ??

    If you really do need a moderator, please add a reply letting us know why before you hit the report button.

    Otherwise, please hang in there for the plugin’s support to reply when they can.

    @macmanx Thanks, there is no way for me to set it to “Unresolved”. Please can you either change the status or just leave it for now. It wasn’t meant to nag the plugin developers into action.

    Moderator James Huff

    (@macmanx)

    Only the original poster or the plugin’s support team can toggle that, so it was set by someone who does consider this resolved.

    I recommend that, instead of posting here, you follow the instructions in the plugin supporter’s reply.

    @macmanx Ok.

    @bmilligan15 I’ve sent a direct support email a couple days ago.

    Please can you release a fix for this?

    I’m using the free version 1.8.3.4 and the issue remains on 7-7-2021. I’m considering disabling the plug-in but really don’t want to. This is NOT resolved !!

    I am also getting this error on the latest version of Envira. Can anyone help? How do we submit a new ticket as I see this one is marked “Resolved” but the issue is NOT RESOLVED!

    Help, please don’t make me switch to a lesser gallery solution.

    +1
    I can confirm this issue has not been resolved with WP 5.8 as of September 2021

    • This reply was modified 3 years, 2 months ago by echodev.
    • This reply was modified 3 years, 2 months ago by echodev.
    Simon

    (@simonmaddox)

    Is anyone looking at this issue? It’s definitely still there and I can’t see how this thread can be marked ‘Closed’

    Thread Starter joesciacca

    (@joesciacca)

    I’m the original poster.
    Seeing that this is still an active issue with many people, I have changed the status to unresolved. I don’t know the protocols of the support group, so I hope it is OK to do that.
    I wasn’t able to turn off debugging per the developer’s suggestion, and didn’t feel I could provide any further details beyond the error message, so I didn’t submit the report to the support link. Perhaps the developer marked it resolved when I didn’t submit to the link.
    After a few days I disabled the plugin and found a work-around until a fix was released. I would love to see a fix.

    @bmilligan15 Issue appears to be plugins/envira-gallery-lite/includes/global/shortcode.php lines 221-223 where the third parameter to wp_localize_script() is not an array like it should be.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Envira Lite error in WP 5.7 – “WP_Scripts::localize was called incorrectly”’ is closed to new replies.