Null User SiteAccess makes it unavailable from "Design"

Null User SiteAccess makes it unavailable from "Design"

Wednesday 01 February 2006 12:03:52 pm - 4 replies

Author Message

Thomas Nunninger

Wednesday 01 February 2006 1:40:37 pm

In which siteaccess do you log in? Did you install another siteaccess earlier? Where did your settings like database, ... go? What is inserted as AvailableSiteAccesList in /settings/override/site.ini.append.php?

Thomas

C C

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

Thomas Nunninger

Wednesday 01 February 2006 10:30:00 pm

Hi,

that's what I expected :-) There is only one listed siteaccess "XYZ". How should the system recognize, which siteaccess you are using? (If you have URI matching, your urls will look like index.php/<siteaccess>/<module>/<function>/<parameters...> or with nice urls index.php/<siteaccess>/<descriptive_path>/<to>/<object>.) Where should the settings (database, ...) of the "null" siteaccess go when your OS won't create a directory /settings/siteaccess/<null>. http://ez.no/doc/ez_publish/technical_manual/3_6/concepts_and_basics will help understanding the system if you haven't read yet.

If you haven't done much till now, I propose to install new. In other cases try to create a new siteaccess manual (if you are familiar with the settings) or save the database and, reinstall and restore the backuped database.

With the bugs: feel free to report them in the bug tracker.

Have a nice day

Thomas

C C

Thursday 02 February 2006 6:34:08 am

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

You must be logged in to post messages in this topic!

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.