[ALF-918] System error after click button "cancel" on page Regenerate Renditions Wizard for Content Publisher (Contributor or Reviewer) Created: 14-Dec-09  Updated: 31-Aug-16  Resolved: 20-Apr-10

Status: Closed
Project: Alfresco
Component/s: ZZ_Archive
Affects Version/s: 3.2 Enterprise
Fix Version/s: 3.3 Enterprise

Type: Bug Priority: Minor
Reporter: Alfresco QA Team (Inactive) Assignee: Closed Bugs (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Alfresco 3.2 EE b 290 Stack 3 Solaris 10 Sparc x64, Weblogic 10.3.2.0, Oracle 11.2.0.1.0 x64, JDK 6u17 x64, Sun One Directory 5.2, Vista SP1 , IE 7


Attachments: PNG File №1 Click next.png     PNG File №2 Click Cancel.png    
Issue Links:
Related
relates to ALF-986 Content Publisher has no permissions ... Closed
Date of First Response:

 Description   

Pre-conditions:
1. Any Web Project "Test" with assigned Web Forms(e.g. Test1, Test2) is created by admin;
2. Any of these forms has rendering engine templates;
3. Several contents based on each of Web Forms in Web Project "Test" are created;
4. Full workflow for contents is made;
5. User 1have been invited to the project as Content Publisher (Contributor or Reviewer);
6. User 1 is logged in;
7. Data Dictionary->Web forms page is opened;

Steps
1. Go to 'More Actions' menu and select 'Regenerate Renditions';
2. Select "Test" project;
3. Select any criteria;
4. Click "Next" button; -> display message "Not allowed to write in:" (see screenshot №1)
5. Click 'Cancel' button; -> display error page (see screenshot №2)

expect result:
Web forms page is opened

andreyMa



 Comments   
Comment by Alfresco QA Team (Inactive) [ 14-Apr-10 ]

The exception also occurs against Alfresco 3.2.1 EE b 495 - Stack 1 (environment: Suse 11.1, Websphere 7.0.0.7, Oracle 10.2g, Alfresco +OpenLDAP Client: MacOS X 10.5.5, Safari 3.2.1)

Comment by Steven Glover [X] (Inactive) [ 15-Apr-10 ]

Seems to be only users in the WCM Content Manager role and the admin user can invoke Regenerate Renditions successfully. Other roles result in permission exceptions. I suspect the original intention was that only Content Managers or admin should have access to this functionality in the GUI and that it should probably be inaccessible for users in other roles i.e. not appear in the drop down in the GUI.

Comment by Steven Glover [X] (Inactive) [ 20-Apr-10 ]

Lowered priority to minor given that only admin or Content Managers should be able to perform this operation and the operation works fine for those users.

However, the GUI is exposing the regenerate renditions action to users without the permissions to perform the action. The fix will ensure that the regenerate renditions action is exposed only to admin users, and users with CONTENT MANAGER permissions on at least one web project. Similarly, the web project drop down list on the first screen of the Regenerate Renditions Wizard will display only web projects that meet the criteria above.

I will also update http://wiki.alfresco.com/wiki/WCM_roles accordingly.

Comment by Steve Rigby [X] (Inactive) [ 12-May-10 ]

For retest in 3.3E build 27

Comment by Alfresco QA Team (Inactive) [ 15-May-10 ]

Successfully validated on Alfresco Enterprise 3.3. build 34
(RHEL 5.1 x64, Tomcat 6.0.18, Mysql 5.1.35, JDK 6u16 x64, FF3.6)

If user has Manager permissions to one of the created Web Projects, then "Regenerate Renditions" button is displayed for Web Forms, in other cases functionality is disabled.

Comment by Derek Hulley [X] (Inactive) [ 31-Aug-16 ]

The component originally used was not a supported, recognisable system component with an associated component owner. Either the component never existed (it was fictional) or it has reached end-of-life.
The issues will be closed. Reopen and assign to an existing system component if necessary. Use labels appropriately.

Generated at Sun Mar 07 18:32:49 GMT 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.