This topic is locked
[SOLVED]

 Error 404

6/9/2007 6:11:21 AM
PHPRunner General questions
A
andyjames author

Hi I have just downloaded the latest version upgrading from PHPRunner4.0 build 258 to build 262 and 265.

As a result of doing so, I can no longer see any of my files, I just get the error 404 message (This error (HTTP 404 Not Found) means that this program was able to connect to the website, but the page you wanted was not found. It's possible that the webpage is temporarily unavailable. Alternatively, the website might have changed or removed the webpage.)
I am running phprunner locally on Apache/2.0.59 (Win32) , php version 5.2.0, MYSQL 5.0.27-community-nt

Localhost paths are all correct and work for older build versions of PHPRunner and other programs, so there isn't a problem with my configuration (or at least I don't think so).
Has anything changed since build 258 that might have caused this to happen? Anyone else experiencing problems?

Thanks for your feedback in advance!

A
andyjames author 6/9/2007

In danger of talking to myself now!! but I think this is something to do with the definition of the output directory.

Even though the paths were correct it didn't work.

BUT if I created a new alias "Select new virtual directory from list" then it works.

Not sure whether this is a bug or whether I am the bug!??

admin 6/10/2007

Andy,
nothing that affects output/virtual directories has changed lately.
Give me more info about this issue.
What directory you select on "Output directory" step?

What is the URL in your browser's address line when you getting 404 error?

A
andyjames author 6/11/2007

Hi Sergey
This is what I do on the output directory page:

Specify my output directory to: C:\wamp\www\aa2\

Specify my website url as: http://localhost/aa2/index.htm
I then build the files.

If I then click on "Open output folder" that works fine and opens the newly created files in C:\wamp\www\aa2\

If I click on "View in Browser", my browser is directed to http://localhost/aa2/index.htm but it returns a 404 error.
However (this is wierd), if you add a "1" after the directory and type in http://localhost/aa21/index.htm, it works !!!
What? There is no C:\wamp\www\aa21\ directory!!
I can get round it but it's kind of wierd.

samsp 6/13/2007

hi,
same problem. i have 3 directories: company, realestate, probe. when i create the files in probe i could not open my company or realestate sites. get the same error. whats happend. did not have the problem with 3.1.
greetings
sam

samsp 6/13/2007

hi,
same problem. i have 3 directories: company, realestate, probe. when i create the files in probe i could not open my company or realestate sites. get the same error. whats happend. did not have the problem with 3.1.
greetings
sam

samsp 6/13/2007

hi,
i have figured out the problem. every time when klick on build button on the "output directory", phpr write in to the "httpd.conf" from apache a virtual directory. so if you try to get the old website on your localhost, you will get the error 404.
solution is: make backup from "httpd.conf" then go to the original and delete on the end all virtual directories.
greeting
sam

admin 6/13/2007

Sam and Andy,
let me explain how it works.
For each project PHPRunner creates a virtual directory in Apache that points to your projects output directory. The purpose is to help people who decided to use default output folder (C:\Program files\PHPRunner4.0\Projects\Project1\output). PHPRunner creates a copy of httpd.conf (httpd.bak) in this case.
When you choose an output directory under Apache root directory and name it after the project name (C:\wamp\www\aa2\) PHPRunner creates a virtual directory named aa2 which leads to 404 error. In other words PHPRunner is not smart enough to understand that no virtual directory is required in this case.
I hope this makes some sense and will help you to avoid this confusion in the future.

samsp 6/14/2007

hi Sergey,
i thing that it makes sence, but its good to know whats happend. thank you for responce.
greeting
sam

A
andyjames author 6/14/2007

Hi Sergey
Thanks for the explanation. I have upgraded my installation of WAMP Server and the problem has resolved itself but good to know if it happens again.

Thanks for your support.