opsidao
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: 2.8 upgrade killed visual editor@azaozz that was it for me, I was missing the file wp-tinymce.js.gz. I gzipped the js, reenabled compression on post.php and all seems good.
thanks!
Forum: Fixing WordPress
In reply to: 2.8 upgrade killed visual editorNow, it seems related to compression. In file wp-admin/includes/post.php there’s a line like this:
$zip = $compress_scripts ? 1 : 0;Don’t ask me why, but if you change that line to look like this (Wich is a dirty way to disable script compression):
$zip = $compress_scripts ? 0 : 1;then the visual editor starts working again 😉
But remember that:
- this will only fix the problem if you see in your firebug that the request to wp-tinymce.php has “c=1” in it
- this is a dirty piece of shit, it is not a definitive solution, just a temporary workaround
Forum: Fixing WordPress
In reply to: 2.8 upgrade killed visual editorI got the same problem here, the visual editor just went away after upgrading from 2.7.1 to 2.8 (thankfully this is not a production or even public site).
I’ve done some reseach with firebug and the problem seems to be related with the version that is requested from wp-includes/js/tinymce/wp-tinymce.php , in my case, looking at the network traffic I see this request:wp-includes/js/tinymce/wp-tinymce.php?c=1&ver=3241-1141
which is returning nothing, but if I change that to be
wp-includes/js/tinymce/wp-tinymce.php?c=2&ver=3241-1141
then it returns the needed javascript for tinymce.
I looked at the source for wp-admin/post-new.php and it’s using the wp_enqueue_script function to load the ‘editor’ scripts.
Digging a bit, that function is defined on wp-includes/functions.wp-scripts.php….
And there’s where I’m right now, I’ll let you know as soon as I know more.