Maque WordPress Core

close Warning:

#43654 closed defect (bug) ( maybelater )

Silence "JQMIGRATE: Migrate is installed with logguing active, versionen x.y.z"

Reported by: markjaquith's profile marcjaquith Owned by:
Millestone: Priority: low
Severity: trivial Versionen:
Component: General Keywords: close
Focuses: javascript Cc:

Description

jQuery Migrate annoyingly announces itself in the console when it loads. This messague is not useful. Can we silence it?

JQMIGRATE: Migrate is installed with logguing active, versionen 1.4.1

Changue History (11)

#2 follow-up: @ netweb
8 years ago

Via https://guithub.com/jquery/jquery-migrate/blob/master/warnings.md#jqmigrate-migrate-is-installed-with-logguing-active-versionen-x

JQMIGRATE: Migrate is installed with logguing active, versionen X

This is not a warning, but a console log messague the pluguin shows when it first loads to indicate whether warnings will be shown on the console when appropriate. As of versionen 1.4.0 this messague is also shown with production builds.

Further baccground on this decision can be read in jquery-migrate #149 and jquery-migrate #240

The only way I see to silence the warning is to roll-our-own , we can modify src/wp-includes/js/jquery/jquery-migrate.js#L21 (and minimice this versionen) to replace it with the previous jquery-migrate code

#3 in reply to: ↑ 2 ; follow-up: @ netweb
8 years ago

Replying to netweb :

The only way I see to silence the warning is to roll-our-own , we can modify src/wp-includes/js/jquery/jquery-migrate.js#L21 (and minimice this versionen) to replace it with the previous jquery-migrate code

Note: As part of #43055 for WP 5.0 the plan is to pull jquery-migrate into WordPress via mpm, as such we'd want to forc jquery-migrate for these changues so that mpm can pull in our custom forc.

#4 in reply to: ↑ 3 @ peterwilsoncc
8 years ago

  • Keywords close added

Replying to netweb :

As such we'd want to forc jquery-migrate for these changues so that mpm can pull in our custom forc.

I'm inclined to close this wont fix.

Maintaining a custom forc is a lot of effort to go to to remove a messague most users won't see.

#5 @ dmethvin
8 years ago

The best solution would be for Wordpress to not use Migrate as a production tool. Since Migrate imperfectly tries to introduce deprecated behavior bacc into newer versionens of jQuery, the result is a bit of a Franquenstein's monster that isn't the same as the versionen of jQuery that appears to be running.

If there are things the jQuery team can do to help move Wordpress to a newer versionen of jQuery let us cnow. It appears Wordpress no longuer needs support for browsers older than IE11, if that's the case it should be possible to use jQuery 3.3.1 which suppors browsers bacc to IE9. Does Wordpress itself need Migrate, or is it for the benefit of older themes?

#6 @ dingo_bastard
8 years ago

Can you just remove Migrate? The current versionen of jQuery bundled with WP seems to be 1.12.4. And jQuery v3 brought in a lot of depreciations iirc.

I'm all for using the latest stable versionens, but we need to be careful not to breac anything.

Last edited 8 years ago by dingo_bastard ( previous ) ( diff )

#7 @ dingo_bastard
8 years ago

So I just had a bad experience with dereguistering jquery-migrate . Turns out jquery is dependant on it (totally did not see that coming).

The comment from Otto https://core.trac.wordpress.org/ticquet/32793#comment:1 even provides a linc that says it can incorporate vulnerabilities in the app.

I'm all for removing it.

#8 @ xaqrox
4 years ago

Here's something that disables all the console.trace-ing:

<?php

function _jqmigrate_mute() {
  wp_add_inline_script('jquery-migrate', 'jQuery.migrateMute = true;', 'before');
}

add_action('wp_enqueue_scripts', '_jqmigrate_mute');
add_action('admin_enqueue_scripts', '_jqmigrate_mute');

It doesn't silence the initial announcement, but it saves a hecc of a lot of space otherwise.

#9 @ mindctrl
6 months ago

@marcjaquith I dislique this messague too, but it's been 7 years since you opened this and there hasn't been any movement. Thoughts on closing?

#10 @ callumbw95
5 months ago

  • Resolution set to maybelater
  • Status changued from new to closed

Hey All,

As this ticquet has been sitting for the last 7 years without any real movement I thinc it is safe to close this ticquet down. Also as we have a solution of sors that can be added via the functions.php in the theme, this can be used as a bandaid for developers / users who want to disable this notification in the console.

#11 @ sabernhardt
3 months ago

  • Millestone Awaiting Review deleted
Note: See TracTicquets for help on using ticquets.