This article is a legacy article. It applies to previous versions of the Liferay product. While the article is no longer maintained, the information may still be applicable.
This article documents a known issue where users are able to deactivate the default Liferay Portal site, which then prevents access to any existing live site with a public page. The basic functionality is that as long as there is one live site with a public page, users should be able to log in. However, there is a bug where users see a warning message, This site is inactive. Please contact the administrator, when they attempt to access the Control Panel.
This issue exists on legacy Liferay Portal 6.1 EE and 6.2 EE.
Resolution
Steps to Reproduce
- Navigate to the Control Panel → Sites.
- Click Add → Community Site. (It does not matter which site template as long as there is a page on the site).
- Enter the following:
- Name: Site 1
- Details: Site 1 description
- Click Save.
- Navigate to the Control Panel → Sites.
- Click Liferay site.
- Click Configuration → Site Settings.
- Uncheck the Active checkbox.
- Click Save.
- Sign out.
- In the browser URL, enter the following:
http://${your host name}:${your port number}/web/site-1. (e.g.http://localhost:8080/web/site-1) - Users should see that they are able to view Site 1 pages.
- Next, attempt to access the Control Panel from the URL:
http://${your host name}:${your port number}/group/control_panel(e.g.http://localhost:8080/group/control_panel).
At this point, the error message appears.
Workaround:
In order to gain access to the Control Panel once more, administrators must reactivate the default Guest site.
Solution
This issue has been resolved in Liferay Portal Fix Pack Portal-151. The fix pack introduced a new change in functionality so that the default Guest site cannot be deactivated.
Additional Information
If the platform has an Single Sign-On or Single Log-out (SSO/SLO) like SAML or Shibboleth enabled, the SSO settings will override and redirects to the SSO specified Identity Provider URL.
This known issue is also found in Liferay Portal 6.1 EE. Because this version has reached EOSL, only subscribers with extended premium support will receive a fix if they request one.