Bug 866751

Summary:	RFE: Throw a Warning/Error when two topics exist in a Content Spec with the same ID, but different Revisions
Product:	[Community] PressGang CCMS	Reporter:	Lee Newson <lnewson>
Component:	CSProcessor	Assignee:	pressgang-ccms-dev
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	thildred
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-06-07 01:31:29 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 Lee Newson 2012-10-16 04:06:12 UTC

The CSP should display a warning or an error when two topics are used in a Content Specification that have the same ID but different revisions.

An example of from thildred as to why it should possibly be an error instead of a warning:

"take the example where two revisions represent two very different versions of a topic (like before and after a new ui was announced). If you allow two revisions of the same topic, you might allow two different sets of instructions on how to do something"

Comment 1 Lee Newson 2012-10-19 00:59:55 UTC

Added in 0.27.5.

Example output:

Starting to parse...
Starting first validation pass...
ERROR: Invalid Content Specification! Topic 8649 has two or more different revisions included in the Content Specification. The topic is located at:
       -> Revision 252830, lines(s) 71.
       -> Revision 286357, lines(s) 370.
ERROR: Invalid Content Specification! Topic 7320 has two or more different revisions included in the Content Specification. The topic is located at:
       -> Revision 180219, lines(s) 135, 182 and 276.
       -> Revision 274895, lines(s) 332, 404, 496, 522 and 545.
ERROR: The Content Specification is not valid.

Comment 2 Lee Newson 2013-06-07 01:31:29 UTC

Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.