Bug 791080 - When editing a topic as IA, tags under SOA-P are greyed out
Summary: When editing a topic as IA, tags under SOA-P are greyed out
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Matthew Casperson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-16 05:12 UTC by Matthew Casperson
Modified: 2014-08-04 22:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-01 23:26:59 UTC


Attachments (Terms of Use)
Basic fix patch (1.85 KB, patch)
2012-02-16 05:56 UTC, Lee Newson
no flags Details | Diff

Description Matthew Casperson 2012-02-16 05:12:04 UTC
The tags are available under the admin login, so it must be a permissions issue.

The tags are available when creating a new topic.

Comment 1 Lee Newson 2012-02-16 05:34:54 UTC
I had a quick look at this. The reason that they are greyed out is because no rule is setup for those categories in security.drl. The ones that I can see that are missing are:

Audiences
Book
Engineering Priority
PM Priority
SME Priority
Writer Priority
SME Reviewers
Nav Priority
Project

As for being able to select the tags when creating the topic I was unable to replicate this as they were greyed out for me.

Comment 2 Lee Newson 2012-02-16 05:56:02 UTC
Created attachment 562397 [details]
Basic fix patch

Added a basic patch that includes all the missing categories and set's the roles for them to writer and ia. This may need revising depending on what should be accessible for each category.

Comment 3 Matthew Casperson 2012-02-17 03:53:05 UTC
Fixed in 20120217-1345

These security restrictions have not been consistently applied, so I have just removed the permission check on the categories. System security will 
require a system wide review, and categories can be locked down.


Note You need to log in before you can comment on or make changes to this bug.