|
Author
|
Message
|
|
Alex Jones
|
Thursday 04 September 2003 3:32:23 pm
I am using a design other than the 'user' or 'standard' ones for a site I am working on; it is called 'agr'. I have enabled Nice URLs and set up the virtual hosts, but for some reason when I view the site with the nice URLs they return a module not found. An example URL generated by the system is: example.com/products/by_maker/a_through_d
I discovered that if I add the name of my design it'll work:
example.com/agr/products/by_maker/a_through_d How can I set up the system to work without using the 'agr/'? I'm sure there is a simple setting somewhere that I've missed... Thanks! Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
<i>When in doubt, clear the cache.</i>
|
|
Paul Forsyth
|
Friday 05 September 2003 6:03:15 am
I assume you have made a seperate siteaccess for your new design? Also, the site.ini files contain info about which siteaccess files are active and can be used. Maybe you need to enable yours. Do a 'grep' to find 'user' to spot where you need to add yours. Paul
|
|
Alex Jones
|
Friday 05 September 2003 6:11:50 am
Yes, I had created a site.ini.append for 'agr' here is the code for [SiteAccessSettings] with 'example.com' substituting for the domain:
[SiteAccessSettings]
RequireUserLogin=false
MatchOrder=uri;host
HostMatchType=map
HostMatchMapItems[]=www.example.com;agr
HostMatchMapItems[]=admin.example.com;admin
You mention to search for 'user' in the SiteAccessSettings... What exactly am I looking for? I am going add the lines:
AvailableSiteAccessList[]=agr
and
SiteAccessList[]=agr Is there anything else to add? Thanks! Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
<i>When in doubt, clear the cache.</i>
|
|
Paul Forsyth
|
Friday 05 September 2003 6:20:49 am
Sorry, do the search within your settings directory. Usually the extra additions are in your site.ini, but depending on how you do your overrides it may be one of a few files... Paul
|
|
Paul Forsyth
|
Friday 05 September 2003 6:23:29 am
I realised now that isn't the best of help... Your available site accesses should do the trick. You may need to change the default site access 'DefaultAccess' I think... Basically play with the settings ;) I haven't got much experience doing this as i stick to 'user'. Paul
|
|
Alex Jones
|
Friday 05 September 2003 7:10:10 am
Hrrrm, actually you helped get me on track. :) Apparently I needed to have it in the actual site.ini. For some reason having it in site.ini.append was not enough. I'm going to experiment a bit more though... Thanks! Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
<i>When in doubt, clear the cache.</i>
|
|
Paul Forsyth
|
Friday 05 September 2003 7:30:11 am
It all depends on placement. site.ini is overriden by your siteacces site.ini, which is overriden by site.ini.append in the override directory.... confusing. Would be nice to have the ez sys info page report on what options are available, and from what file ;) paul
|
|
Alex Jones
|
Friday 05 September 2003 7:43:37 am
Ahhh, my understanding of the overrides was a bitt off. I assumed that the override/site.ini.append trumped all aothers. I agree it would be nice to see what settings are used in the admin section. Also, why are there three possible config files to change? Why not take it down to site.ini and the override/site.ini and drop the append file? If all of the functionality of the append file is added to the override files it would be a lot easier to ensure changes are made where they belong. Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
<i>When in doubt, clear the cache.</i>
|
|
Paul Forsyth
|
Friday 05 September 2003 9:26:36 am
Erm, i think i said that the site.ini.append in the override does trump all of the others? read again :) Although confusing you have a *lot* of flexibility depending exactly how you want to configure your site. The original site.ini is the default, you can then add a few things in each siteaccess to have your site do something for the correct design, then further global changes can be applied by the override directory to affect all siteaccess designs... powerful but easy to muck up! paul
|
|
Alex Jones
|
Friday 05 September 2003 9:44:16 am
Ooops, I mispoke (mistyped?), I had assumed that the siteaccess/user/override/site.ini.append would trump all others. I.e. the site-specific override would be the final word. :) I hope that makes sense. I agree it is powerful, and perhaps your earlier suggestion would ease much of the confusion that comes with three configuration files that essentialy control the exact same settings. Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
<i>When in doubt, clear the cache.</i>
|