#3572 closed defect (bug) (fixed)
IIS RTE not loading in 2.1
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 2.2 | Priority: | high |
Severity: | normal | Version: | 2.1 |
Component: | Administration | Keywords: | tinyMCE RTE rich text editor IIS dev-feedback |
Focuses: | Cc: |
Description (last modified by )
tinyMCE is not loading in both my installations of 2.1.
ENV: IIS, with MySQL 4.1.21-community-nt
PHP Version 4.3.1 CGI/FastCGI
2.1alpha3: http://archgfx.net/sandbox
2.1beta2: http://archgfx.net/wordpress
Screenshot: http://picasaweb.google.com/sunburntkamel/Screenshots/photo#5019191130067666034
Attachments (2)
Change History (29)
#2
@
18 years ago
- Description modified (diff)
- Summary changed from RTE not loading in 2.1 to IIS RTE not loading in 2.1
#3
@
18 years ago
firebug shows the following errors:
invalid flag after regular expression
(http://archgfx.net/wordpress/wp-includes/js/tinymce/tiny_mce_gzip.php?ver=20061113 line 121)
tinyMCE is not defined
(http://archgfx.net/wordpress/wp-includes/js/tinymce/tiny_mce_config.php?ver=20061113 line 35)
tinyMCE is not defined
(http://archgfx.net/wordpress/wp-admin/post-new.php line 201)
#7
@
18 years ago
looking at:
http://archgfx.net/wordpress/wp-includes/js/tinymce/tiny_mce_gzip.php?ver=20061113
i see the last line refers to ob_gzhandler, which doesn't work/exist on my server. is there some setting that should be flipped to turn it off?
#8
follow-up:
↓ 9
@
18 years ago
You have the zlib extension installed, so ob_gzhandler() should exist. The error suggests that ob_gzhandler() is being run twice. If you have plugins activated, check to make sure none of them invoke ob_gzhandler(). Failing that, if you can edit your php.ini, try setting output_buffering to Off. It is currently 4096. I don't think that should matter since zlib.output_compression is off, but it won't hurt to check.
#9
in reply to:
↑ 8
@
18 years ago
Replying to ryan:
You have the zlib extension installed, so ob_gzhandler() should exist. The error suggests that ob_gzhandler() is being run twice. If you have plugins activated, check to make sure none of them invoke ob_gzhandler(). Failing that, if you can edit your php.ini, try setting output_buffering to Off. It is currently 4096. I don't think that should matter since zlib.output_compression is off, but it won't hurt to check.
alright, last time i had trouble with ob_gzhandler() loading twice, i deleted it from functions.php, and that fixed it. i can't edit php.ini myself, but i've asked my host, and i'll let you know.
#11
@
18 years ago
i added:
ini_set('output_buffering', 'off');
to /sandbox/wp-config.php, still nothing.
#13
@
18 years ago
fwiw, both installs are running 2.1.0, and they still don't work.
if having admin access would be helpful, drop me an email:
http://www.archgfx.net/aspnet_client/obfuscated1.html
#15
@
18 years ago
i deleted it out of
/wp-includes/functions.php
like this, but no, it didn't help. is there someplace else i should delete it?
#18
in reply to:
↑ 17
@
18 years ago
Replying to andy:
I missed a directory there but I think you can find it :)
alright, i deleted everything from line 132 to 137, now it works.
#19
@
18 years ago
I was having the exact same problem. I commented out the entire Check for gzip header or northon internet securities section from 131 - 145.
That led to out of memory error to which I added:
ini_set("memory_limit","12M");
after the first require. It now works. I'm not sure I fixed anything but if memory serves me correctly from my old C programming days leaking memory is never good but if you are going to leak assign a big buffer to your array... ;) That way your problem will happen much later and may never crop up if the process gets terminated/reset before you run out of memory.
#20
@
18 years ago
- Keywords dev-feedback added
- Milestone changed from 2.1.1 to 2.1.2
Reporters problem seems fixed by the "hack".
Is there a way to test for this issue and include a permanent fix in core or is this so rare that we'll just learn to live with it?
#26
@
18 years ago
- Resolution set to fixed
- Status changed from new to closed
Excellent, we will call this fixed then.
FWIW, my client is windows XP SP2, and it occurs in both FF 2 and IE 7