'No input file specified.' error when accessing pages

Next topic

Author	Message
mihnea stoian	Monday 26 January 2004 9:22:44 am If I try accessing the site through http://www.domain.com/site/index.php it displays fine, but http://www.domain.com/site/index.php/site and http://www.domain.com/site/index.php/site_admin both give the 'No input file specified.' error. The same error appears when I click on any of the links on the plain page I see at http://www.domain.com/site/index.php. Any help would be HUGELY appreciated, as I've finally managed to get this far after a week of frustrations and do not want to give up now! (setup went flawless, btw). Thank you, Mihnea
Kåre Køhler Høvik	Monday 26 January 2004 10:04:35 am Hi Please make sure you have enabled AcceptPathInfo. http://ez.no/ez_publish/documentation/configuration/troubleshooting/ez_publish_3_and_apache_2 -- Kåre Høvik Kåre Høvik
mihnea stoian	Monday 26 January 2004 11:48:43 am It's not the AcceptPathInfo On directive, as I hoped it to be. If it were that, I would've gotten a 404 instead of the 'No input file specified.' I get. The netnation.com account is running Apache 1.3.*, so the AcceptPathInfo On fix won't work anyway, and it seems that it's running fine, since it doesn't give me a 404 and the url in the address bar gets correctly updated. What else could it be? The support person mentioned that PHP is being run as a module... could that be it? Thanks, Mihnea
mihnea stoian	Tuesday 27 January 2004 7:45:46 am I tried to install the system again with as little customization as possible, and it still gives me the same error when I try to access anything else but the index.php file. It's really frustrating, as I don't know why it's doing this and I can feel that once I get this working it should all be going smoothly. To recap, the system that it's running on is Linux 2.4.24 with PHP 4.3.2 and the latest Apache 1.3.27. any help would be HUGELY appreciated! mihnea
Angered User	Wednesday 28 January 2004 11:48:00 am Also having this problem, running in on the same settings as above i believe. Its quite a dumb idea too, its too... unusual for people to see anything after the extension. My suggestion, drop that method and stick to using separate files for each for the next version