TinyMCE failing when using ModPagespeed

[franmaWp]

TinyMCE Stops working correctly When using ModPagespeed module.

TypeError: wp.svgPainter is undefined

I needed to edit this file to fix the issue:

/wp-admin/js/svg-painter.js

[lukecavanagh]

Is this on Apache or NGNIX?

[franmaWp]

Replying to lukecavanagh:

Is this on Apache or NGNIX?

It is in Apache.

[azaozz]

Sounds like the svg-painter.js file is not loaded for some reason. That triggers a JS error that prevents TinyMCE from working properly.

Assuming you're running from /src or have SCRIPT_DEBUG defined, does that happen when you run from /build or set SCRIPT_DEBUG to false?

[franmaWp]

svg-painter.js is loaded correctly but when this code from svg-painter.js is executed:

$(document).ready( function() {
		// detection for browser SVG capability
		if ( document.implementation.hasFeature( 'http://www.w3.org/TR/SVG11/feature#Image', '1.1' ) ) {
			$( document.body ).removeClass( 'no-svg' ).addClass( 'svg' );
			wp.svgPainter.init();
		}
	});

i get "TypeError: wp.svgPainter is undefined" then many Js admin functionalities stop working. To solve the problem i move that script out of wp.svgPainter Object.

To test this i am having SCRIPT_DEBUG=true

Any suggestions? thanks.

[desrosj]

I found this one in a report of tickets missing a milestone.

Quite a bit has changed in the last 8 years, but I've gone and done some testing to try and replicate this.

To test, I am using the local Docker environment in wordpress-develop with today's state of trunk and I've replaced the standard nginx container with one containing the PageSpeed plugin. It's configured, confirmed on, and I'm seeing the caching happen in the configured folder.

TinyMCE is no longer the default experience for WordPress, so I've gone and activated the ​Classic Editor plugin. Following this, I've been unable to encounter any breaking of TinyMCE.

It looks like TinyMCE was version 4.3.10 in WordPress 4.5.2 (see [37253]). The version currently included in Core is 4.9.11.

svg-painter has also undergone a minimal number of changes since:

• Some jQuery compatibility updates ([50420,50547])
• Old code targeting IE9 was removed ([58997]).

Since I cannot find any other reports of this issue here on Trac in the 8 years since this last saw activity, I'm going to close this out as worksforme. Whatever was causing this seems to have been a configuration issue specific to @franmaWp's server, or a bug that has since been fixed through one of the many changes since this report was submitted.