Ticket #821 (closed defect: fixed)

Opened 14 years ago

Last modified 14 years ago

Advanced Search form link may be wrong

Reported by: bdelbosc Owned by: jmorliaguet
Priority: P2 Milestone: CPS 3.4.0
Component: CPSPortlets Version: TRUNK
Severity: normal Keywords: advanced search form link cache


Advanced Search form link may be wrong

Advanced search form link is cached for 1h, after a startup if you access your site with a different location than normal users (localhost, https ...) then the advanced link is wrong for one hour.

This link should not be cached and set here/advanced_search_form instead of /advanced_search_form to have the 'search here: ....' enable.

Change History

comment:1 Changed 14 years ago by jmorliaguet

  • Status changed from new to assigned


The current cache parameter is:

   'Search Portlet': ['no-cache'],

which means that the portlet is never cached.

With the new options available in the cache parameters it is however possible to cache the portlet if the advanced options are not set:


But maybe you are talking about the Templet? In that case it is better to go to the cache management screen in CPSSkins and change the caching option to "do not cache"

And generally speaking it is better to use portlets rather than templets.

comment:2 Changed 14 years ago by fguillaume

  • Milestone changed from unspecified to CPS 3.4.0

comment:3 Changed 14 years ago by jmorliaguet

  • Status changed from assigned to closed
  • Resolution set to fixed

fixed in [30614]

Templets do not support other caching schemes than timeout. So the search portlet which has the same functionality should be used instead if caching is important.

The default theme has been updated to not cache the search box templet by default. Another solution is to replace the search templet with a portlet. Reopen the bug if the second solution is better.

comment:4 Changed 14 years ago by madarche

It would be easier for new comers to CPS if the search box was a portlet. But how hard would it be to do it? Could you please describe the needed steps?

comment:5 Changed 14 years ago by jmorliaguet

the portlet would be rendered in a templet (a sort of proxy). The only problem right now is that it would require going through CPSIO during the installation phase.

this is not a problem for custom products, but I wouln't want to introduce a dependency on CPSIO in the "stock CPSSkins" at this stage.

comment:6 Changed 14 years ago by madarche

Thanks for the explanation.

Agreed, let's keep this bug closed at least for now.

Note: See TracTickets for help on using tickets.