Active
Project:
Wysiwyg
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
12 Jan 2011 at 14:49 UTC
Updated:
23 Mar 2011 at 00:55 UTC
Wysiwyg 2.2 and CKEditor 3.5 (other editors affected?) on D6 seems to be incompatible with mod_pagespeed.
When I activate mod_pagespeed (the version installed by my host Dreamhost), the Wysiwyg module doesn't show any editor buttons as soon as the "Rich editor" is active. After disabling mod_pagespeed, everything goes back to normal.
See also http://drupal.org/node/962946 for a generic discussion on mod_pagespeed and Drupal. Thanks -
Comments
Comment #1
twodThanks for reporting this!
I have not used mod_pagespeed before, so any information you can provide regarding possible causes of the problem and any details about your setup that may differ from a default Drupal+Wysiwyg installation would be really helpful. I won't have time to dig into this myself for a while due to other projects.
Comment #2
sunThis is a feature request. Without further debugging and analysis by the original poster or others, we are going to issue won't fix soon.
Comment #3
threading_signals commentedNo problems with Wysiwyg profile / NicEdit 0.9 as far as I can tell with modpagespeed. Have not tried this for comments. Tested for 6.x. Was tested when logged in as admin. CKEditor 3.4.0.5825 does not work. TinyMCE 3.3.8 does work. All modpagespeed core filters enabled as of 1/18/2011 when tested.
Comment #4
twodAre there any errors when using mod_pagespeed with editors that do not work?
Also, if you didn't already, please make sure to clear caches when enabling/disabling mod_pagespeed, as from the info I've found out so far it'll rewrite and possibly aggregate files sent to the browser. That seems like a very risky thing to do when such complex scripts are involved, IMHO.
Comment #5
threading_signals commentedApache log setting is set to error, and there are no wysiwyg error messages. Caches were cleared after enabling mod_pagespeed, but not after enabling the various editors. Drupal javascript aggregation is disabled, since my site uses ddblock, which doesn't display properly with aggregation on. CKEditor is pretty old, so I would think that the javascript optimization is likely the problem, which a comparison of the code can reveal. It is too early to say whether it is a wysiwyg problem or the editor.
Comment #6
twodCKEditor's first 3.0 release (the rewrite of FCKeditor) is from 2009, TinyMCE 3.0 is from 2007 and I could not find any data for NicEdit other than their site copyright from 2007, so I don't think their age matters much.
The optimization/minificaton could perhaps be the problem since we had to disable Drupal's JS aggregation of ckeditor.js in ckeditor.inc.
Can you perhaps try excluding that one or all of CKEditor's files from processing via
ModPagespeedDisallow?Comment #7
tomass_zutis commentedDisallowing mod_pagespeed for CKEditor and WYSIWYG specific folders appears to have worked for us.
Just added the following in pagespeed.conf :
ModPagespeedDisallow */modules/wysiwyg/*
ModPagespeedDisallow */libraries/ckeditor/*
Not a solution but keeps mod_pagespeed running for the rest of the site until everything else is resolved.
Comment #8
twod#356480: Lazy-load editors includes code which will manually set CKEditor's own base path variables, maybe that's enough?
Comment #9
threading_signals commentedrelease a dev version? lazy loading sounds like a good idea.
Comment #10
3dloco commentedThanks, solution on #7 works for D6, see also #1095908: CKEditor not load when Apache mod_pagespeed is enabled