| Summary: | "Report a Bug" block breaks Process | ||
|---|---|---|---|
| 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.21.3 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-02-22 02:48:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
It also breaks Refer to relationships:
Pull the Content Spec from the server [6228] [R: 6230]
breaks with the same error.
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. Opps wrong version. It was fixed in 0.21.3. 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&component=documentation&version=5.0&keywords=Documentation&cf_environment=Instance+Name%3A+ECS%0ACSProcessor+Build%3A+0.21.3&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">>> 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...? 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. SPEC ID 6192 They are commented out *because* they are broken... and I need to keep working :-) I've uncommented the Process in 6192, and verified that it still breaks for me. 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. Spec ID 6192 now builds with the Process uncommented. |
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&component=documentation&version=5.0&keywords=Documentation&cf_environment=Instance+Name%3A+ECS%0ACSProcessor+Build%3A+0.21.2&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">>> Next step</link> in <link linkend="LevelID35">Basic Content Spec Tutorial</link> </para>