|
Author
|
Message
|
|
Peter Putzer
|
Sunday 25 February 2007 3:15:37 am
I'm trying to upgrade our site http://pluspunkt.at/ to eZ publish 3.9.1rc1 (I wanted to wait for 3.9.1, but since it will take more time, apparently, I'm content with 3.9.1rc1). Unfortunately, the IndexPage directive in site.ini seems to be ignored. Everything else (taking into account some template bugs triggered by the upgrade, but that was to be expected) works fine, except for the IndexPage. I have checked to bug tracking system and this forum, to no avail. I am <i>not</i> using PathPrefix or anything of the sort. Has anyone else experienced this problem? Any workarounds (besides moving from a separate index page to a modified root folder, which would be my last ressort)?
Accessible website starting from eZ publish 3.0 (currently: 4.1.0): http://pluspunkt.at
|
|
André R.
|
Sunday 25 February 2007 9:19:16 am
Are you using the website interface ?
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|
|
Peter Putzer
|
Sunday 25 February 2007 9:55:45 am
Not unless its somehow hardcoded. I just unpacked the tgz and copied over my templates and settings (so the same extensions as in 3.8 should be enabled, nothing extra).
Accessible website starting from eZ publish 3.0 (currently: 4.1.0): http://pluspunkt.at
|
|
christian bencivenni
|
Sunday 25 February 2007 1:14:22 pm
I don't know if the problem is the same but I have the same problem.
I installed xampp 1.6 (last release) and when I try to start the instllation setup of 3.9.1rc1 it doesn't work. Explorer and Firefox reply a "page not found".
Other php scripts and html pages works good.
Some ideas?
|
|
André R.
|
Monday 26 February 2007 12:23:06 am
Peter: Is the data correct if you got to the ini editor and take a look at SiteSettings in site.ini of your frontpage SiteAccess ? christian: You are not trying to run eZ Publish on php 5 are you ?
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|
|
Peter Putzer
|
Saturday 03 March 2007 3:20:43 am
Strangely enough, the siteaccess selection box in the admin interface INI editor is disabled. But yeah, I even put things in the override settings (manually of course, I am a command line junkie), so the settings were definitely applied. I "solved" the problem by reworking my templates to work with the root folder, which is semantically cleaner anyway, but still, a strange bug.
Accessible website starting from eZ publish 3.0 (currently: 4.1.0): http://pluspunkt.at
|
|
Guillaume Kempfer
|
Wednesday 07 March 2007 3:37:16 am
I've got the same problem, IndexPage doesn't work with pathprefix.
My site.ini.append :
[SiteSettings]
SiteUrl=bacon-immobilier.com
IndexPage=/content/view/full/141
DefaultPage=/content/view/full/141
LoginPage=embedded When i load the index, i get the pathprefix node but i want pathprefix/accueil node
|
|
Heath
|
Thursday 08 March 2007 9:48:41 am
There is a related issue on file, <i>http://issues.ez.no/IssueView.php?Id=10408&activeItem=1</i>
Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org
|
|
meinhard benn
|
Monday 12 March 2007 7:52:28 am
I am having the same issue with 3.8.8. I set IndexPage to a different node than the standard node 2, which worked fine until we upgraded from 3.8.7 to 3.8.8 recently. Now {$module_result|attribute(show,1)} in pagelayout.tpl shows me node_id '2' on the start page despite my ini setting. I worked around it with a system URL forward from / to /content/view/full/xx (via URL translator in the admin). Update: I just added a bug report: http://issues.ez.no/IssueView.php?Id=10436
http://goozee.benn.org/ - Google Co-op for eZ sites
|
|
Heath
|
Friday 16 March 2007 7:49:56 am
I looks like this bug has been fixed in svn and the issues updated! Fixed in
trunk rev. 18356
release/3.9.1 rev. 18357
release/3.8.7 rev. 18358
release/3.7.10 rev. 18359
release/3.6.12 rev. 18360
I tested the updated sources from svn which fixed the problem for me.
Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org
|