Kenya online casino games real money,Peso888 login.REGISTER NOW GET FREE 888 PESOS REWARDS!

Resolved Josh Levinson
(@joshlevinson)

11 years, 4 months ago

I get the error message GET https://example.com/wp-admin/jquery-1.10.2.min.map 404 (Not Found) in the admin, and a similar message on the front-end, with the exception that the script is attempted to be loaded from /wp-includes/js/ instead.

This intermittently stops a WooCommerce extension I’ve been working on from doing things with javascript. My plugin does not load its own version of jQuery or anything foolish; it doesn’t load or require anything beyond what WordPress and WooCommerce ships with. Sometimes my javascript will work, other times it will not. I cannot reliably reproduce unique situations that cause the two separate results.

I am using TwentyTwelve with only two plugins active – WooCommerce and my own plugin.

This problem did not occur before upgrading to 3.6.

Viewing 15 replies - 1 through 15 (of 22 total)

1 2 →

markfink
(@markfink)

11 years, 3 months ago

+1
I see the same issue. I do not currently need the map for debugging but you are supposed to have it when using the minimized jquery version.
If you do not want to provide the map you have to remove the reference.

benjaminprojas
(@benjaminprojas)

11 years, 3 months ago

I also have this same issue on a brand new install of WP 3.6, no plugins activated, debug mode off, Twenty-Thirteen Theme.

Any way to fix this?

esmi
(@esmi)

11 years, 3 months ago

@benjaminprojas: As per the Forum Welcome, please post your own topic. Posting in an existing topic prevents us from being able to track issues by topic. Added to which, your problem – despite any similarity in symptoms – is likely to be completely different.

benjaminprojas
(@benjaminprojas)

11 years, 3 months ago

Thanks @esmi,

Although my issue is virtually identical, new post: https://www.ads-software.com/support/topic/get-wp-adminjquery-1102minmap-404-not-found-1?replies=1#post-4515759
skoblenick
(@rskoblenick)

11 years, 3 months ago
Simple fix for this:

This error can be ‘fixed’ by removing the comment on line 2 of the jquery. Change the following:
```
/*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license
@ sourceMappingURL=jquery-1.10.2.min.map
*/
```
to:
```
/*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license */
```
See my response on here as well: https://bugs.jquery.com/ticket/14225#comment:2
benjaminprojas
(@benjaminprojas)

11 years, 3 months ago

we shouldn’t need to modify core files in order to fix this, but thanks for the easy fix.

paul.irish
(@paulirish-1)

11 years, 3 months ago

@benjaminprojas the real fix is just to include the .map file in the place it belongs.

download https://code.jquery.com/jquery-1.10.2.min.map and toss it in!

Thread Starter Josh Levinson
(@joshlevinson)

11 years, 3 months ago

See https://core.trac.www.ads-software.com/ticket/24994
wpthemesidea
(@wpthemesidea)

11 years, 3 months ago
Yes rskoblenick, but don’t delete the row just change from :
```
/*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license
//@ sourceMappingURL=jquery-1.10.2.min.map
*/
```
to
```
/*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license
*@ sourceMappingURL=jquery-1.10.2.min.map
*/
```
Thread Starter Josh Levinson
(@joshlevinson)

11 years, 3 months ago

@wpthemesidea – that is incorrect. Please reference https://core.trac.www.ads-software.com/ticket/24994 and the attached patch – https://core.trac.www.ads-software.com/attachment/ticket/24994/24994.patch. The ticket and patch state to remove the line completely.

The real fix is to make the changes as shown on the patch: https://core.trac.www.ads-software.com/attachment/ticket/24994/24994.patch

That is what will be done in the next release.

wpthemesidea
(@wpthemesidea)

11 years, 3 months ago

ok, I see your link, thanks josh

sheriffderek
(@sheriffderek)

11 years, 3 months ago

I’ll have to agree with Paul. Just drop it in. Tada!

Aaron T. Grogg
(@aarontgrogg)

11 years, 3 months ago

@paul.irish & @sheriffderek:
what happens with the next WP upgrade? that files gets nuked again, right?

juanp_1982
(@juanp_1982)

11 years, 3 months ago

I was able to fix it by modifying the second line (as it was suggested) but I added the URL of the file.

/*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license
//@ sourceMappingURL=https://code.jquery.com/jquery-1.10.2.min.map
*/

@aaron T. Grogg: yes, this is just a temporary solution but it’s better than nothing :-p until WP fix it themselve

Thread Starter Josh Levinson
(@joshlevinson)

11 years, 3 months ago

Please stop posting incorrect fixes.

The only correct fix for this, and the one that should be implemented by all in this thread, is the one that will be put into effect by the next WordPress update.

https://core.trac.www.ads-software.com/attachment/ticket/24994/24994.patch

The red is what was, the green is what will be.