Changed URL parameters are messing up rendering of a page

Eric Borisow

Hi,

We recently upgraded from Portal 7.3 to Portal 8.1.  However, I've run into a problem with our custom federated search.  We had customized our search page to use Get instead of Post previously and are hoping to do that again.  Here's the problem:

In 7.3, the one parameter was rendered like this:

javax.portlet.prp_b2240e5152bc310244170b9de418c22a_viewID=merged_results

Now, in 8, it's getting rendered like this:

javax.portlet.prp_b2240e5152bc310244170b9de418c22a=prv%253D%2526viewID%253Dmerged_results

 

So, the incorrect page is rendered as a result.  If I manually go in and change the URL to how it previously rendered, then it displays our custom search results with no problem.  Even if I try to cheat and put in some code and do a replace just prior to the submit, it still fails.  Can someone tell me how this extra data gets into the parameter?  Even better, how can I disable it?

 

Thanks,

Eric

 

Al_Daniel

Hello Eric,

The change in behavior is documented in OpenText KB Article 17552965, including instructions for restoring the origional behavior using the following property.

    portal.encode_parameters.enabled=false

Regards

Alex

 

 

Quoted eborisow@us.imshealth.com on 2011-12-07 07:44:

Hi,

We recently upgraded from Portal 7.3 to Portal 8.1.  However, I've run into a problem with our custom federated search.  We had customized our search page to use Get instead of Post previously and are hoping to do that again.  Here's the problem:

In 7.3, the one parameter was rendered like this:

javax.portlet.prp_b2240e5152bc310244170b9de418c22a_viewID=merged_results

Now, in 8, it's getting rendered like this:

javax.portlet.prp_b2240e5152bc310244170b9de418c22a=prv%253D%2526viewID%253Dmerged_results

 

So, the incorrect page is rendered as a result.  If I manually go in and change the URL to how it previously rendered, then it displays our custom search results with no problem.  Even if I try to cheat and put in some code and do a replace just prior to the submit, it still fails.  Can someone tell me how this extra data gets into the parameter?  Even better, how can I disable it?

 

Thanks,

Eric