|

»

»

»

Channel title used within uPortal 3 theme

View: New views

19 Messages — Rating Filter: Alert me

	Channel title used within uPortal 3 theme by Matthew Peterson-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Can anyone tell me why, within the theme, channel titles are produced using ‘UP:CHANNEL_TITLE-{<xsl:value-of select="@ID" />}’ syntax rather than just using ‘<xsl:value-of select="@name" />’ syntax? We have changed from the former to the latter as the former was producing inconsistence results for portlets. It was sometimes producing the name of the channel as defined in the channel set-up but was sometimes producing the name of the portlet as defined in portlet.xml. Where we need it to be consistently the name of the channel as defined in the channel set-up. Maybe a bug??? Cheers, Matt Peterson Web Developer University of New England Ph. (02) 6773 3550 -- You are currently subscribed to uportal-user@... as: lists@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user
	Re: Channel title used within uPortal 3 theme by Eric Dalquist :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Because channel titles can be dynamic. This was added somewhat for 2.6 and flushed out for 3.0. The actual driver for this functionality is portlets which include the ability in the API to set the title dynamically with each render call. The reason the string token is used and not a XSL parameter is that the channel title is not known until after the theme transform is complete. Also with the way uPortal caches the results of the theme transform the framework needs to be able to change the title text with each re-rendering on a tab. The behavior you're seeing is expected for the portlets most likely. Those portlets are using the name from portlet.xml and calling setTitle in during their render cycle. If no dynamic title is set the title from the channel definition is used. I hope that helps, -Eric Matt Peterson wrote: Can anyone tell me why, within the theme, channel titles are produced using ‘UP:CHANNEL_TITLE-{<xsl:value-of select="@ID" />}’ syntax rather than just using ‘<xsl:value-of select="@name" />’ syntax? We have changed from the former to the latter as the former was producing inconsistence results for portlets. It was sometimes producing the name of the channel as defined in the channel set-up but was sometimes producing the name of the portlet as defined in portlet.xml. Where we need it to be consistently the name of the channel as defined in the channel set-up. Maybe a bug??? Cheers, Matt Peterson Web Developer University of New England Ph. (02) 6773 3550 -- You are currently subscribed to uportal-user@... as: eric.dalquist@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user smime.p7s (4K) Download Attachment
	Re: Channel title used within uPortal 3 theme by Cris J Holdorph :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Perhaps there is room for a 'feature improvement' jira, where a system admin can override the functionality to not allow the portlet to change it's title, and instead 'fix' the title to a certain value. shrug ---- Cris J H Eric Dalquist wrote: > Because channel titles can be dynamic. This was added somewhat for 2.6 > and flushed out for 3.0. The actual driver for this functionality is > portlets which include the ability in the API to set the title > dynamically with each render call. > > The reason the string token is used and not a XSL parameter is that the > channel title is not known until after the theme transform is complete. > Also with the way uPortal caches the results of the theme transform the > framework needs to be able to change the title text with each > re-rendering on a tab. > > The behavior you're seeing is expected for the portlets most likely. > Those portlets are using the name from portlet.xml and calling setTitle > in during their render cycle. If no dynamic title is set the title from > the channel definition is used. > > I hope that helps, > -Eric > > Matt Peterson wrote: >> >> Can anyone tell me why, within the theme, channel titles are produced >> using ‘UP:CHANNEL_TITLE-{<xsl:value-of select="@ID" />}’ syntax rather >> than just using ‘<xsl:value-of select="@name" />’ syntax? >> >> >> >> We have changed from the former to the latter as the former was >> producing inconsistence results for portlets. It was sometimes >> producing the name of the channel as defined in the channel set-up but >> was sometimes producing the name of the portlet as defined in >> portlet.xml. Where we need it to be consistently the name of the >> channel as defined in the channel set-up. Maybe a bug??? >> >> >> >> Cheers, >> >> >> >> Matt Peterson >> >> Web Developer >> >> University of New England >> >> Ph. (02) 6773 3550 >> >> >> >> >> -- >> >> You are currently subscribed to uportal-user@... as: eric.dalquist@... >> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user --- You are currently subscribed to uportal-user@... as: lists@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user
	Re: Channel title used within uPortal 3 theme by Eric Dalquist :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message If the behavior isn't desired you can simply remove the use of the UP:CHANNEL_TITLE token and go back to just using the @name attribute in the theme XSL. -Eric Cris J Holdorph wrote: > Perhaps there is room for a 'feature improvement' jira, where a system > admin can override the functionality to not allow the portlet to > change it's title, and instead 'fix' the title to a certain value. > shrug > > ---- Cris J H > > Eric Dalquist wrote: >> Because channel titles can be dynamic. This was added somewhat for >> 2.6 and flushed out for 3.0. The actual driver for this functionality >> is portlets which include the ability in the API to set the title >> dynamically with each render call. >> >> The reason the string token is used and not a XSL parameter is that >> the channel title is not known until after the theme transform is >> complete. Also with the way uPortal caches the results of the theme >> transform the framework needs to be able to change the title text >> with each re-rendering on a tab. >> >> The behavior you're seeing is expected for the portlets most likely. >> Those portlets are using the name from portlet.xml and calling >> setTitle in during their render cycle. If no dynamic title is set the >> title from the channel definition is used. >> >> I hope that helps, >> -Eric >> >> Matt Peterson wrote: >>> >>> Can anyone tell me why, within the theme, channel titles are >>> produced using ‘UP:CHANNEL_TITLE-{<xsl:value-of select="@ID" />}’ >>> syntax rather than just using ‘<xsl:value-of select="@name" />’ syntax? >>> >>> >>> >>> We have changed from the former to the latter as the former was >>> producing inconsistence results for portlets. It was sometimes >>> producing the name of the channel as defined in the channel set-up >>> but was sometimes producing the name of the portlet as defined in >>> portlet.xml. Where we need it to be consistently the name of the >>> channel as defined in the channel set-up. Maybe a bug??? >>> >>> >>> >>> Cheers, >>> >>> >>> >>> Matt Peterson >>> >>> Web Developer >>> >>> University of New England >>> >>> Ph. (02) 6773 3550 >>> >>> >>> >>> >>> -- >>> >>> You are currently subscribed to uportal-user@... as: >>> eric.dalquist@... >>> To unsubscribe, change settings or access archives, see >>> http://www.ja-sig.org/wiki/display/JSG/uportal-user > > --- You are currently subscribed to uportal-user@... as: > eric.dalquist@... > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/uportal-user smime.p7s (4K) Download Attachment
	Re: Channel title used within uPortal 3 theme by Cris J Holdorph :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message In Matt's case, where he's already shown the initiative to edit .xsl, sure. I was thinking of something more 'out of the box' administrative GUI for places that might not have .xsl skillsets on staff. ---- Cris J H Eric Dalquist wrote: > If the behavior isn't desired you can simply remove the use of the > UP:CHANNEL_TITLE token and go back to just using the @name attribute in > the theme XSL. > > -Eric > > Cris J Holdorph wrote: >> Perhaps there is room for a 'feature improvement' jira, where a system >> admin can override the functionality to not allow the portlet to >> change it's title, and instead 'fix' the title to a certain value. >> shrug >> >> ---- Cris J H >> >> Eric Dalquist wrote: >>> Because channel titles can be dynamic. This was added somewhat for >>> 2.6 and flushed out for 3.0. The actual driver for this functionality >>> is portlets which include the ability in the API to set the title >>> dynamically with each render call. >>> >>> The reason the string token is used and not a XSL parameter is that >>> the channel title is not known until after the theme transform is >>> complete. Also with the way uPortal caches the results of the theme >>> transform the framework needs to be able to change the title text >>> with each re-rendering on a tab. >>> >>> The behavior you're seeing is expected for the portlets most likely. >>> Those portlets are using the name from portlet.xml and calling >>> setTitle in during their render cycle. If no dynamic title is set the >>> title from the channel definition is used. >>> >>> I hope that helps, >>> -Eric >>> >>> Matt Peterson wrote: >>>> >>>> Can anyone tell me why, within the theme, channel titles are >>>> produced using ‘UP:CHANNEL_TITLE-{<xsl:value-of select="@ID" />}’ >>>> syntax rather than just using ‘<xsl:value-of select="@name" />’ syntax? >>>> >>>> >>>> >>>> We have changed from the former to the latter as the former was >>>> producing inconsistence results for portlets. It was sometimes >>>> producing the name of the channel as defined in the channel set-up >>>> but was sometimes producing the name of the portlet as defined in >>>> portlet.xml. Where we need it to be consistently the name of the >>>> channel as defined in the channel set-up. Maybe a bug??? >>>> >>>> >>>> >>>> Cheers, >>>> >>>> >>>> >>>> Matt Peterson >>>> >>>> Web Developer >>>> >>>> University of New England >>>> >>>> Ph. (02) 6773 3550 >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> You are currently subscribed to uportal-user@... as: >>>> eric.dalquist@... >>>> To unsubscribe, change settings or access archives, see >>>> http://www.ja-sig.org/wiki/display/JSG/uportal-user >> >> --- You are currently subscribed to uportal-user@... as: >> eric.dalquist@... >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/uportal-user > --- You are currently subscribed to uportal-user@... as: lists@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user
	RE: Channel title used within uPortal 3 theme by Matthew Peterson-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Cool. I didn’t realise that was the reason for the syntax. It still doesn’t explain the behaviour we are experiencing, however. The homegrown portlet being used as the test subject for this is not using dynamic titles but it is using a <portlet-info><title /></portlet-info> element within portlet.xml. The strange behaviour is that this channel will, on some renders, have the title as set in the channel set-up while on other renders will have the title as the portlet info title as given in portlet.xml. In my mind one or the other should consistently be rendered when the portlet is not using dynamic titles. From: bounce-5907449-5729388@... [mailto:bounce-5907449-5729388@...] On Behalf Of Eric Dalquist Sent: Wednesday, 28 May 2008 10:05 AM To: uportal-user@... Subject: Re: [uportal-user] Channel title used within uPortal 3 theme Because channel titles can be dynamic. This was added somewhat for 2.6 and flushed out for 3.0. The actual driver for this functionality is portlets which include the ability in the API to set the title dynamically with each render call. The reason the string token is used and not a XSL parameter is that the channel title is not known until after the theme transform is complete. Also with the way uPortal caches the results of the theme transform the framework needs to be able to change the title text with each re-rendering on a tab. The behavior you're seeing is expected for the portlets most likely. Those portlets are using the name from portlet.xml and calling setTitle in during their render cycle. If no dynamic title is set the title from the channel definition is used. I hope that helps, -Eric Matt Peterson wrote: Can anyone tell me why, within the theme, channel titles are produced using ‘UP:CHANNEL_TITLE-{<xsl:value-of select="@ID" />}’ syntax rather than just using ‘<xsl:value-of select="@name" />’ syntax? We have changed from the former to the latter as the former was producing inconsistence results for portlets. It was sometimes producing the name of the channel as defined in the channel set-up but was sometimes producing the name of the portlet as defined in portlet.xml. Where we need it to be consistently the name of the channel as defined in the channel set-up. Maybe a bug??? Cheers, Matt Peterson Web Developer University of New England Ph. (02) 6773 3550 -- You are currently subscribed to uportal-user@... as: eric.dalquist@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user -- You are currently subscribed to uportal-user@... as: lists@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user
	Re: Channel title used within uPortal 3 theme by Eric Dalquist :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Is your home-grown portlet using the Spring portlet MVC? If so I believe the either the dispatcher port or the base Controller calls setTitle for you using the localized title from the portlet.xml There may be a way to disable this behavior but I haven't looked at the docs in a while. -Eric Matt Peterson wrote: Cool. I didn’t realise that was the reason for the syntax. It still doesn’t explain the behaviour we are experiencing, however. The homegrown portlet being used as the test subject for this is not using dynamic titles but it is using a <portlet-info><title /></portlet-info> element within portlet.xml. The strange behaviour is that this channel will, on some renders, have the title as set in the channel set-up while on other renders will have the title as the portlet info title as given in portlet.xml. In my mind one or the other should consistently be rendered when the portlet is not using dynamic titles. From: bounce-5907449-5729388@... [bounce-5907449-5729388@...] On Behalf Of Eric Dalquist Sent: Wednesday, 28 May 2008 10:05 AM To: uportal-user@... Subject: Re: [uportal-user] Channel title used within uPortal 3 theme Because channel titles can be dynamic. This was added somewhat for 2.6 and flushed out for 3.0. The actual driver for this functionality is portlets which include the ability in the API to set the title dynamically with each render call. The reason the string token is used and not a XSL parameter is that the channel title is not known until after the theme transform is complete. Also with the way uPortal caches the results of the theme transform the framework needs to be able to change the title text with each re-rendering on a tab. The behavior you're seeing is expected for the portlets most likely. Those portlets are using the name from portlet.xml and calling setTitle in during their render cycle. If no dynamic title is set the title from the channel definition is used. I hope that helps, -Eric Matt Peterson wrote: Can anyone tell me why, within the theme, channel titles are produced using ‘UP:CHANNEL_TITLE-{<xsl:value-of select="@ID" />}’ syntax rather than just using ‘<xsl:value-of select="@name" />’ syntax? We have changed from the former to the latter as the former was producing inconsistence results for portlets. It was sometimes producing the name of the channel as defined in the channel set-up but was sometimes producing the name of the portlet as defined in portlet.xml. Where we need it to be consistently the name of the channel as defined in the channel set-up. Maybe a bug??? Cheers, Matt Peterson Web Developer University of New England Ph. (02) 6773 3550 -- You are currently subscribed to uportal-user@... as: eric.dalquist@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user -- You are currently subscribed to uportal-user@... as: eric.dalquist@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user smime.p7s (4K) Download Attachment
	Re: Channel title used within uPortal 3 theme by Eric Dalquist :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Yes, that is a good idea. It could probably be accomplished via a structure attribute that the theme XSL checks to determine if just to use the @name or the replacement token. -Eric Cris J Holdorph wrote: > In Matt's case, where he's already shown the initiative to edit .xsl, > sure. I was thinking of something more 'out of the box' > administrative GUI for places that might not have .xsl skillsets on > staff. > > ---- Cris J H > > Eric Dalquist wrote: >> If the behavior isn't desired you can simply remove the use of the >> UP:CHANNEL_TITLE token and go back to just using the @name attribute >> in the theme XSL. >> >> -Eric >> >> Cris J Holdorph wrote: >>> Perhaps there is room for a 'feature improvement' jira, where a >>> system admin can override the functionality to not allow the portlet >>> to change it's title, and instead 'fix' the title to a certain >>> value. shrug >>> >>> ---- Cris J H >>> >>> Eric Dalquist wrote: >>>> Because channel titles can be dynamic. This was added somewhat for >>>> 2.6 and flushed out for 3.0. The actual driver for this >>>> functionality is portlets which include the ability in the API to >>>> set the title dynamically with each render call. >>>> >>>> The reason the string token is used and not a XSL parameter is that >>>> the channel title is not known until after the theme transform is >>>> complete. Also with the way uPortal caches the results of the theme >>>> transform the framework needs to be able to change the title text >>>> with each re-rendering on a tab. >>>> >>>> The behavior you're seeing is expected for the portlets most >>>> likely. Those portlets are using the name from portlet.xml and >>>> calling setTitle in during their render cycle. If no dynamic title >>>> is set the title from the channel definition is used. >>>> >>>> I hope that helps, >>>> -Eric >>>> >>>> Matt Peterson wrote: >>>>> >>>>> Can anyone tell me why, within the theme, channel titles are >>>>> produced using ‘UP:CHANNEL_TITLE-{<xsl:value-of select="@ID" />}’ >>>>> syntax rather than just using ‘<xsl:value-of select="@name" />’ >>>>> syntax? >>>>> >>>>> >>>>> >>>>> We have changed from the former to the latter as the former was >>>>> producing inconsistence results for portlets. It was sometimes >>>>> producing the name of the channel as defined in the channel set-up >>>>> but was sometimes producing the name of the portlet as defined in >>>>> portlet.xml. Where we need it to be consistently the name of the >>>>> channel as defined in the channel set-up. Maybe a bug??? >>>>> >>>>> >>>>> >>>>> Cheers, >>>>> >>>>> >>>>> >>>>> Matt Peterson >>>>> >>>>> Web Developer >>>>> >>>>> University of New England >>>>> >>>>> Ph. (02) 6773 3550 >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> You are currently subscribed to uportal-user@... as: >>>>> eric.dalquist@... >>>>> To unsubscribe, change settings or access archives, see >>>>> http://www.ja-sig.org/wiki/display/JSG/uportal-user >>> >>> --- You are currently subscribed to uportal-user@... >>> as: eric.dalquist@... >>> To unsubscribe, change settings or access archives, see >>> http://www.ja-sig.org/wiki/display/JSG/uportal-user >> > > --- You are currently subscribed to uportal-user@... as: > eric.dalquist@... > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/uportal-user smime.p7s (4K) Download Attachment
	RE: Channel title used within uPortal 3 theme by Matthew Peterson-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. No, it’s a very simple portlet which has been written by extending GenericPortlet. It just forwards on to a JSP to generate the view, edit and help content. From: bounce-5907476-5729388@... [mailto:bounce-5907476-5729388@...] On Behalf Of Eric Dalquist Sent: Wednesday, 28 May 2008 10:30 AM To: uportal-user@... Subject: Re: [uportal-user] Channel title used within uPortal 3 theme Is your home-grown portlet using the Spring portlet MVC? If so I believe the either the dispatcher port or the base Controller calls setTitle for you using the localized title from the portlet.xml There may be a way to disable this behavior but I haven't looked at the docs in a while. -Eric Matt Peterson wrote: Cool. I didn’t realise that was the reason for the syntax. It still doesn’t explain the behaviour we are experiencing, however. The homegrown portlet being used as the test subject for this is not using dynamic titles but it is using a <portlet-info><title /></portlet-info> element within portlet.xml. The strange behaviour is that this channel will, on some renders, have the title as set in the channel set-up while on other renders will have the title as the portlet info title as given in portlet.xml. In my mind one or the other should consistently be rendered when the portlet is not using dynamic titles. From: bounce-5907449-5729388@... [bounce-5907449-5729388@...] On Behalf Of Eric Dalquist Sent: Wednesday, 28 May 2008 10:05 AM To: uportal-user@... Subject: Re: [uportal-user] Channel title used within uPortal 3 theme Because channel titles can be dynamic. This was added somewhat for 2.6 and flushed out for 3.0. The actual driver for this functionality is portlets which include the ability in the API to set the title dynamically with each render call. The reason the string token is used and not a XSL parameter is that the channel title is not known until after the theme transform is complete. Also with the way uPortal caches the results of the theme transform the framework needs to be able to change the title text with each re-rendering on a tab. The behavior you're seeing is expected for the portlets most likely. Those portlets are using the name from portlet.xml and calling setTitle in during their render cycle. If no dynamic title is set the title from the channel definition is used. I hope that helps, -Eric Matt Peterson wrote: Can anyone tell me why, within the theme, channel titles are produced using ‘UP:CHANNEL_TITLE-{<xsl:value-of select="@ID" />}’ syntax rather than just using ‘<xsl:value-of select="@name" />’ syntax? We have changed from the former to the latter as the former was producing inconsistence results for portlets. It was sometimes producing the name of the channel as defined in the channel set-up but was sometimes producing the name of the portlet as defined in portlet.xml. Where we need it to be consistently the name of the channel as defined in the channel set-up. Maybe a bug??? Cheers, Matt Peterson Web Developer University of New England Ph. (02) 6773 3550 -- You are currently subscribed to uportal-user@... as: eric.dalquist@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user -- You are currently subscribed to uportal-user@... as: eric.dalquist@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user -- You are currently subscribed to uportal-user@... as: lists@... To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-user
	Re: Channel title used within uPortal 3 theme by Eric Dalquist :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. So now that I'm at work and can look at code I realize it is actually GenericPortlet that does this. This is the render method from GenericPortlet: `public void render (RenderRequest request, RenderResponse response) throws PortletException, java.io.IOException { response.setTitle(getTitle(request)); doDispatch(request, response); }` And this is getTitle from GenericPortlet: `protected java.lang.String getTitle(RenderRequest request) { return config.getResourceBundle(request.getLocale()).getString("javax.portlet.title"); }` So if you don't want a portlet to do this you'll need to either override getTitle to return what you want (you can try returning null though I can't find good documentation on the expected behavior in that case) or you can override render and just call doDispatch. -Eric Matt Peterson wrote: No, it’s a very simple portlet which has been written by extending GenericPortlet. It just forwards on to a JSP to generate the view, edit and help content. From: bounce-5907476-5729388@... [bounce-5907476-5729388@...] On Behalf Of Eric Dalquist Sent: Wednesday, 28 May 2008 10:30 AM To: uportal-user@... Subject: Re: [uportal-user] Channel title used within uPortal 3 theme Is your home-grown portlet using the Spring portlet MVC? If so I believe the either the dispatcher port or the base Controller calls setTitle for you using the localized title from the portlet.xml There may be a way to disable this behavior but I haven't looked at the docs in a while. -Eric Matt Peterson wrote: Cool. I didn’t realise that was the reason for the syntax. It still doesn’t explain the behaviour we are experiencing, however. The homegrown portlet being used as the test subject for this is not using dynamic titles but it is using a <portlet-info><title /></portlet-info> element within portlet.xml. The strange behaviour is that this channel will, on some renders, have the title as set in the channel set-up while on other renders will have the title as the portlet info title as given in portlet.xml. In my mind one or the other should consistently be rendered when the portlet is not using dynamic titles. From: bounce-5907449-5729388@... [bounce-5907449-5729388@...] <