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
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.
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.
Need some info from Martin W.