-
Type:
Regression Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.2.0 CE RC1, 6.2.0 CE RC2
-
Fix Version/s: 6.2.0 CE RC1, 6.2.0 CE RC2
-
Labels:None
-
Environment:Tomcat 7.0 + MySQL 5. Portal 6.2.x master GIT ID: ab3891a0e643fae1de9e24eba39d3211decb3c23.
Plugins ee-6.2.x master GIT ID: 863dfb49565d8efe89551667500ab3aad836382d.
-
Fix Priority:5
Steps to Reproduce:
- Deploy Kaleo Web Plugin
- Add a Community Site
- Unflag Enable propagation of changes from the site template Community Site
- Click Staging > Activate Local Live
- Flag Enabled on Public Pages
- Click Workflow Configuration
- Select [Single Approver (Version 1)] next to Page Revision
- Add a Site Role
Name: Staging Admin - Click Define Permissions > Site Administration > Pages > Site Pages
- Flag all the Action checkboxes
- Add a Site Role
Name: Web Content Creator - Click Define Permissions > Site Administration > Content > Web Content
- Flag all the Action checkboxes
- Click Define Permissions > Site Administration > Applications > Web Content Display
- Flag the Action checkbox > Save
- Add a User
Screen Name: contentcreator
Email Address: [email protected]
First Name: ContentCreator - Set a password
- Click Sites under User Information
- Click Select link > Community Site Test > Save
- Click Roles under User Information
- Click Select link near Site Roles > Staging Admin
- Click Select link near Site Roles > Web Content Creator
- Navigate to Community Site Test
- Assert staging
- Sign Out
- Sign in as [email protected]
- Navigate to Community Site Test > Staging
- Add Web Content Display portlet
- Click Staging > Submit for Publication
- Click Publish to Live > Publish
Expected result:
ContentCreator should not be able to publish to live, as another user must approve the publication first.
Actual result:
ContentCreator cannot publish to live, but the Publish to Live window displays both a, “Your request completed successfully” message and “Failed” message. When the user clicks on “Details?” next to the “Failed" message the following error message is displayed:
An unexpected error occurred with the publication process. Please check your portal and publising configuration. com.liferay.portal.NoSuchLayoutException: No Layout exists with the primary key 0
These conflicting messages are confusing.
Either a message should be displayed explaining the the user ContentCreator does not have permission to publish directly to live, or the Publish to Live button should not display at all when the current user does not have permission to publish to live.
When navigating to the live site, the Web Content Display portlet is not published as expected.
See attached .gif.