Liferay Search Migration from 6.2 to 7.1

In Liferay 6.2, search scope used to be specified by groupId (site) , whereas 7.1 defines the scope either only as Everything or This-site by enum value.

The way to specify search scope itself has been simplified (minimized?), but still search result can be filtered by Search facets which accepting groupId, assetEntryId, etc as search criteria.

No need for modification in API yo

Done!



https://github.com/liferay/liferay-portal/tree/7.1.x/modules/apps/portal-search/portal-search-web


https://github.com/liferay/liferay-portal/tree/6.2.x/portal-web/docroot/html/portlet/search

Comments

Post a Comment

Popular posts from this blog

Portlet Edit Mode (Portlet preference) to replace Portlet configuration

Within the  EDIT  portlet mode, a portlet should provide content and logic that lets a user customize the behavior of the portlet Typically, portlets in  EDIT  portlet mode will set or update portlet preferences. Add the following properties to the MVCPortlet component annotation. "javax.portlet.portlet-mode=text/html;edit" "javax.portlet.init-param.edit-template=/edit.jsp" And then If you go into the grid button on the portlet, 'Preference' option will appear which redirects you to edit.jsp
Read more

GoGo Shell & What can be deleted in Liferay Instance

In Liferay Instance, remove 'state' in osgi & 'work' in tomcat to remove all histories. GoGoShell is for checking the current state of each jar files in modules. pen cmd as admin and type 'telnet localhost 11311' lb : list all the jar files with state stop 70 (jar file numner) / start 70 (uninstall 70 but for deletion, it would be better to delete jar file from module folder physically) )
Read more