Bug 743487 - Topic Title injects incorrectly in template
Summary: Topic Title injects incorrectly in template
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Matthew Casperson
QA Contact: David Ryan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-05 05:41 UTC by David Ryan
Modified: 2015-02-01 23:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-09 22:49:34 UTC


Attachments (Terms of Use)

Description David Ryan 2011-10-05 05:41:58 UTC
20111004-1127 /CustomSearchTopicList.xhtml

The Topic Title is currently injecting incorrectly into the default template. 

The following example is a dummy topic created with only a Topic Title entered into the Topic Title field of a new topic in Skynet. Once Generate Detail Comment is clicked, the template populates with the Topic Title appended immediately under the <procedure> element. 

It should be populating up where the the <!-- INJECT TITLE HERE --> comment exists on line 2. 

As a result, all new topics are failing validation unless the author addresses this manually. Example as follows:

http://pastebin.test.redhat.com/63560

Comment 1 Matthew Casperson 2011-10-05 05:44:18 UTC
topics 5015,5036,4699,4432,4430,5033,4585,4586,4571,5222,2448,5176,4719,4747,3877,3878,3879,4825,4307 are affected (from Misty)

Comment 2 Misty Stanley-Jones 2011-10-05 06:06:56 UTC
All are fixed now but 5222, which I am about to fix. Here is its broken XML. The formalpara is supposed to be titled Overview, I think. The section title got put there instead.

<?xml version="1.0" encoding="UTF-16"?>
<section>
  <!-- INJECT TITLE HERE -->
  <!-- Uncomment prerequisites and result if required. -->
  <!-- Replace all text marked with ** and leave other text -->
  <!--
	  <itemizedlist>
	  <title>Prerequisites</title>
	  ** inject list items here **
	  </itemizedlist>
  -->
  <formalpara>
	<title>Configure server advertisement properties for your mod_cluster-enabled HTTPD</title>
	<para>
	  For instructions on configuring your HTTPD to interact with the
	  mod_cluster load balancer, refer to <!-- Inject: 5218 -->. One aspect of
	  the configuration which needs more explanation is <firstterm>server
	  advertisement</firstterm>.
	</para>
  </formalpara>
  <para>
	When server advertisement is active, the HTTPD broadcasts messages
	containing the IP address and port number specified in the mod_cluster
	virtual host. To configure these values, refer to <!-- Inject: 5218 -->. If
	UDP multicast is not available on your network, or you prefer to configure
	worker nodes with a static list of proxy servers, you can disable server
	advertisement and manually configure the worker nodes. Refer to <!-- Inject:
	5223 --> for information on configuring a worker node.
  </para>
  <procedure>
	<title>Task</title>
	<step>
	  <title>Disable the <code>AdvertiseFrequency</code> parameter, if it exists.</title>
	  <para>
		If you have a line like the following in your
		<sgmltag>&lt;VirtualHost&gt;</sgmltag> statement, comment it out by
		putting a <literal>#</literal> (hash) character before the first
		character. The value may be different from <literal>5</literal>.
	  </para>
	  <screen>AdvertiseFrequency 5</screen>
	</step>
	<step>
	  <title>Add the directive to disable server advertisement.</title>
	  <para>
		Add the following directive inside the
		<sgmltag>&lt;VirtualHost&gt;</sgmltag> statement, to disable server
		advertisement.
	  </para>
	  <screen>ServerAdvertisement Off</screen>
	</step>
	<step>
	  <title>Restart the HTTPD server.</title>
	  <para>
		Restart the HTTPD server by issuing one of the following, depending on
		whether you use Red Hat Enterprise Linux or Microsoft Windows Server.
	  </para>
	  <stepalternatives>
		<step>
		  <title>Red Hat Enterprise Linux</title>
		  <screen>[root@host ]# service httpd restart</screen>
		</step>
		<step>
		  <title>Microsoft Windows Server</title>
		  <screen>C:\&gt; net service httpd stop
		  C:\&gt;net service httpd start</screen>
		</step>
	  </stepalternatives>
	</step>
  </procedure>

  <formalpara>
	<title>Result</title>
	<para>
	  The HTTPD no longer advertises the IP address and port of your mod_cluster
	  proxy. To reiterate, you need to configure your worker nodes to use a
	  static address and port to communicate with the proxy. Refer to <!--
	  Inject: 5223 --> for more details.
	</para>
  </formalpara>

  <!-- Generated Topic Details

GENERAL DETAILS

Topic ID: 5222
Topic Title: Configure server advertisement properties for your mod_cluster-enabled HTTPD
Topic Added By: 
Topic Description: 

TOPIC TAGS

4: Task
13: IA Proposed
30: IA Low Priority
48: High Availability (HA) Clustering
50: mod_cluster
58: Configuration
71: Assigned
90: mstanley
132: EAP 6 Beta

SOURCE URLS


RELATED TOPICS

5218: Install the mod_cluster module into Apache HTTPD or Enterprise Web Server HTTPD

  -->
</section>

Comment 3 Matthew Casperson 2011-10-06 22:04:33 UTC
Fixed in 20111007-0803

Comment 4 David Ryan 2011-10-09 22:49:34 UTC
Verified in build 20111007-1458 per test below. Title now correctly injects under the <section> element, with the template's <title>Task</title> element string restored to the <procedure> section as a separator from Summary and Prerequisite blocks. 

<?xml version="1.0" encoding="UTF-8"?>
<section>
    <title>Title Inject Fix Test</title>
    <!-- INJECT TITLE HERE -->
    <!-- Uncomment prerequisites and result if required. -->
    <!-- Replace all text marked with ** and leave other text -->
    <!--
     	<itemizedlist>
        	<title>Prerequisites</title>
        	** inject list items here **
     	</itemizedlist>
	-->
    <procedure>
        <title>Task</title>
        <!-- "Task" title only required to visually separate task from prerequisites -->
        <step>
            <title>** step title **</title>
            <para>** step instructions **</para>
        </step>
        <step>

--snip--


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