manager has white screen

hi, i have recently moved my modx site from a staging url to the production url. the site itself is working properly, however when trying to access the manager, i get the white screen of death. nothing is printing to the error logs. i’ve scoured the forums for those who have similar issues and i can confirm that the paths in core/config/config.inc.php are correct. i can also confirm that the steps in this post were followed: http://rtfm.modx.com/display/revolution20/Moving+Your+Site+to+a+New+Server

in firefox only, the manager loads, however if i try to edit a document - nothing shows up for the editor. in chrome and safari, it is a white screen.

any help is appreciated. thank you!!

i forgot to say, i am using:

MODx Revolution 2.0.4-pl2
PHP version 5.2.6

Did you actually configured the path in mysqlDB correctly, too?
Did you empty your cache folder (server, browser)?
file permissions are correct, too?

You could also give a look here:
http://modxcms.com/forums/index.php/topic,59881.msg340784.html#msg340784

thanks, clearing the cache worked partially. i am able to see the manager, log in and see my files on the left side, however if i click on a resource to edit, it doesn’t populate with the content. weird. the path in the db for workspaces is correct as well.

I had a similar problem to yours. If you have set up Friendly URLs, double-check that your .htaccess file settings are compatible with your host. Their tech support and some Googling might be able to help you determine this.

thanks for your response, i am not using friendly urls though

The manager white screen issue came up for me while I was using the manger on a site that otherwise had been working fine. I was saving a resource, not doing anything fancy or special, and suddenly everything went white. For others who experience this the solution mentioned previously worked for me - clear the cache directory (core/cache). MODX will rewrite everything that needs to be in that directory.

There’s a bug related to the cache that’s fixed in 2.0.8, so upgrading might solve your problem.