Bug 1037269

Summary:	RFE: Allow default entities to be used in topics
Product:	[Community] PressGang CCMS	Reporter:	Lee Newson <lnewson>
Component:	CCMS-Core	Assignee:	Lee Newson <lnewson>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.3	CC:	mcaspers
Target Milestone:	---
Target Release:	1.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-23 23:44:03 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:
Bug Depends On:	1051952
Bug Blocks:	1065821

Description Lee Newson 2013-12-03 03:42:40 UTC

Currently you can define custom entities, however you can't use the default entities provided by the builder, which you should be able to use. eg:

&BOOKID;
&YEAR;
&TITLE;
&HOLDER;
&BZURL;
&BZCOMPONENT;
&BZPRODUCT;

These should also be resolved when pushing to Zanata.

Comment 1 Jared MORGAN 2013-12-04 00:36:40 UTC

Noted in 25747

Comment 2 Lee Newson 2014-02-11 05:15:57 UTC

Server and csprocessor fixed in 1.4-SNAPSHOT build 201402111516

The default entities are now included in the building, validation and translation processing.

Note: The UI still needs to be fixed to include the default entities.

Comment 3 Lee Newson 2014-02-15 08:24:00 UTC

UI fixed in 1.4-SNAPSHOT build 201402151749

The UI will now display all content specs (since each content spec is unique). Since this mean that a lot of content specs are shown which can be rather confusing, and is a usability issue I've implemented BZ#1051952. Additionally the rendering information now displays two lots of entities. The "Default Entities" which are generated from the information in the content spec and the "Custom Entities" which are any entities defined by the user.

Comment 4 Matthew Casperson 2014-02-17 02:12:51 UTC

I tested this  by adding the following to a topic:

<itemizedlist>
	<listitem>
		<para> 
			&BOOKID;
		</para>
	</listitem>
	<listitem>
		<para> 
			&YEAR;
		</para>
	</listitem>
	<listitem>
		<para> 
			&TITLE;
		</para>
	</listitem>
	<listitem>
		<para> 
			&HOLDER;
		</para>
	</listitem>
	<listitem>
		<para> 
			&BZURL;
		</para>
	</listitem>
	<listitem>
		<para> 
			&BZCOMPONENT;
		</para>
	</listitem>
	<listitem>
		<para> 
			&BZPRODUCT;
		</para>
	</listitem>
</itemizedlist>

All entities were resolved in the UI when a content spec was selected. Confirmed that the entities resolved in the final build.

I have seen an issue where the &YEAR; differs in the rendered preview to the value displayed in the book. Topic 29049 displays 114 in place of &YEAR; when CS22624 is selected, but the final build displays 2014.

Comment 5 Lee Newson 2014-02-17 02:26:01 UTC

This was caused by the gwt emulation displaying the year from 1990 (hence the 114). I've taken this into account so it should now display properly.

Comment 6 Lee Newson 2014-02-17 03:29:12 UTC

UI Fixed in 1.4-SNAPSHOT build 201402171309.

Note: This version has been deployed to the test/development server.

Comment 7 Matthew Casperson 2014-02-17 03:37:26 UTC

Verified