|
Author
|
Message
|
|
Mike Cohen
|
Wednesday 26 February 2003 1:54:52 pm
Prior to upgrading to RC 2 I had no problems with logins being required to access the general site. Now no matter what I do I am requested for a login when I try to access the home page or any sub page of the site. I have:
[SiteAccessSettings]
RequireUserLogin=false
in both site.ini and in the site.ini.append file in the:
'settings/siteaccess/mysite' directory. I have also verified that my anonymous user has read permissions on the content module with no limitations. Any ideas as to why a login is requested? Thanks, Mike Cohen
|
|
Volker Lenz
|
Thursday 27 February 2003 1:57:53 am
> Prior to upgrading to RC 2 I had no problems with logins
> being required to access the general site. Now no matter
> what I do I am requested for a login when I try to access
> the home page or any sub page of the site.
>
> I have:
>
> [SiteAccessSettings]
> RequireUserLogin=false
>
> in both site.ini and in the site.ini.append file in the:
> 'settings/siteaccess/mysite' directory.
>
> I have also verified that my anonymous user has read
> permissions on the content module with no limitations.
>
> Any ideas as to why a login is requested?
>
> Thanks,
>
> Mike Cohen Read this: http://developer.ez.no/forum/message/14361/ You have to define some kind of user login permission for the default user account (anonymous). I recommend that you restrict this default user login permission to your public site access ( user site ) unless you like to have public visitors on your admin console. Edit your role for anonymous and apply the following policy:
module: user
function: login
limitation: site access( user ) ezp-rc2 requires such a policy, since the site access checker currently evaluates a users right to login to the given site before it checks other permissions. The login policy does not mean that ezp actually "logs in" anonymous users in the background. ezp just checks whether a user could log in ( as a somewhat weird prerequisite to let even unlogged users access content.)
|
|
Claus Jensen
|
Thursday 27 February 2003 2:23:07 am
> You have to define some kind of user login permission for
> the default user account (anonymous).
>
> I recommend that you restrict this default user login
> permission to your public site access ( user site ) unless
> you like to have public visitors on your admin console. Edit
> your role for anonymous and apply the following policy:
>
> module: user
> function: login
> limitation: site access( user ) I have a similar problem, but I wonder... where do I edit these permissions? In some files, from a webapp or directly in a db?? Kind of new to ezpublish, and isn't to impressed with the user-friendlyness of the system yet...
regards,
claÜs
|
|
Volker Lenz
|
Thursday 27 February 2003 2:35:25 am
> > You have to define some kind of user login permission
> for
> > the default user account (anonymous).
> >
> > I recommend that you restrict this default user login
> > permission to your public site access ( user site )
> unless
> > you like to have public visitors on your admin console.
> Edit
> > your role for anonymous and apply the following policy:
> >
> > module: user
> > function: login
> > limitation: site access( user )
>
> I have a similar problem, but I wonder... where do I edit
> these permissions? In some files, from a webapp or directly
> in a db?? Kind of new to ezpublish, and isn't to impressed
> with the user-friendlyness of the system yet...
>
> regards,
> claÜs No, you have to enter your ADMIN-SITE and go to the ROLES-View (left menu bar). Then you enter the role for ANONYMOUS and apply the policy I described above. It's all GUI-based, no ini-files involved, no db-hacks required ;-) Rergards Volker
|
|
Claus Jensen
|
Thursday 27 February 2003 3:51:17 am
> It's all GUI-based, no ini-files involved, no db-hacks
> required ;-) I see, got there but still no luck. I now wonder if I have messed up my config files, since I have been editing them directly (site.ini, site.append.ini and such).
Here's what I have done. Installed the ez3 RC2 with mysql and apache bundled in. The demo-site then worked. I wanted to create a new site, but didnt find info on how to do it, so i started with making a copy of siteaccess/user and called it test. I did the same in the design/user and called it test. Then changed following in site.ini
...
Matchorder = port
...
SiteAccessList[] = user
SiteAccessList[] = demo
SiteAccessList[] = admin
SiteAccessList[] = test
...
[PortAccessSettings]
1337 = demo
1338 = admin
1340 = test
... When using the same database it worked, I then in the siteaccess/test/site.ini.append, override the database settings, trying to use a postgresql database, and it dont work. Also now the demo site (port 1337) just gives a message: "Unavailable - the object is not avaiable", and stops. I dont have a clue... Also there have been some problems with some files having changed permissions to root and my own user when editing them. With these I have changed them to the ez user account. Is this the wrong way to setup a new site, should everything be done from the admin site? I am beginning to feel that its not the right way... Any help is appreciated.
regards,
claÜs
|
|
Claus Jensen
|
Thursday 27 February 2003 3:54:42 am
> It's all GUI-based, no ini-files involved, no db-hacks
> required ;-) I see, got there but still no luck. I now wonder if I have messed up my config files, since I have been editing them directly (site.ini, site.append.ini and such).
Here's what I have done. Installed the ez3 RC2 with mysql and apache bundled in. The demo-site then worked. I wanted to create a new site, but didnt find info on how to do it, so i started with making a copy of siteaccess/user and called it test. I did the same in the design/user and called it test. Then changed following in site.ini
...
Matchorder = port
...
SiteAccessList[] = user
SiteAccessList[] = demo
SiteAccessList[] = admin
SiteAccessList[] = test
...
[PortAccessSettings]
1337 = demo
1338 = admin
1340 = test
... When using the same database it worked, I then in the siteaccess/test/site.ini.append, override the database settings, trying to use a postgresql database, and it dont work. Also now the demo site (port 1337) just gives a message: "Unavailable - the object is not avaiable", and stops. I dont have a clue... Also there have been some problems with some files having changed permissions to root and my own user when editing them. With these I have changed them to the ez user account. Is this the wrong way to setup a new site, should everything be done from the admin site? I am beginning to feel that its not the right way... Any help is appreciated.
regards,
claÜs
|
|
Mike Cohen
|
Thursday 27 February 2003 8:51:14 am
> > Prior to upgrading to RC 2 I had no problems with logins
> > being required to access the general site. Now no matter
> > what I do I am requested for a login when I try to
> access
> > the home page or any sub page of the site.
> >
> > I have:
> >
> > [SiteAccessSettings]
> > RequireUserLogin=false
> >
> > in both site.ini and in the site.ini.append file in the:
> > 'settings/siteaccess/mysite' directory.
> >
> > I have also verified that my anonymous user has read
> > permissions on the content module with no limitations.
> >
> > Any ideas as to why a login is requested?
> >
> > Thanks,
> >
> > Mike Cohen
>
> Read this: http://developer.ez.no/forum/message/14361/
>
> You have to define some kind of user login permission for
> the default user account (anonymous).
>
> I recommend that you restrict this default user login
> permission to your public site access ( user site ) unless
> you like to have public visitors on your admin console. Edit
> your role for anonymous and apply the following policy:
>
> module: user
> function: login
> limitation: site access( user )
>
> ezp-rc2 requires such a policy, since the site access
> checker currently evaluates a users right to login to the
> given site before it checks other permissions.
>
> The login policy does not mean that ezp actually "logs in"
> anonymous users in the background. ezp just checks whether a
> user could log in ( as a somewhat weird prerequisite to let
> even unlogged users access content.) Volker,
I read the forum post you suggested and added the:
user login *
role to my anonymous user and it worked. I don't know how you guys figure some of this stuff out. Many Thanks, Mike
|
|
James Robertson
|
Tuesday 09 August 2005 2:28:08 pm
I just spent ages struggling with this very problem for v3.6.1 installation. Unfortunately only found this forum message after I had solved it myself (hence knew the right terms to search on). My thanks to Volker for the explanation. Where is this stuff documented? Seems pretty fundamental to getting a site to actually work! I follow the tutorial ( http://ez.no/products/ez_publish_cms/documentation/building_an_ez_publish_site ) - with many corrections to make it actually work. Why doesn't the 'Plain' site have the correct permissions set-up for the Anonymous role?
Cheers
JamesR
|
|
James Ashley
|
Tuesday 16 August 2005 3:00:48 pm
In 3.7.0.rc1, it looks like this is a default setting. So maybe enough people have complained about it to make a difference <G>.
|
|
James Ashley
|
Tuesday 16 August 2005 4:03:43 pm
Oops, I take that back. The first site I created gave Anonymous visiting permissions. The second site didn't. Or maybe I gave Anonymous rights without realizing. It does kind of make sense, I guess. It probably would be far too difficult to set up a basic flag to attach to various sites that says "This one is admin. Anonymous & Guest Users keep out." <shrug>.
|