IndexPage is ignored

Next topic

Author	Message
Ciprian Popovici	Friday 05 May 2006 4:54:21 am My IndexPage option has started being ignored rather suddenly. I have two siteaccess's set up on one eZ installation and both of them seem to pull the default page out of their hat. As it happens, one of them gets it right (it's the one I set up way back then), but the other doesn't (it picks a folder upper in the content tree). I've set up the 2 sites like this: Content root: -- site1 --\|-- node X -- site2 --\|-- node Y For each site I say IndexPage=/content/view/full/X (or Y). As of recent, they ignore this and I always get X for the first and the node id of the [site2] folder for the second. I've tried several things I could think of: cleared all cache, deleted everything manually from var/cache/, checked that I don't have IndexPage in the global override. Nothing.
Ciprian Popovici	Sunday 07 May 2006 11:37:51 pm I've "solved" it by going to Setup/URL Translator and setting up a system forwarding from "site2" (the folder that holds the objects for this site) to content/view/full/145 (the node that holds the homepage article). I repeat, the nodes are different, site2 being 141 and the homepage article being 145. IndexPage is set to 145, yet it keeps showing 141. I'm glad it worked out, but if anybody can give me an explanation I'd appreciate it. Besides, this workaround has the lovely effect of being active for the admin siteaccess too, and I can't go into the "site2" folder anymore, it redirects to the homepage article below. It makes adding new folders or articles rather tedious, having to move them around after creation.

Author

Message

Friday 05 May 2006 4:54:21 am

My IndexPage option has started being ignored rather suddenly. I have two siteaccess's set up on one eZ installation and both of them seem to pull the default page out of their hat. As it happens, one of them gets it right (it's the one I set up way back then), but the other doesn't (it picks a folder upper in the content tree).

I've set up the 2 sites like this:

Content root:
-- site1
--|-- node X
-- site2
--|-- node Y

For each site I say IndexPage=/content/view/full/X (or Y). As of recent, they ignore this and I always get X for the first and the node id of the [site2] folder for the second.

I've tried several things I could think of: cleared all cache, deleted everything manually from var/cache/, checked that I don't have IndexPage in the global override. Nothing.

Ciprian Popovici

Sunday 07 May 2006 11:37:51 pm

I've "solved" it by going to Setup/URL Translator and setting up a system forwarding from "site2" (the folder that holds the objects for this site) to content/view/full/145 (the node that holds the homepage article). I repeat, the nodes are different, site2 being 141 and the homepage article being 145. IndexPage is set to 145, yet it keeps showing 141.

I'm glad it worked out, but if anybody can give me an explanation I'd appreciate it.

Besides, this workaround has the lovely effect of being active for the admin siteaccess too, and I can't go into the "site2" folder anymore, it redirects to the homepage article below. It makes adding new folders or articles rather tedious, having to move them around after creation.