Bug 979881

Summary:	non-standard apostrophe in contentspec file and topic title causes csprocessor error
Product:	[Community] PressGang CCMS	Reporter:	Julie <juwu>
Component:	CSProcessor	Assignee:	pressgang-ccms-dev
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.1	CC:	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-07-01 05:55:23 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 Julie 2013-07-01 05:33:12 UTC

Description of problem:
If the apostrophes in the content spec file and topic title didn't match, csprocessor returns an error when validating. I think it used to work without an error. 

Actual results:
[asettle@dhcp-1-185 Insight]$ csprocessor push
CSProcessor client version: 0.33.1
Loading configuration from /home/asettle/.config/csprocessor.ini
Loading project configuration from csprocessor.cfg
Connecting to PressGang server: http://skynet.usersys.redhat.com:8080/TopicIndex/

Starting to parse...
Starting first validation pass...
Attempting to download all the latest topics...
Starting second validation pass...
ERROR: Line 503: Invalid Topic! Existing topic title doesn't match.
       -> Specified: To download a Timeline’s data
       -> Topic 15485: To download a Timeline's data
ERROR: The Content Specification is not valid.

Expected results:
csprocessor to function as normal

Comment 1 Lee Newson 2013-07-01 05:55:23 UTC

This is expected behaviour as the titles technically don't match. If you know all the title mismatches are just due to a topic title rename and not from using the wrong topic then you can add the "--permissive" (or "-p" for short) option to fix the titles up when the Content Spec is saved.