Enrique,

Thanks for the link you've pointed out. I have taken a look at the doc and
it was quite helpful. Nonetheless there are still some misty points to me,
like :

1) how come "role:user:group:user:group:admin" doesn't look first for
/pages/_role/user/_group/user/_group/admin ? (similarly to J1 example
supplied)

2) it looks like user-role-fallback is the best pick for me (first look
inside _user, then _role's user). How can I set it to default profile ?

3) my previous question 3) : when does J2 decide to copy _user/template to
_user/myUser ?

Ludovic

> Hi, Ludovic
>
> As far as I know, every time a new user is registered (succesfully) in
> the system (through the "User Registration" portlet), a new folder is
> created under "jetspeed/WEB-INF/pages/_user/" and named as the username
> (specified by the user).
>
> Then, there is a profiling rule for searching pages in the portal that
> works like this:
>
>     - Supposed we want to look for the page "tab1.psml"
>     - The searching engine starts from the deepest folder and comes back
>     to root (I think this is called "fall-back", but I'm not sure):
>     
> WEB-INF/pages/_user/[username]/_mediatype/[media]/_language/[lang]/_country/[country]/tab1.psml
>
>     - If there is a tab1.psml in that path, J2 shows that page, but if
>     there is no match found in that path (because there is no
>     "tab1.psml" in it, or simply "/_country/[country]" does not exists),
>     J2 tries to look for "tab1.psml" in the next directory:
>     
> WEB-INF/pages/_user/[username]/_mediatype/[media]/_language/[lang]/tab1.psml
>     NOTE that we skip the directory "/_country/". This is a rule for the
>     profiler: it will skip all folders that start with character "_".
>
>     -And so on, if exists, J2 shows that page; if not, tries for the
>     next path. Suppossing there is no "tab1.psml" in any directory, I
>     think the searching paths would be:
>     WEB-INF/pages/_user/[username]/_mediatype/[media]/tab1.psml
>     WEB-INF/pages/_user/[username]/tab1.psml
>     WEB-INF/pages/tab1.psml
>     WEB-INF/pages/default-page.psml
>
>
> If I didn't make it clear enough (or I'm wrong), you can find more info
> about profinling rules in this docs:
> https://svn.apache.org/repos/asf/portals/jetspeed-2/branches/JETSPEED-BRANCH-2.0.1/design-docs/src/profiler/
>
> and then look for a file called: J2-page-manager-profiling
>
> Regards,
> Enrique
>
> [EMAIL PROTECTED] escribió:
>> Hi again,
>>
>> 1) I've recently noticed that ALL my pages which have VelocityTwoColumns
>> actually display 1 column (1 portlet per row). I haven't touched
>> anything
>> to my PSMLs as far as I know. I even tried to pull out an older version
>> which I remember displayed OK, and now it's screwed as well.
>> Therefore my guesses tend to be around the Database, problem is I don't
>> have a single idea on which table to search...
>>
>> 2) Is there a guide on how to use profiles that I'm missing ?
>> I've been playing around with those profiles lately in order to display
>> the same pages for all "manager" (role) and let all simple user with
>> default ones. It looks like J1 and J2 don't do the job, unlike
>> role-fallback (and maybe the others "fallback" too). So what are J1 and
>> J2's specialities ? Why are they the default profiles ?
>> I have taken a look at the Administrative->Profile Manager but it's
>> quite
>> confusing...
>>
>> 3) Why sometimes (depending on the profile maybe ?) a default-page.psml
>> is
>> generated in _user/aNewUser/ ? How to prevent this from happening ?
>>
>> For information, I have upgraded from J2.0 to J2.0.1 yesterday.
>>
>> Thanks,
>> Ludovic
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to