User login
Recent jobs
Active forum topics
- Vignette Portal Documentation
- VAP certification
- Users unable to login to CMA
- menu bar disappeared
- How to insert Content Instance into Relator?
- custom content input form
- Content Integration with VCM and VAP
- content input form
- VAP Aplication is not running in Tomcat
- Exceptional opportunity with one of the Top Leading MNC for Project Managers in Portal Content Management.
What happens with the content publisher portlet when the vgnextoid parameter doesn't exists?
Thu, 01/10/2008 - 18:20 — vgnadmin
The problem is that I have a page with a mix of a jsr-168 portlet and four content publisher portlets. The first time I enter in the page all works fine, but when I navigate throug the jsr-168 portlet I miss the vgnextoid parameter and the content publisher portlet shows the contents of other channel, not the contents of the channel I suppose I am.
If I add manually the parameter vgnextoid to the url, the content publisher portlets shows the expected contents.
I thought that the html result of these content publisher portlets must not change when the current request is for other portlet, not for them.
How could I do to make the html result of these portlets doesn't change?
Thanks in advance!
Re: What happens with the content publisher portlet when the vgn
I think these content publisher portlets need a valid vgnextoid param
There is nothing wrong to
There is nothing wrong to add vgnextid to the url, which I was doing after confirming from our Vignette Architect. Its a limitation, but appending vgnextid to the url is a workaround.
Ganesh.
Re: What happens with the content publisher portlet when..
Thanks Ganesh, now I am doing it this way. But I think this is another Vignette Portal bug. The tag <portlet:renderUrl/> and <portlet:actionURL/> must mantain the parameters that are not pretended for the portlet.
For instance, If I try to deploy a standard JSR-168 portlet I have to change all the url's generated by this portlet to append the vgnextoid parameter.