Thursday 29 January 2004 3:16:22 pm

I have the same problem with my 3.3 install (on Windows XP). The thing is that /index.php works fine, but /index.php/somepage doesn't work! I'm not sure whether this has something to do with eZp's kernel or Apache's setup.

Could somebody from the ez crew please answer this?
I really need to get my client's website to work.

Saturday 31 January 2004 2:52:30 am

There is some known problem with the configuration, if you use Apache 2. But i don't find the solution in here right now. But it is a one-line in the Apache config.
If you are using Apache 1.3, i don't know the solution, but i really think, that it must be an apache config problem.
Lots of people (including myself) were able to install and run the installation perfectly.

The problem seems to be, that Apache does not "recognise" the "index.php" part of the URL to be the file to run.

Marco
http://www.hyperroad-design.com

Sunday 01 February 2004 6:24:26 am

A search on this forum for '404' came up with this post:
http://www.ez.no/community/forum/install_configuration/404_no_input_file_specified/re_404_no_input_file_specified__1

We all obviously should have searched some more before asking for answers. If you use Apache 1.3 and have this problem, you've probably set PHP to run as CGI in your httpd.conf file. eZp needs PHP to be run as a SAPI module.

To do this (in Apache 1.3), I followed the instructions for installing PHP as a module (NOT as CGI, which causes the problem), found in the PHP manual http://no.php.net/manual/en/install.apache.php. Of course if you've configured PHP as CGI before, you have to remove these configuration lines from the httpd.conf file as well. This worked like a charm for me! eZp is back and running on my local testing server :)

If you use Apache 2, try adding 'AcceptPathInfo on' to your .htaccess file, as STan found out.

Wednesday 04 February 2004 1:28:14 pm

ok now it is a CGI pb.
somebody wrote a patch
see : http://ez.no/community/forum/install_configuration/my_final_patch_for_phpcgi for answers.
The pb is that when using that patch we have same same pb as Antonio (in the last reply before ours) : We need to add an "?" after the index.php for the website to run which is quite strange to us. Did anybody used it ? had the same pb ? any help would be most appreciated !

Francis.

Friday 13 February 2004 7:40:49 pm

I got the same warning when running the setup on Apache 1.3.29 with PHP installed as a module (on FreeBSD 4.9, built from the ports collection). However, after going back over httpd.conf and my virtualhost settings multiple times, I decided to try ignoring the warning. The system set up just fine, with all sample sites (using URL access).

I'm assuming the problem is due to a setting in our virtualhost. Below is a copy of mine for reference.

<VirtualHost *>
# Domain config
ServerName publish.mydomainname.com
ErrorLog /path/to/sites/publish.mydomainname.com/logs/error_log
CustomLog /path/to/sites/publish.mydomainname.com/logs/access_log combined
# eZpublish config
DocumentRoot /path/to/ezpublish
RewriteEngine On
RewriteRule !(^/design|^/var/.*/storage|^/var/storage|^/extension/.*/design|^/kernel/setup/packages).*\.(gif|css|jpg|png|jar|js|ico|pdf)$ /path/to/ezpublish/index.php
</Virtualhost>