Bug 767000

Summary:	Duplicate IDs on elements when topic included more than once
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Lee Newson <lnewson>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	jwulf, lcarlon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	0.20.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-20 01:44:48 UTC	Type:	---
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 2011-12-12 23:40:50 UTC

We've solved it for the section ID, but there are elements inside the section that have IDs on them. 

For example, a topic may have a table in it, and the table may have an ID. When the topic is used twice in the same namespace the section ID is rewritten to a unique ID, but the table ID is not.

The workaround in the meantime is to not put an ID on an element within a section (within a topic).

Comment 1 Lee Newson 2012-01-31 05:07:35 UTC

Fixed.

Now when processing the topics the builder will parse the entire XML data and append to the id a number (this is done before topic injection so that the injected id's are messed up). For the first topic that is a duplicated the id will be left as it originally is incase the id is used as a link. For every ID after that it adds the suffix "-<number>" where <number> is a counter starting from 1.

This should not break any links in the content spec and it should also allow id's to be used within a topic that is duplicated.