Make WordPress Core

Opened 13 years ago

Closed 10 years ago

#8806 closed defect (bug) (worksforme)

Insert Image Button Fails (White Screen of Death)

Reported by: neovita Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0.1
Component: Upload Keywords: needs-patch
Focuses: Cc:


This has been a bug on and off since 2.5. In short after successfully uploading an image via either flash or non flash upload wordpress can't insert the image into the post. This bug even manifests itself in Wordpress.com.

In other words when trying to insert an image the insert page goes to a blank white screen and fails to insert. The work around is to get the image URL and insert the image manually in the HTML tab. I have 5+ blogs with this bug on two different servers. There are dozens of other users on the forum. We would love to help you find a fix for this bug.

Here are some links to forum posts on this issue in Wordpress.org:
http://wordpress.org/support/topic/166082?replies=8#post-734561 (this fix did not work for me but it may help you)

Here is a link to the wordpress.com discussion of the same bug

Attachments (1)

screen-capture-2.png (121.4 KB) - added by neovita 13 years ago.
This is what the White Screen of Death looks like.

Download all attachments as: .zip

Change History (24)

13 years ago

This is what the White Screen of Death looks like.

#1 @azaozz
13 years ago

  • Keywords reporter-feedback added

There used to be a problem with the uploader iframe referencing the main window but it was fixed some time ago (you've noticed that the support threads are over 6 months old).

Trying this in Firefox with Firebug would catch any js errors there, could you post the first error shown.

#2 @benny148148
13 years ago

I have this same error in 2.7...

Using firebug, I receive this scripts.js error (not familiar with how to do this is firebug, so if I'm doing it wrong let me know)

scripts.js (line 6)

$ is not a function                       
$('myForm').addEvent('submit', function(e) {

Is this helpful?

#3 @neovita
13 years ago

Here is a bug from the forum. I'll run my firebug scan soon.

uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLTextAreaElement.selectionStart]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://my.website.org/blog/wp-includes/js/quicktags.js?ver=20081210 :: edInsertContent :: line 349" data: no]

#4 @neovita
13 years ago

On loading the media insert image window I get this error.

Permission denied to call method Location.toString
tb_show("Add an Image", "http://www.thomasumstattd.com/wp-admin/media-upload.php?post_id=-1232062903&type=image&TB_iframe=true&width=640&height=395", false)thickbox...-20080430 (line 230)
tb_init()()thickbox...-20080430 (line 26)
e()jquery.j...ver=1.2.6 (line 11)
e()jquery.j...ver=1.2.6 (line 11)
[Break on this error] if($.browser.safari){//safari needs...p because it will not fire iframe onload

When I try to insert an image I get this error:

Permission denied to get property Window.send_to_editor
[Break on this error] win.send_to_editor('<img src=\"http://ww...alignnone size-full wp-image-565\" />');
media-up...232062903 (line 4)

Or this error:

Permission denied to get property Window.send_to_editor
tb_show("Add an Image", "http://www.thomasumstattd.com/wp-admin/media-upload.php?post_id=-1232062903&type=image&TB_iframe=true&width=640&height=395", false)thickbox...-20080430 (line 230)
tb_init()()thickbox...-20080430 (line 26)
e()jquery.j...ver=1.2.6 (line 11)

Sometimes firebug gives no errors at all. Not sure why.

#5 @doorbells29
13 years ago

I'm getting this error too. I've done countless searching, can't figure out what's going on.

$results.bgiframe(); is not a function

Please see this support post regarding the problem:

#6 @hakre
12 years ago

For all those who have this problem. Please test again on the same server system but against a fresh brand new wordpress setup 2.7.1 with an own database table prefix. thanks.

#7 @neovita
12 years ago

I tested the bug in in a fresh install of WP 2.7.1 and still no luck.

#8 @hakre
12 years ago

With your new install, can you please disable your browsers Cache completely and try again? Loading time might take longer but this will ensure that you accidently won't get outdated / wrong javascript files. The error-mesages you post looks like something messed up in that domain.

I use the webdevelopers toolbar in firefox for that with ease, switching the cache off is just two clicks away then.

#9 @neovita
12 years ago

I actually just fixed the problem by going to general settings and changing http://www.BlogName.com to http://www.blogname.com. Several others users reported the same fix on the forum.

#10 @hakre
12 years ago

looks like a domain policy thingy in javascript. thanks for leaving this info. maybe a filter putting a blogname to lowercase would help here?

Can you provide a link to the forum as well?

#11 @neovita
12 years ago

The forum post is http://wordpress.org/support/topic/180623/page/2#post-1018702

The domain fix is not working for everyone. This problem seems to have many causes.

#12 @Denis-de-Bernardy
12 years ago

  • Component changed from Gallery to TinyMCE
  • Keywords needs-patch added; reporter-feedback removed
  • Owner set to azaozz

#13 @Denis-de-Bernardy
12 years ago

  • Milestone changed from 2.8 to 2.9

#14 @Denis-de-Bernardy
12 years ago

  • Component changed from TinyMCE to Upload
  • Owner azaozz deleted

#16 follow-up: @Denis-de-Bernardy
12 years ago

  • Priority changed from high to highest omg bbq

testing the colorization for report/2

#17 @Denis-de-Bernardy
12 years ago

  • Priority changed from highest omg bbq to normal
  • Severity changed from critical to normal

works great.

#18 in reply to: ↑ 16 @hakre
12 years ago

Replying to Denis-de-Bernardy:

testing the colorization for report/2


Replying to Denis-de-Bernardy:

works great.


I do not understand what you did and what worked great.

#19 @Denis-de-Bernardy
12 years ago

At the time I wrote it, tickets in reports were colored based on their severity. They were changed, per dd32's suggestion, and are now colored based on the need for dev/wrangler attention.

#20 @azaozz
12 years ago

  • Milestone changed from 2.9 to Future Release

No patch.

#21 @Conqueror
11 years ago

  • Version changed from 2.7 to 3.0.1

Can anyone test this solution?

Short description (tiny_mce.js):

  c = t.dom.get('__caret');  // c == null
  r.setStartBefore(c);       // error

#22 @jarkastr
10 years ago

Encountered this issue this past week. It appears that it is induced by the theme I was using. I was using "Beauty & Clean" as my theme. I got the white screen as everyone has spoken about with the same procedure.

Did some investigation on it and it turns out that it was failing because of line 10: in site.com/wp-content/themes/beauty-clean/admin-options/include/rm_script.js. Tried to figure out what was causing the issue within this file, but I couldn't figure it out due to my limited knowledge of wordpress/js.

Instead, all I did was simply rename the rm_script.js file (for use later if something else breaks with the theme), but it would have worked if I deleted the js file instead.

At least in my case, I can say that the blank white screen was induced by my current wordpress theme.

#23 @ocean90
10 years ago

  • Milestone Future Release deleted
  • Resolution set to worksforme
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.