41 posts
  • Elite Author
  • Sold between 50 000 and 100 000 dollars
  • Exclusive Author
  • Has been a member for 2-3 years
  • Bought between 10 and 49 items
  • Referred between 50 and 99 users
IshYoBoy says

Seems to be an official WP 3.6 Bug and according to the ticket below:

http://core.trac.wordpress.org/ticket/24994

The solution would be to remove the 2nd line from “wp-includes/js/jquery/jquery.js”. Although this is a very nasty practice (editing core files) it seems this will be the solution i the next update based on the issue tracker above.

changing:

/*! 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 
*/

How are you guys solving the issue on your side?

553 posts Fuel Your Web
  • Elite Author
  • Won a Competition
  • Sold between 250 000 and 1 000 000 dollars
  • Exclusive Author
  • Has been a member for 7-8 years
  • Bought between 50 and 99 items
  • Referred between 200 and 499 users
  • Europe
Pirenko says

After all I’m not alone :)
The weird thing is that I think that this only started yesterday. And it only happens on some Chrome browsers. If you want to turn that off on your browser http://stackoverflow.com/questions/18365315/jquerys-jquery-1-10-2-min-map-is-triggering-a-404-not-found
Anyway, touching any file on the wp-includes is totally forbidden to me.

1466 posts
  • Has been a member for 2-3 years
  • Exclusive Author
  • Sold between 10 000 and 50 000 dollars
  • Bought between 10 and 49 items
  • Referred between 1 and 9 users
  • Croatia
OriginalEXE says

I guess we will have to wait for 3.6.1

322 posts
  • Envato Studio (Microlancer) Beta Tester
  • Most Wanted Bounty Winner
  • Author had a File in an Envato Bundle
  • Has been a member for 5-6 years
  • Sold between 10 000 and 50 000 dollars
  • Exclusive Author
  • Bought between 10 and 49 items
  • Referred between 50 and 99 users
  • Romania
QBKL says

This issue appeared since WP started using jQuery 1.10.2.

This issue does not lie withing WordPress itself, it’s not a WP bug there, but rather in certain plugins calling a jQuery plugin function called jQuery.BlockUI. This function requires jQuery 1.2.3 (or 1.3) in order to work and when the checking happens and matches against 1.10.2, it fails since it would need a leading 0 to make a good comparison like:

1.02.3 < 1.10.2 < 1.2.3

Unfortunately, the only thing that can fix this is making sure all plugins are up to date, particularly the ones that reference this BlockUI function as the newer updated versions of that jQuery plugin have the new comparison model incorporated.

553 posts Fuel Your Web
  • Elite Author
  • Won a Competition
  • Sold between 250 000 and 1 000 000 dollars
  • Exclusive Author
  • Has been a member for 7-8 years
  • Bought between 50 and 99 items
  • Referred between 200 and 499 users
  • Europe
Pirenko says

This issue appeared since WP started using jQuery 1.10.2.

This issue does not lie withing WordPress itself, it’s not a WP bug there, but rather in certain plugins calling a jQuery plugin function called jQuery.BlockUI. This function requires jQuery 1.2.3 (or 1.3) in order to work and when the checking happens and matches against 1.10.2, it fails since it would need a leading 0 to make a good comparison like:

1.02.3 < 1.10.2 < 1.2.3

Unfortunately, the only thing that can fix this is making sure all plugins are up to date, particularly the ones that reference this BlockUI function as the newer updated versions of that jQuery plugin have the new comparison model incorporated.
Allow me to disagree… On a fresh Wordpress install with the twenty thirteen theme I have this issue too. No plugins active…
1074 posts
  • Forum Superstar
  • Most Wanted Bounty Winner
  • Envato Studio (Microlancer) Beta Tester
  • Author had a Free File of the Month
  • Bought between 50 and 99 items
  • Referred between 50 and 99 users
  • Europe
  • Has been a member for 3-4 years
  • Exclusive Author
+1 more
Smartik says


This issue appeared since WP started using jQuery 1.10.2.

This issue does not lie withing WordPress itself, it’s not a WP bug there, but rather in certain plugins calling a jQuery plugin function called jQuery.BlockUI. This function requires jQuery 1.2.3 (or 1.3) in order to work and when the checking happens and matches against 1.10.2, it fails since it would need a leading 0 to make a good comparison like:

1.02.3 < 1.10.2 < 1.2.3

Unfortunately, the only thing that can fix this is making sure all plugins are up to date, particularly the ones that reference this BlockUI function as the newer updated versions of that jQuery plugin have the new comparison model incorporated.
Allow me to disagree… On a fresh Wordpress install with the twenty thirteen theme I have this issue too. No plugins active…

This error doesn’t appear only in Wordpress. I have it in one of my HTML templates that use JQuery 1.10.2. And it doesn’t load any plugins it’s just the library.

4 posts
  • Bought between 10 and 49 items
  • Europe
  • Exclusive Author
  • Has been a member for 3-4 years
lup says

I got rid of this error by going to console “General” settings and disabling “Enable source maps”. I guess chrome needs an update.

84 posts
  • Bought between 1 and 9 items
  • Exclusive Author
  • Has been a member for 2-3 years
  • Indonesia
  • Most Wanted Bounty Winner
  • Referred between 1 and 9 users
  • Sold between 1 000 and 5 000 dollars
hainug says

Hm… It’s really strange, previously i don’t get this kind of error, i just get this an hour ago…

322 posts
  • Envato Studio (Microlancer) Beta Tester
  • Most Wanted Bounty Winner
  • Author had a File in an Envato Bundle
  • Has been a member for 5-6 years
  • Sold between 10 000 and 50 000 dollars
  • Exclusive Author
  • Bought between 10 and 49 items
  • Referred between 50 and 99 users
  • Romania
QBKL says

As lup said, as a developer you can get rid of this error by disabling “Enable source maps” in Chrome settings.

This error apparently only shows up when using the “DevTools” (Inspect Element etc.) as it’s an “interpretation map” for minified code from what I understand.

This means that any regular user/visitor will never be bothered by this error, provided they won’t use the DevTools, and functionality and usability will not be affected.

Clearly not a WordPress bug, no matter how fresh or old the install is, clean or jam-packed with plugins.

332 posts
  • Exclusive Author
  • Sold between 5 000 and 10 000 dollars
  • Has been a member for 4-5 years
  • Europe
  • Envato Studio (Microlancer) Beta Tester
  • Bought between 1 and 9 items
  • Referred between 1 and 9 users
dekciw says

Today I’ve noticed another strange thing.

At the moment, I’m developing few WP themes. I’m using LESS for development (just including less.js) and it seems like Chrome refuses to rerender styles generated by LESS. Basically, I had to add ?ver=<?php echo the_time(); ?> at the end of my styles.less include to see the changes :S Pretty strange. If I remember correctly, Chrome was updated the day before yesterday / yesterday?

Tom

by
by
by
by
by
by