Not speaking from a data.xml point of view here. Just from an 'up and
running' point of view....
I'd logon with 'guest' and delete all tabs I had permission to delete.
So that the ONLY things left on my layout (while I was "logged on" as
guest) were fragments.
---- Cris J H
Timothy Carroll wrote:
i was able to resolve this issue. i made a rookie mistake!
i was using the group evaluator against a user attribute, so i was able
to get this scenario to work.
now, i am curious about some things that chris and drew mentioned about
creating a blank guest user template, then merging in fragments as
appropriate.
i have not been able to get a guest user fragment to show up. are there
any known gotchas here? when you guys talk about an empty guest user,
how "empty" is it actually... does it just have a root layout node, or
does it need more? less?
thanks, tim
Timothy Carroll wrote:
the override is not working as i had expected. currently...
1. i have the portal.properties template user set to 'guest'
2. i have a 'guest' user and associated layout that simply shows the
login screen
3. i defined a few fragments in the dlm.xml file that resolve when
username is not 'guest'
4. i created user ids for each of the fragment owners
5. i created layouts for each of the fragment owners
6. i created a 'tcarroll' user
7. i start the portal, and the 'guest' user template shows up with the
login screen prompting for credentials
8. i login with the 'tcarroll' user id
9. i'm expecting to see the fragments that i created, but i see the
'guest' layout with login screen with welcome tcarroll message
any suggestions?
thanks again, tim
Drew Wills wrote:
Tim,
Typically, the 'guest' user is the account that all unauthenticated
users get.
The 'guest-lo' user is a DLM fragment owner: the 'guest' user will
see the content of the 'guest-lo' user's layout.
You can actually log in as 'guest-lo'; once you do, you can edit the
content of the Guests fragment.
I should think you probably *do* need a 'guest' user account, though
you can name it something else (if you really want to) in
portal.properties.
You can remove the 'guest-lo' user if you want to. If you do, be
sure to remove the corresponding fragment from dlm.xml.
drew wills
Timothy Carroll wrote:
hi all. we are currently cleaning up our data.xml file, and i'm am
curious about removing the guest user and layout.
we are developing under up26 and using dlm.
there is a dlm guest fragment owner (guest-lo), so i suppose my real
question is...
how are the "guest" user template and "guest-lo" fragment owners
used? are they both necessary? if not, how are each used?
i can't seem to find any real clear references to the difference.
thank so much, tim
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
