|
Sunday 23 February 2003 3:10:46 am
Thanks for this Michael,
> Yes, you are right I was just checking to see if the
> defaults where there. They are you can change them once you
> get logged in. Sorry to ask all of the stupid questions
> just trying to talk you though my check list.
>
> Hmmm I just though of something, you have setup one DNS.
> How are you loggin in to the admin part of the site. Well I hoped that the default was what they appear to call 'URI' resolution. And it certainly appears that way in my sinte.ini immediately after install. So that I would be doing http://ez3.jcsolutions.co.uk/ to get to the default, which would be the user site, and something like http://ez3.jcsolutions.co.uk/admin/ to get to the admin site. But of course it does look as if the http://ez3.jcsolutions.co.uk/ is trying the admin site, or that the user site is demanding a login. The top left corner of that screen does say >User/Login.
>The
> site that I setup the user side I made open and the admin
> site was passworded. Are you accessing the admin part of
> the site by port or DNS. If you are using DNS remember to
> change the sitesettings. Here are what mine look like:
> [SiteAccessSettings]
> CheckValidity=false
> RequireUserLogin=true
> MatchOrder=host;port;uri From what I mentioned above, I thought I would have 'uri' first in this statement and sure enough by default it is.
> URIMatchType=element
> URIMatchElement=1
> URIMatchRegexp=^/([^/]+)/
> URIMatchRegexpItem=1
> HostMatchType=regexp
> HostMatchElement=0
> HostMatchRegexp=^mtest(.+)\.bf-internal\.com$
> HostMatchRegexpItem=1
> HostMatchSubtextPre=
> HostMatchSubtextPost=mtest.bf-internal.com
> IndexMatchType=regexp
> IndexMatchElement=1
> IndexMatchRegexp=^/index_(.+)\.php$
> IndexMatchRegexpItem=1
> IndexMatchSubtextPre=index_
> IndexMatchSubtextPost=.php
>
> These two are very key:
> HostMatchRegexp=^mtest(.+)\.bf-internal\.com$
> HostMatchSubtextPost=mtest.bf-internal.com
> This sets up the DNS to be like the following:
> mtestadmin.bf-internal.com
> mtestuser.bf-internal.com I thought these looked important, but then because I was using URI, the SiteAccess instruction document seems to imply that it is not needed. Just out of interest, I presume that as a 'co.uk' domain I would use something like HostMatchRegexp=^mtest(.+)\.bf-internal\.co.uk$ if I were doing that?
>
> If you are using the port, make sure that port is visible to
> the HTTPD. For example for apache I had to add the line:
> Listen 1338
>
> Then you might setup your site as:
> HostMatchRegexp=^(.+)\.bf-internal\.com$
> HostMatchSubtextPost=.bf-internal.com
>
> This setup the site like the following:
> user.bf-internal.com
> user.bf-interanl.com:1338 I will have a look at these settings, but it seems to me, reading between the lines, that by default the system uses uri resolution, and that in my site.ini it is set up that way. There is a setting in SiteSettings called 'AdminSiteURL' or something and I don't know what to put in there if I am using URI resolution. I may have to go and try to use Host based resolution - which would be a great shame as I have a name service providor who limits the number of host names I can have per domain, so it looks great to me to be able to access version three with only one. If you use host based resolution by the way, do you just copy the info from the doc/install file again into the settings for the admin hst in the httpd.conf?
> I hope this help,
> Michael Thanks for trying. I'd really like to get there sometime soon! Jock
|
