Bug 846552 - RFE: Validate Topic Title and ID in Human-readable Relationships
Summary: RFE: Validate Topic Title and ID in Human-readable Relationships
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-08 06:35 UTC by Joshua Wulf
Modified: 2014-10-19 23:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-24 22:39:12 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 837960 0 unspecified CLOSED RFE: Human readable relationships 2021-02-22 00:41:40 UTC

Internal Links: 837960

Description Joshua Wulf 2012-08-08 06:35:46 UTC
As of 0.26.2-1, the topic title used in Human-readable relationships is not validated with the topic ID specified. This can cause unpredictable output when a human readable title does not match the topic specified by the ID.

Two tasks to align this:

1. Validate topic title and topic ID of all human-readable relationships and produce an error list when they do not match.
2. Add logic to --permissive, -p to realign relationship block titles with the canonical title based on the ID specified.

Comment 1 Joshua Wulf 2012-08-08 06:37:27 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=837960#c3 is the Human-readable relationships feature request

Comment 2 Joshua Wulf 2012-08-08 09:05:18 UTC
[Feature Status Note added to docs, needs to be updated when feature is ready:

http://deathstar1.usersys.redhat.com:8080/TopicIndex/Books/Content_Spec_Processor_Guide/index.html#Referto_relationship

Topic ID: 6252]

Comment 3 Lee Newson 2014-02-24 22:39:12 UTC
This has been in csprocessor for some time (I'm not sure what version it got added), however due to the change we did in 1.0 this now works in reverse. ie It will print a warning by default, and error when strict title processing is in place.


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