|
Author
|
Message
|
|
Francis Nart
|
Thursday 29 January 2004 1:26:03 am
Hi,
we are brand new to ez publish and we have juste finished a website locally on a windows system.
We now want to upload it to our dedicated server on a lamp installation.
We dowloaded the tar.gz ez publish version, we uploaded it to our server and then...problem.
We get an access to the home page, the index page of the plain site (we did not upload our templatesand database at this time !) and it does work fine. The problem is that no link work ! every link on the index page (the basic one) does link to an internal error page.
Then, we did upload our templates and our database.
Once agian, the index page works fine (images and so on)and the content extracted from the database. The problem is that, once again the links just don't work (internal error 500).
We are really stuck here for we don't get any error message during the install ! (the wizard). Our server is running apache / mysql on a linux redhat system. There is an appliance interface called ensim but it doesn't seem to be the problem ! even when we activate the debug we don't get any error but apparently the system does not parse the url correctly ! Please help for we are really lost here ! Best regards.
Francis.
|
|
Joakim Stai
|
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.
|
|
Ted Striker
|
Friday 30 January 2004 10:59:31 am
Have the same problem too. After installing and following the tutorial... no http://localhost/expublish/iondex.php/plain works neither .../index.php/plain_admin. Hope someone knows whats wrong :)
Can you feel it Mr. Anderson? Closing in on you? Oh I can, I really should thank you after all. It was, after all, it was your life that taught me the purpose of all life. Purpose of life is to end.
|
|
Marco Zinn
|
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
|
|
STan Hoffman
|
Sunday 01 February 2004 4:15:21 am
'AcceptPathInfo on' in the htaccess fixed it for me.
|
|
Joakim Stai
|
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.
|
|
Marco Zinn
|
Wednesday 04 February 2004 11:15:14 am
Hi Stan,
hi Joakim thanks for sharing your hints & Links here. This question is the topic of 50% of threads in the "installation" forum. I'm sure, that this will help a lot of people... if they read this ;)
Marco
http://www.hyperroad-design.com
|
|
Francis Nart
|
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.
|
|
mihnea stoian
|
Monday 09 February 2004 7:40:13 am
I got this response from my x-webhost: Since the server runs php as an suexec CGI the PATH_INFO and LOCAL_* variables are not set. This was why the index.php/my/content links didn't work. This was on a server running Apache 1.3.27, so no php.ini fixes for that unless they/you reconfigure the apache server.
|
|
Eric Weik
|
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>
|
|
Francis Nart
|
Tuesday 17 February 2004 2:17:01 am
too bad there is no possibility to get in touch with the developer of the patch ! to be clear : is there anybody who found a way to run ez publish with CGI ? Francis.
|
