I slid a couple of modules FROM the /modules dir to the /sites/all/modules dir and my site went down. Now ALL pages say "Page Not Found".

A couple of the modules that I moved were CCK and Views.

Any ideas?

Comments

silverwing’s picture

if you put them back, does the site load properly?
~silverwing

_____________________________________________
Land of Midnight | MisguidedThoughts | showcaseCMS

iansears’s picture

Well, of course I immediately did just that when the problem occurred, but no, after draging he modules back to the /modules/ dir the site continued to (continues to) say "Page Not Found" on ALL pages.
Home Page = "Page Not Found"
mysite.com/node/3 = "Page Not Found"
mysite.com/admin = "Page Not Found"
mysite.com/update.php = "Page Not Found"

heeelp

silverwing’s picture

EDIT: can you even get into Admin?

You change to a default theme (garland, chameleon, something you haven't used) go you still get those errors?

update.php should not be affected by this. Did you accidentally remove other files?

This is just weird.

~silverwing

_____________________________________________
Land of Midnight | MisguidedThoughts | showcaseCMS

iansears’s picture

As I said, ALL pages say Page Not Found.
Cant get into admin
cant specify a clean url
cant use a bookmark
EVERY attempt to get into a page says Page Not Found.

Edit: I am using Garland and have been for days.
I did not remove any files. just slid them over, and slid them back
While slid over to /sites/all/modules, I THEN went into administer -> modules and unchecked the ones that I had slid (I know, I know) and when the Page Not Found error began I immediately slid them back.

criznach’s picture

iansears’s picture

criznach,
Same result. Thanks for the suggestion.
What I see is the same thing every time.
Here, I'll try to post a screenshot:

drupal_841’s picture

I had the same problem, the issue was my sql database was not uptodate so, all i did was to run the update.php page and vola! the site is back, So make sure you run your updates.
Cheers
Greenopolis

kevinquillen’s picture

Shouldn't have put them in the root.

Can you check your access/error logs for more information? Seems like something else is going on here.

Then again, if you created a lot of pages as a view, you would get Page Not Found..

===========
read my thoughts

cog.rusty’s picture

Who says "Page not Found"? Drupal or Apache? Can you tell? Try:

http://example.com/index.php
http://example.com/modules
http://example.com/blah

Do you see any difference in the error message between these pages?

Can you describe exactly what it says and how it looks? Does the error page contain any links or have any style?

iansears’s picture

cog.rusty,
None of those experiments triggered anything in the apache error log except the attempt to call:
http://www.mysite.com/modules
...which triggered the following in the error_log:
[Sun Jun 22 06:57:25 2008] [error] [client 127.0.0.1] Directory index forbidden by Options directive: /Users/**myaccount**/Sites/**morePriveEditedDirName**/drupal/drupalv62i1/modules/
(Those asterisked dir name I just obscured for this forum posting for my privacy, is all)
Also note: the dir named drupalv62i1 is the root dir of this drupal instance. It runs fine from there and the long path thing before it is not the problem.

cog.rusty’s picture

Try http://www.example.com.com/update.php
Does it work? If it works, does it give you any error messages?

Then try to temporarily rename Drupal's .htaccess file to .htaccess-OFF to see if it helps to display at least the http://www.example.com.com/index.php page.

iansears’s picture

cog.rusty,
All last night I was getting "Page not Found" when going to http://www.mysite.com/update.php, as I state above.
But ever humble as I can be I did it again to follow your suggestion.
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.

THANK you cog.rusty, and all for looking into this issue. I so hope it will somehow help others down the road.
Closed.