Title: WP_Scripts localize called incorrectly
Last modified: April 6, 2021

---

# WP_Scripts localize called incorrectly

 *  [brittanyio](https://wordpress.org/support/users/brittanyio/)
 * (@brittanyio)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/wp_scripts-localize-called-incorrectly/)
 * We are getting this error on our site that has been tracked down to this plugin:
 * 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.

Viewing 1 replies (of 1 total)

 *  Plugin Author [kgblocalize](https://wordpress.org/support/users/kgblocalize/)
 * (@kgblocalize)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/wp_scripts-localize-called-incorrectly/#post-14285060)
 * Hi brittanyio,
 * Sorry that you are having this problem. Would it be possible to let me know on
   which website you are having this problem?
 * Thanks,
    Kirk Bobash [Signature removed by moderator per [forum guidelines](https://wordpress.org/support/guidelines/#do-not-spam).]
    -  This reply was modified 5 years, 1 month ago by [Yui](https://wordpress.org/support/users/fierevere/).
      Reason: signature dropped

Viewing 1 replies (of 1 total)

The topic ‘WP_Scripts localize called incorrectly’ is closed to new replies.

 * ![](https://ps.w.org/localizejs/assets/icon-256x256.png?rev=2744226)
 * [Localize - Website Translation Integration](https://wordpress.org/plugins/localizejs/)
 * [Support Threads](https://wordpress.org/support/plugin/localizejs/)
 * [Active Topics](https://wordpress.org/support/plugin/localizejs/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/localizejs/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/localizejs/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [kgblocalize](https://wordpress.org/support/users/kgblocalize/)
 * Last activity: [5 years, 1 month ago](https://wordpress.org/support/topic/wp_scripts-localize-called-incorrectly/#post-14285060)
 * Status: not resolved