Tell me more ×
WordPress Answers is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.
up vote 3 down vote favorite

The wordpress crop tool is greyed out for me in Firefox 3.6 (and IE7/8). I have disabled firefox add-ons and tried the solution here:

http://wordpress.stackexchange.com/questions/1597/wordpress-image-editor-not-working-conflict

But this hasn't resolved the issue. Anyone know how wordpress determines whether to enable the crop button?

WP version is 3.0.1

thanks,

share|improve this question
1  
Just realised that the button is disabled until you start dragging. The issue was caused by one of the installed plugins (I think). Just need to figure out which one now. – codecowboy Oct 14 '10 at 9:17

2 Answers

up vote 2 down vote accepted

I'm 99% sure this was caused by the firephp plugin.

share|improve this answer
did deactivating the firephp plugin help you? can you link the firephp plugin? – hakre Oct 14 '10 at 18:29
yep. Link is inchoo.net/wordpress/wordpress-firephp-plugin – codecowboy Oct 15 '10 at 9:39
Then probably the WordPress FirePHP is not smart enough to know when it should shut up (in AJAX requests for example). – Jan Fabry Oct 19 '10 at 14:23
up vote 0 down vote

For anyone else where codecowboy's solution did not resolve the problem try this...

I had a very similar issue to what I think your experiencing over there... After hours and hours of trying to resolve it by coincidence I figured out that the problem was an extra space at the bottom of my custom functions.php file.

So... go and try this. Open your themes main folder and look for your functions.php file. Now go to the very bottom of the page and look for the closing ?> php tag. Now, make sure that there are NO tabs, spaces or line returns after the > including any comments or anything extra.

For me this fixed my issue and I think its a wordpress problem. If your still having the issue check to see if your calling any external php files within your functions.php file and if so do the same steps as listed above. Hope it helps someone.

share|improve this answer
2  
This is not specific to WordPress, but to PHP. You cannot set HTTP headers if you already sent output. Having content outside PHP tags sends this output (as expected), and the crop functionality probably depends on Ajax with specific headers or content (not prefixed with empty lines). The solution is to leave off the closing PHP tag, this is still valid PHP, but prevents these kind of errors. – Jan Fabry Oct 19 '10 at 14:15
Very true... Still it's something I noticed so I figured I would share – NetConstructor.com Oct 21 '10 at 5:41

protected by toscho♦ Nov 9 '12 at 21:12

This question is protected to prevent "thanks!", "me too!", or spam answers by new users. To answer it, you must have earned at least 10 reputation on this site.

Not the answer you're looking for? Browse other questions tagged or ask your own question.