This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project.

Wiki

Theme Id or Portlet Id references in portal-ext.properties

Details Print
Tags: portal.properties installation deployment setup portlet id theme id

Table of Contents [-]

  1. FQPI (Fully Qualified Portlet Id)
    1. FQTI (Fully Qualified Theme Id)

      FQPI (Fully Qualified Portlet Id) #

      When configuring plugin portlet references within the portal configurations, the portlet id used must be the Fully Qualified Portlet Id.

      This takes the form of

      portletId_WAR_webapplicationcontext

      The webapplicationcontext

      will have dashes, periods, and spaces stripped away. The portlet id may also require an instance id. The instance id can be made up, and is a 4 char alphanumeric string.

      Examples:

      • Referencing a non-instanceable portlet which is in the core: default.guest.public.layout.column-1=58
      • Referencing an instanceable portlet which is in the core: default.guest.public.layout.column-1=58_INSTANCE_4gtH
      • Referencing a non-instanceable portlet which is in EXT: default.guest.public.layout.column-1=my_ext_portlet_id
      • Referencing an instanceable portlet which is in EXT: default.guest.public.layout.column-1=my_ext_portlet_id_INSTANCE_rgp6
      • Referencing a non-instanceable portlet which is in a plugin, where the plugin WAR context path is /my_plugin-1.3.6: default.guest.public.layout.column-1=my_plugin_portlet_id_WAR_my_plugin136
      • Referencing an instanceable portlet which is in a plugin, where the plugin WAR context path is /my_plugin-1.3.6: default.guest.public.layout.column-1=my_ext_portlet_id_INSTANCE_rgp6_WAR_my_plugin136

      FQTI (Fully Qualified Theme Id) #

      When configuring plugin theme references within the portal configurations, the theme id used must be the Fully Qualified Theme Id.

      This takes the form of

      themeId_WAR_webapplicationcontext

      The webapplicationcontext

      will have dashes, periods, and spaces stripped away.

      Examples:

      • Referencing a theme which is in the core: default.regular.theme.id=theme_id
      • Referencing a theme which is in EXT: default.regular.theme.id=my_ext_theme_id
      • Referencing a theme which is in a plugin, where the plugin WAR context path is /my_plugin-1.3.6: default.regular.theme.id=my_plugin_theme_id_WAR_my_plugin136
      0 Attachments
      47038 Views
      Average (1 Vote)
      The average rating is 5.0 stars out of 5.
      Comments
      Threaded Replies Author Date
      Finding the right value for this seems to be a... Ray Parker October 29, 2010 5:54 AM
      Additionally for Portlets one put one on page;... Corné Aussems August 18, 2015 1:07 AM

      Ray Parker
      Finding the right value for this seems to be a challenge, especially if you don't have an easy means of peeking around in the Liferay database, however I found a simple means which seems to return the correct value. Export a community which uses the theme in question. After the LAR file is downloaded, open it using your favorite archive tool, and look at the manifest.xml file in the root folder. The name of the theme associated with the community will be found on the <header> tag under the theme-id attribute. The theme name will be provided whether you have included the actual theme in the export or not.
      Posted on 10/29/10 5:54 AM.
      Corné Aussems
      Additionally for Portlets one put one on page;
      >> Portlet Wrench (configuration)
      >> Look and Feel
      >> Advanced Styling
      >>> Add a CSS rule for just this portlet. and see the nomenclature in the class.
      Of course source of HTML will do too
      Posted on 8/18/15 1:07 AM in reply to Ray Parker.