Lost all content

By wideboy-1 on 6 Sep 2006 at 10:40 UTC

Hi, I had a Drupal page setup with minimal content in it. It was on a web server that we have at work. I told one of the technicians to get himself farmiliar with Drupal, so what he done was to reinstal Apache2triad. This inturn cleared all of the work that I had done. My files are still there, but when you try to open the drupal page (on the local host) I get an Apache error message. It looks like all my files have lost there paths, but I want to know how to put them back, so when you browse to the page, you can see my site again?

Many Thanks

Gary

Comments

What is the error messge?

Tresler commented 6 September 2006 at 13:30

What error message did you get?

Sounds like you've just deleted the vhost, but can't be certain of that.

Sam Tresler
http://www.treslerdesigns.com

The Error message

wideboy-1 commented 6 September 2006 at 14:06

This is the error message I get when I try to connect to the site.

---------------------------------------------------------------------------------------------------------------------

Object not found!
The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again.

If you think this is a server error, please contact the webmaster.

Error 404
152.105.116.14
09/06/06 15:04:08
Apache/2.2.0 (Win32) PHP/5.1.2

---------------------------------------------------------------------------------------------------------------------

I know it's something daft that I haven't done properly.

Any help would be grateful

Thanks

Gary...

I'm not a server guy, but

Tresler commented 6 September 2006 at 22:08

Sounds like when he replaced apache, he didn't transfer the configuration file that tells apache to take page requests to your URL (or multiple url's under one name server). Try this simple test, backup your drupal site and remove it from the server. Put a basic .html page in the webroot. If it doesn't resolve then you know that the problem is with Apache not drupal... at which point I might suggest the Apache support channels.

If it does resolve, we can start looking at drupal again. But from what you have written this isn't a drupal problem but a hosting problem.

Sam Tresler
http://www.treslerdesigns.com