URL problems after installing on a hosted server

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
Mikko Mustakallio	Wednesday 19 May 2004 2:04:34 am Hi, I've read tens of threads related to this topic and I know that a lot of people have been struggling with the same issue, especially in hosted environments: installation goes well, but after entering the front-end only the index.php page on the site works and none of the links. The back-end's admin login page cannot be found either. Based on what I've read here, the problem seems to lie in the fact that the hosted server might be <b> running PHP as suexec in CGI mode and that's why no PATH_INFO can be found</b>. However, according to EZP's error page, AcceptPathInfo can be turned off, but then the links won't work. My question is, if there is no other chance than to run PHP as suexec in CGI mode, do I have to forget using EZP? I haven't asked my hosting provider yet, but I strongly doubt they would change their PHP settings... Thanks for any input! Regs. Mikko
Björn Dieding@xrow.de	Wednesday 19 May 2004 2:14:23 am There are also hostproviders out there that are specialized in eZ hosting. Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Mikko Mustakallio	Friday 21 May 2004 12:35:18 am Okay, installing 3.4 beta 1 fixed the problem (which was actually said somewhere in this forum ;). I should have done that in the first place instead of wasting my time trying to patch 3.3-5... Thanks & keep up the good work!
Peter Quennell	Sunday 23 May 2004 8:23:15 am Hi Mikko Still around? I hope so. I put posts in the Install and Bugfix forums on 20 May on the bug causing the problem you describe. We now have experience of THREE installations where the bugfix got beyong the problem. Please let us know of your own experiences. I am sure "out" problem is spooking possible adopers way from EZ Publish. It very very nearly had us gone - even though this great prog is 1000% right for our needs. Peter Quennell New York
Peter Quennell	Sunday 23 May 2004 8:25:38 am Re the above "out" should read "our" of course... Is there a known reason why the text entry box has to be at 2-3 pixels? Such a wacky setting is hardly a good advertisement for the quality of support here!

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 31 2025 00:39:23
Script start
Timing:	Jan 31 2025 00:39:23
Module start 'layout'
Timing:	Jan 31 2025 00:39:23
Module start 'content'
Timing:	Jan 31 2025 00:39:23
Module end 'content'
Timing:	Jan 31 2025 00:39:23
Script end

Main resources:

Total runtime	0.0221 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	588.3828	151.2422
Module start 'layout'	0.0048	0.0033	739.6250	220.7500
Module start 'content'	0.0082	0.0126	960.3750	1,001.9922
Module end 'content'	0.0208	0.0013	1,962.3672	33.9922
Script end	0.0221		1,996.3594

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	10.5621	14	0.0002
Check MTime	0.0010	4.5317	14	0.0001
Mysql Total
Database connection	0.0008	3.4550	1	0.0008
Mysqli_queries	0.0020	9.1915	3	0.0007
Looping result	0.0000	0.0452	1	0.0000
Template Total	0.0009	4.1	1	0.0009
Template load	0.0007	3.2838	1	0.0007
Template processing	0.0002	0.7946	1	0.0002
Override
Cache load	0.0005	2.1899	1	0.0005
General
dbfile	0.0014	6.3943	8	0.0002
String conversion	0.0000	0.0269	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs