#50919 closed defect (bug) (fixed)
wp_localize_script( 'jquery') has stopped working
Reported by: | rajeshsingh520 | Owned by: | SergeyBiryukov |
---|---|---|---|
Milestone: | 5.5.1 | Priority: | normal |
Severity: | normal | Version: | 5.5 |
Component: | Script Loader | Keywords: | has-patch commit |
Focuses: | Cc: |
Description
Hi,
In my plugin i user wp_localize_script( 'jquery', 'pi_global_day_time', $return ); to locaive certail variable but after upgrading to 5.5 the varible are not getting localized
Attachments (1)
Change History (20)
#1
@
4 years ago
- Component changed from General to Script Loader
- Keywords reporter-feedback added
- Version set to 5.5
#2
@
4 years ago
Yes the issue was still there, it was infect affecting my other plugins as well
you can reproduct the issue on your end
all the wp_localize_script( 'jquery', 'pi_global_day_time', $return ); localizing with 'jquery' are not getting added in the front end
I fixed it in my plugin by changing it to localize with some other handler script
#4
follow-up:
↓ 6
@
4 years ago
It looks like this happens because wp_localize_script
rewrites jquery
to jquery-core
. In WordPress 5.4, jquery
didn't have a script of its own, and was instead a wrapper for jquery-core
and jquery-migrate
. In #37110, this was changed so that jquery
has a script of its own and doesn't reference jquery-core
at all.
An immediate fix for this would be dropping that rewrite in wp_localize_script
, but it seems like there could be other scenarios where plugins/themes are relying on jquery-core
being actually enqueued. I think it'd make the most sense to change jquery
back to a wrapper for jquery-core
. Particularly since we'll be reintroducing jquery-migrate
in 5.6 when we update to jQuery 3.
#6
in reply to:
↑ 4
@
4 years ago
Replying to TimothyBlynJacobs:
but it seems like there could be other scenarios where plugins/themes are relying on
jquery-core
being actually enqueued. I think it'd make the most sense to changejquery
back to a wrapper forjquery-core
.
This might indeed also helps with a related issue that I noticed today: If a plugin previously had deliberately enqueued jquery-core
(because its JS files didn't need jquery-migrate
), the jquery.js file might now loaded twice (e.g. if another plugin or the theme is also enqueuing it). This leads to issues if other jQuery plugins (like jquery-ui
and similar) are loaded, as the second copy of jquery.js then overrides the extended jQuery JS object again.
Right now, this can be fixed by not enqueuing jquery-core
directly, but it takes away the possibility to deliberately not load jquery-migrate
.
So, indeed, if jquery
could be made a "wrapper" or "alias" for jquery-core
(until the new jquery-migrate
is integrated), the just-described problem and the original ticket problem should be solved.
#7
@
4 years ago
That said, maybe replacing
$scripts->add( 'jquery', '/wp-includes/js/jquery/jquery.js', array(), '1.12.4-wp' );
with
$scripts->add( 'jquery', false, array( 'jquery-core' ), '1.12.4-wp' );
might already be sufficient.
This ticket was mentioned in Slack in #core by audrasjb. View the logs.
4 years ago
This ticket was mentioned in Slack in #core by desrosj. View the logs.
4 years ago
#14
@
4 years ago
- Keywords commit added
Just noting for reference that comment:10 is a bit misleading and the patch doesn't actually revert all of [48323], just restores the jquery
handle as an alias for jquery-core
.
50919.patch looks good to me, since we'll need to add a newer version of jquery-migrate
in 5.6, per #50564, as noted in comment:4.
#15
@
4 years ago
- Owner set to SergeyBiryukov
- Resolution set to fixed
- Status changed from new to closed
In 48890:
#17
@
4 years ago
Per https://travis-ci.com/github/WordPress/wordpress-develop/jobs/378540395, updating the tests to reference jquery-core
.
Welcome and thanks for the report @rajeshsingh520 .
What's the exact problem you're seeing? Are the variables still being passed but just not localized? Or are they missing entirely? Some example code would be a great help.