If you mean when you access you variables in JS code just by name they are really undefined in JavaScript environment. In order to access variables in JS you need to type as in your example www_vars.whichcats instead of just whichcats Also it’s good to understand how wp_localize_script works. First param is your js file … Read more
Dynamic variable names are unpleasant to work with. A slightly better solution would be to use a single array / object which references each ‘instance’ using an auto-incremented integer. This isn’t a far cry from what you have already, but it keeps all you parameters inside on variable, and accessing a particular property of an … Read more
That’s how the wp_localize_script function works. It prints all the variables before your script is included to make sure that the variables are available to the script. If you want to print the localized variables only one time, but make sure that they are accessible for all three scripts – you can do that by … Read more
The solution is basically from this SO post: When wordpress “localizes” a script, what it does is has php print out <script></script> tags with javascript objects in them that are then accessible within the DOM to the scripts you are “sending” the parameters to. If I understand correctly, the extension of WP_Scripts simple adds a … Read more
Translate string with wp_localize_script()
You should remove trailing slash / from 3rd line. $ait_pfad = plugin_dir_url( __FILE__ ) . ‘/assets/js/ait_buttons.js’; this should be $ait_pfad = plugin_dir_url( __FILE__ ) . ‘assets/js/ait_buttons.js’; wp_plugin_dir() function returns url including a trailing slash (“https://wordpress.stackexchange.com/”) so you should not add it again. Please read wp_plugin_dir() function reference to learn more about this function.
It doesn’t work because you haven’t enqueued your script properly. If the script isn’t printed, neither are the variables set by wp_localize_script. Please read a WP Codex entry on wp_localize_script function. You have to include a path to the script after the handle.
My need was to set different prices in the session and fetch those in my js script. I am using a jquery session plugin to set and get session, but it wasn’t getting session set by php, so I was trying to send variables using wp_localize and set it in the js script. Taking the … Read more
Instead of passing count through wp_localize_script you should just handle the JS logic in JS. For example in JS: var count = document.querySelectorAll( ‘input[name^=”link”]’ ).length; That would get the count of all input elements where the name attribute starts with link. It would be more performant to scope the selector by adding a class to … Read more
I just had this issue myself and was able to fix it by assigning it to the script that required the data and not to “jquery”, example below: wp_localize_script(‘jquery’, ‘vars’, $vars); wp_localize_script( ‘replace-with-your-script-name’, ‘vars’, $vars); To clarify: This would be the same name that was used to identify in wp_enqueue_script() and should match it.