Bug 976111

Summary:	RFE: Protect content specs from manual editing
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	Web-UI	Assignee:	pressgang-ccms-dev
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.1	CC:	lcarlon, lnewson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-01 03:52:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joshua Wulf 2013-06-19 23:58:54 UTC

Description of problem:

At the moment users can edit content specs in the web editor with no validation. This results in broken content specs. It's especially a problem for new users, because they rightly expect that the system would not allow them to do something that would break their stuff without warning them.

Solution:

The immediate solution should be to make content specs read-only in the web editor. It can be done trivially with JavaScript:

if (topic.isContentSpec()) makeEditorReadOnly();

If you wanted to make it user friendly, you could put a link to the death star content spec editor, a GUI wrapper for the content spec processor, while you are waiting for your own web-based solution. Otherwise, a notice telling them to use the csprocessor to edit the spec (please- no modal dialogs! :-) would be good.

Comment 1 Lee Newson 2013-09-01 03:52:30 UTC

Closing this as won't fix since we will be moving to the new editor very shortly. If anyone tries to edit an old content spec topic in the editor then they will be prompted to use the new editor.