#5136 closed defect (bug) (fixed)
Post enty box not active in IE7 using TinyMCE
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | 2.5 | Priority: | normal |
| Severity: | normal | Version: | 2.2.2 |
| Component: | TinyMCE | Keywords: | |
| Focuses: | Cc: |
Description
Hi all. When trying to post a new entry using IE 7.0.5, one of our users cannot get the cursor active in the post entry box. This problem persists even if we switch to "code" mode. But corrects itself if we turn off the rich text editor on the profile page. I have been able to replicate this on my own Windows machine.
IE throws a Javascript error, as follows:
Line: 125
Char: 22
Error: 'this,contentWindow.document' is null or not an object
Code: 0
URL: "URL-of-the-blog/wp-admin/post-new.php
We have experienced this problem before on different versions of Wordpress.
Change History (6)
#2
follow-up:
↓ 3
@
19 years ago
I notice the WordPress version is 2.2.2, do you also see this issue with WordPress 2.3?
#3
in reply to:
↑ 2
;
follow-up:
↓ 4
@
19 years ago
Replying to foolswisdom:
I notice the WordPress version is 2.2.2, do you also see this issue with WordPress 2.3?
I'd like to answer that, but for the first time ever, I'm having troubles installing the latest WP vesion. I'll keep trying and report back.
#4
in reply to:
↑ 3
@
19 years ago
Replying to mbaze:
Replying to foolswisdom:
I notice the WordPress version is 2.2.2, do you also see this issue with WordPress 2.3?
Yes, it still happens on 2.3. A clarification: The error message cited above is from trying to enter the post field using the "code mode. This is the error when in "visual" mode:
Line: 184 Char: 290 Error: Access denied Code: 0 URL: "URL-of-the-blog/wp-admin/post-new.php
#5
@
18 years ago
- Milestone 2.6 deleted
- Resolution set to fixed
- Status changed from new to closed
Both errors seem related to TinyMCE trying to load. There's a known bug/feature in IE7 that returns "Access Denied" js error on certain AJAX calls. Relaxing the security setting for the blog site would usually fix it. Also this seems fixed in WordPress 2.5, TinyMCE 3.
Running IE 7.0.6 I haven't seen this issue. Does that version resolve this issue?