Null User SiteAccess makes it unavailable from "Design"

Wednesday 01 February 2006 12:03:52 pm

Hello,
During installation, I intentionally left blank the "User access" directory, to avoid creating an extra directory in the structure.

The installation proceeded without problems. Now, when I login as an administrator, and I try to "Design" the user access, I cannot. The User access is not available in the drop-down box that says "SiteAccess" - Only the admin SiteAccess is listed.

This seems to be an obvious bug (The fact that I used a blank directory for the user SiteAccess gives a clue).

QUESTION:
Do I have any way of recovering the install by easily changing the SiteAccess to some directory, or am I better off deleting the whole thing and starting again?

COMMENT:
- The installation script should be modified so that it does not accept null entries for a SiteAccess, or even better
- Let the user use null entries, and catch the problem in other parts of the Admin interface.

Any help will be appreciated

ChC

Wednesday 01 February 2006 8:38:21 pm

Answers inline:

> In which siteaccess do you log in?
The user SiteAccess is null. The Admin SiteAccess is XYZ
- I login to domain/index.php/XYZ
- Everything is working fine, EXCEPT that the drop-down box for SiteAccess only showsx XYZ (of course, it doesn't know how to show me a "null" option in the list

> Did you install another siteaccess earlier?
No

> Where did your settings like database, ... go?
I don't understand your question

> What is inserted as AvailableSiteAccesList in /settings/override/site.ini.append.php?
It says:
AvailableSiteAccessList[]
AvailableSiteAccessList[]=XYZ

See? It doesn't know what to do with the "null" directory. The drop-down box, instead of letting me chose between a blank line, for example, and XYZ, only shows my XYZ

So, my question still stands: Do I have any way of recovering the install by easily changing the SiteAccess to some directory, or am I better off deleting the whole thing and starting again?

And of course, my comments about bugs, documenting them, and if possible fixing them :) also stand

Cheers!

ChC

Thursday 02 February 2006 6:34:08 am

Thanks, Thomas, for your time and attention.
Cheers
CC