Bug 809545 - EPP-SP migration: Overriding search form template location not working after migration
Summary: EPP-SP migration: Overriding search form template location not working after ...
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Site Publisher
Version: 5.2.0.GA,5.2.0.SP.GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 5.2.1.GA
Assignee: Martin Weiler
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-03 15:42 UTC by Martin Weiler
Modified: 2018-11-30 22:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If the EPP-SP instance was migrated from EPP 5.2.x to EPP 5.2.1, the built-in templates and views were not automatically updated to the new version. This resulted in some functions not working correctly in some use-cases, such as using the advanced search. This behavior has been corrected in the current version by upgrading the built-in templates and views automatically during a migration from a previous EPP-SP version.
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
EXO WCM JIRA ECMS-3358 0 None None None Never
EXO WCM JIRA SPREDHAT-119 0 None None None Never

Description Martin Weiler 2012-04-03 15:42:33 UTC
Description of problem:
We have a problem with the search form groovy template, when using the default instance of the WCMAdvanceSearchPortlet portlet. We have created our own portal extension and search form and result groovy templates to override the default search form and result templates.


Steps to Reproduce:
1. Migrate from EPP-SP-5.1.1 to EPP-SP-5.2.0
2. Add a new page
3. Add Advanced Search portlet to the page
4. Advanced Search portlet doesn't display well
5. We have exceptions in server console

Comment 2 Martin Weiler 2012-04-11 11:44:54 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The built-in templates and views were not automatically updated to the new version, if the EPP-SP instance was migrated from EPP 5.2.x to EPP 5.2.0. This resulted in some functionality, such as using the advanced search, to not work properly in certain use cases. This has been corrected in the current version, where the built-in templates and views are automatically upgraded during a migration from a previous EPP-SP version.

Comment 3 Jared MORGAN 2012-04-11 23:43:32 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-The built-in templates and views were not automatically updated to the new version, if the EPP-SP instance was migrated from EPP 5.2.x to EPP 5.2.0. This resulted in some functionality, such as using the advanced search, to not work properly in certain use cases. This has been corrected in the current version, where the built-in templates and views are automatically upgraded during a migration from a previous EPP-SP version.+If the EPP-SP instance was migrated from EPP 5.2.x to EPP 5.2.1, the built-in templates and views were not automatically updated to the new version. This resulted in some functions not working correctly in some use-cases, such as using the advanced search. This behavior has been corrected in the current version by upgrading the built-in templates and views automatically during a migration from a previous EPP-SP version.

Comment 4 prabhat jha 2012-04-12 15:56:06 UTC
Need some info from Martin W.


Note You need to log in before you can comment on or make changes to this bug.