Bug 795410 - "Report a Bug" block breaks Process
Summary: "Report a Bug" block breaks Process
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-20 12:44 UTC by Joshua Wulf
Modified: 2014-10-19 23:00 UTC (History)
2 users (show)

Fixed In Version: 0.21.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-22 02:48:09 UTC


Attachments (Terms of Use)

Description Joshua Wulf 2012-02-20 12:44:28 UTC
The Content Spec:
 Process: Basic Content Spec Tutorial
    Create your first Content Spec [6224]
    Push your first Content Spec to the server [6225] [P:6224]


The xml error:
expected ..... got (title para para procedure formalpara simplesect para )

It's the para after the simplesect that blows it up.


Here's the invalid xml output:

	</formalpara>
	 <simplesect> <title></title>
	 <para role="RoleCreateBugPara">
		<ulink url="https://bugzilla.redhat.com/enter_bug.cgi?product=Internal&amp;component=documentation&amp;version=5.0&amp;keywords=Documentation&amp;cf_environment=Instance+Name%3A+ECS%0ACSProcessor+Build%3A+0.21.2&amp;cf_build_id=6224-39650+20+Feb+2012+19%3A59+en_US">Report a bug</ulink>
	</para>
	 </simplesect> <para role="process-next-link">
		<link linkend="TopicID6225">&gt;&gt; Next step</link> in <link linkend="LevelID35">Basic Content Spec Tutorial</link>
	</para>

Comment 1 Joshua Wulf 2012-02-20 12:47:28 UTC
It also breaks Refer to relationships:

    Pull the Content Spec from the server [6228] [R: 6230]

breaks with the same error.

Comment 2 Lee Newson 2012-02-20 23:04:55 UTC
Fixed in server version 0.21.4.

I had already discovered and fixed this problem over the weekend, however I must of reverted the change somewhere. I'll be sure to be more careful when reverting/committing in the future. Anyways the error was caused by processing bugzilla injections at the same time as regular skynet injection. However relationships are processed after that and as such they were being injected after the bugzilla links. So now the bugzilla are injected as the very last step.

Comment 3 Lee Newson 2012-02-20 23:05:38 UTC
Opps wrong version. It was fixed in 0.21.3.

Comment 4 Joshua Wulf 2012-02-21 01:37:20 UTC
Web Service at http://csprocessor.cloud.lab.eng.bne.redhat.com:8080/ version: 0.21.3


....


	 <simplesect> <title></title>
	 <para role="RoleCreateBugPara">
		<ulink url="https://bugzilla.redhat.com/enter_bug.cgi?product=Internal&amp;component=documentation&amp;version=5.0&amp;keywords=Documentation&amp;cf_environment=Instance+Name%3A+ECS%0ACSProcessor+Build%3A+0.21.3&amp;cf_build_id=6227-39795+21+Feb+2012+10%3A35+en_US">Report a bug</ulink>
	</para>
	 </simplesect> <para role="process-next-link">
		<link linkend="TopicID6235">&gt;&gt; Next step</link> in <link linkend="LevelID35">Basic Content Spec Tutorial</link>
	</para>


Looks like the Next link is still being injected after the bug link...?

Comment 5 Lee Newson 2012-02-21 10:40:16 UTC
I can't reproduce this using the same server files as the production server on the test server or locally. Can you please either attach the Content Spec or give me an ID for the item on the live servers, as I can't see any that have a process not commented out.

Comment 6 Joshua Wulf 2012-02-21 13:10:16 UTC
SPEC ID 6192

They are commented out *because* they are broken... and I need to keep working :-)

Comment 7 Joshua Wulf 2012-02-21 13:11:03 UTC
I've uncommented the Process in 6192, and verified that it still breaks for me.

Comment 8 Lee Newson 2012-02-21 23:01:13 UTC
Fixed in 0.21.4

Cause:
The injector was injecting the bugzilla link into the original topic. Duplicate were then cloning this topic.

Consequence:
Any duplicated topics, besides the first one would break when injected with bugzilla links because the injector was injecting into the original topic.

Fix:
Made the injector, inject the links into the cloned topic.

Comment 9 Joshua Wulf 2012-02-22 02:48:09 UTC
Spec ID 6192 now builds with the Process uncommented.


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