portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Baranovsky (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-786) Tool for conversion preferences from database no-principal preferences to defaults preferences in psml pages
Date Mon, 15 Oct 2007 22:42:50 GMT

    [ https://issues.apache.org/jira/browse/JS2-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534996
] 

Vitaly Baranovsky commented on JS2-786:
---------------------------------------

Thanks!

It is only the way to move portal to 2.1.3 version from portals with Jetspeed 2.0 if admin
configures public pages for users.

> Tool for conversion preferences from database no-principal preferences to defaults preferences
in psml pages
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JS2-786
>                 URL: https://issues.apache.org/jira/browse/JS2-786
>             Project: Jetspeed 2
>          Issue Type: Wish
>          Components: Portlet Entities and Preferences
>    Affects Versions: 2.1.3
>            Reporter: Vitaly Baranovsky
>            Assignee: David Sean Taylor
>             Fix For: 2.1.3
>
>
> With jetspeed 2.0 version all preferences was per entity. But all preferences become
per user with release of jetspeed 2.1.
> But people with Jetspeed 2.0 have important use case: admin configures portlets on public
portal pages for all users (include guests).
> So, people with Jetspeed 2.0 can't migrate to 2.1 version (and later versions).
> edit-defaults custom portlet mode (https://issues.apache.org/jira/browse/JS2-634) can
solve this problem. But people with Jetspeed 2.0 can't use edit-defaults portlet mode, because
edit-defaults custom portlet mode stores preferences directly in psml pages, and there is
no conversion tool to convert no-principal preferences from database to psml pages.
> So, there is need for conversion tool that moves no-principal preferences from db directly
to psml pages. 
> This is the only way to migrate to Jetspeed 2.1.3 for company that uses important use
case described above.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message