Hi David, in my original thought all the portalPages would have been rendered by a single "system" screen that would have offered to the logged in user all the portlaPages he has access to.
This is what happens now accessing to the common/control/portalPage url. The portalPages available to the user to choose from should be the ones that belongs to the actual user plus all the portalPages defined as "public" (with a not yet present flag). I did not think to the portalPage overriding but only to the possibility for the user to create new pages. What you propose is a great solution to both have the portalPage overriding feature (even in the "system" portalPage rendering screen) and to have the include-portal-page screen widget element. Thank you! I will try to implement this. 2008/10/19 David E. Jones (JIRA) <[EMAIL PROTECTED]> > > [ > https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640827#action_12640827] > > David E. Jones commented on OFBIZ-1999: > --------------------------------------- > > I was thinking about the include-portal-page screen widget element and the > primary key of the PortalPage entity. Right now there is just a portalPageId > in the pk, so when a default page is overridden by a user a new portalPageId > would have to be created, which would break the include-portal-page element > that points to the original portalPageId. > > There is a "owner" field in the entity (might be more clear if it was > called "ownerUserLoginId" instead) and we could add that to the pk (ie make > it a pk field). When rendering a page with just a portalPageId we'd look for > a record with the userLoginId of the current user and if that isn't found > we'd use the "system" userLoginId or something. > > Does that make sense? > > > A portal/portlet implementation > > ------------------------------- > > > > Key: OFBIZ-1999 > > URL: https://issues.apache.org/jira/browse/OFBIZ-1999 > > Project: OFBiz > > Issue Type: New Feature > > Components: ALL COMPONENTS > > Reporter: Bruno Busco > > Priority: Minor > > Attachments: portalPage-configure-off.jpg, > portalPage-configure-on.jpg, portalPages.patch, portalPages.patch, > portalPages.patch, portalPages.patch > > > > > > Hi devs, > > I am trying to set up a portal/portlet model similar to what is > implemented into JIRA user interface. > > The Idea is that every component can "register" its selected screens as > system portlets using something like: > > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" > screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > > In this case the portal component has registered a welcome screen as > "WELCOME" portlet. > > The portlets can later be "mounted" into portals with the entity: > > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" > columnNum="1" sequenceNum="1" /> > > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" > columnNum="2" sequenceNum="2" /> > > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" > columnNum="1" sequenceNum="2" /> > > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" > columnNum="3" sequenceNum="2" /> > > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" > columnNum="1" sequenceNum="2" /> > > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and > PORTLET003 are mounted into the DEFAULT portal into the indicated solumns > and with the indicated order. > > Every portal is defined by the entity: > > <Portal portalId="DEFAULT" name="Default home portal" description="The > default OFBiz portal" owner="admin" /> > > And is related to a specific user. So every user can have as many portals > he needs and a DEFAULT portal can be defined by the admin. > > In the attached zip file there is a very draft implementation of this > that I would like so submit to your attention to share ideas about it and > eventually develop together. > > Many thanks for your feedbacks, > > Bruno > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
