Multiple CMSPortlet instances - how to extend /content...

[jboss.biancashouse.com]

This relates to the problem whereby you can only use CMS links in the default instance of CMSPortlet. If you try to use more instances of CMSPortlet (i.e. on new pages) then CMS links always fetch the page that has the default instance. This is a severe limitation of CMS.

Could anyone shed some light on how portal processes URLs with /content... ?

I have spent hours pouring over RenderPageCommand etc., but I can't figure out the lifecycle of a CMS link request.

I have this idea that if I could work out how CMS links (/content/...) are handled, I could then hack a way to allow additional TargetWindowRef values.

I imagine that someone at JBoss is workig hard to fix this shortcoming, but I'd like to help if I can. Hope someone can shed some light to get me started...

Thanks

Ian
Sydney

[theute]

This issue has already been fixed, in the 2.4 Branch and 2.6:

Affects Version/s: 2.2 Final , 2.4 Final , 2.6.Alpha1
Fix Version/s: 2.6.Beta1 , 2.4.2 Final
http://jira.jboss.com/jira/browse/JBPORTAL-538?page=all

[jboss.biancashouse.com]

Thanks for the quick response Tom.

I'm actually using 2.6 Alpha 2.

Anyway, there is only one place for setting TargetWindowRef (in the xml), so this is an o/s issue (design issue) ?

or did I miss something ?

[jboss.biancashouse.com]

Thomas, do you advise that I checkout the 2.6 Beta1 version from SVN ?

Or should I just wait for you guys to announce when it becomes ready for download ?

Thanks,

Ian

[theute]

It will be in Beta1, (or you can get it in the actual SVN)

Now when you click on a realtive link you should stay on the same page. (not redirected to TargetWindowRef).

TargetWindowRef is just used for content you access through /content/

[jboss.biancashouse.com]

Excellent.

2 questions:

- What's the SVN address ? - I only saw 2.6-SNAPSHOT

- When you say "relative link", are you now saying we don't use /content/... - what would a link to another content item look like now ?

Many thanks for you help.
Much appreciated. Thanks

Ian