I mistakenly dragged a few modules FROM the /modules dir TO a new dir in /sites/all/modules/ before disabling them in admin.

I THEN went into Administer->Modules and un-checked the modules and selected SAVE.
My site instantly went down and now ALL pages produce the logo and the text:

Page not found
The requested page could not be found.
Powered by Drupal, an open source content management system
followed by the footer.
I moved the moved modules BACK to /modules directory, but nothing has changed. Site still broken. Please help me do something to preserve the hundreds of hours I've put in to building this site.

Thank you in advance for understanding what a bone-head I was, but please help me restore this.

Comments

iansears’s picture

Component: other » usability
iansears’s picture

Component: usability » base system
iansears’s picture

Status: Active » Closed (fixed)

All last night I was getting "Page not Found" when going to http://www.mysite.com/update.php, as I state above.

Once again, this morning, I tried surfing to http://www.mysite.com/update.php
THIS time I got an "Access Denied: you are not logged in kind of thing, with a WONDERFUL Drupal error message suggestion to edit /sites/default/settings.php and change $update_free_access = TRUE; to TRUE, which I did and that allowed me to finally get in.

So far so good. It still does not isolate the root cause of the problem but the good news is I seem to be recovered. For now, and to anyone reading this.... I am going to go with something more like... "Restart the web server to see if that helps."

Strange, strange, strange as can be, and no, I do NOT know what caused this potentially catastrophic delay, but CAN say do NOT place/edit any files up outside of your /sites directory. Get use to, early on, learning how to make ALL of your Drupal changes inside of /sites as an absolute ONLY method of making changes to your Drupal site. Of course, also do not move a module folder unless the module has first been un-checked in it's entirety AND update.php has been run in it's entirety. Even then.....
... ahem.

I'm closing this open issue on my own here. Special thanks go to cog.rusty for the second pair of eyes and forum support of open troubles.
:-)

caspercash’s picture

Many thanks man! I've bumped into this problem early this morning and poof! It just needed to run the update.php

This post is just the same with this one http://drupal.org/node/273407