Red Hat Bugzilla – Bug 113741
6.1 Naming Conventions for Content types
Last modified: 2010-09-03 10:28:19 EDT
Description of problem:
News Content Type - Spec states 'Date' rather than 'News Date' as
implemented - is there a reason that it has to be called 'News Date'
or can it revert to 'Date'
Event Content type - 'Description' field does not display correctly -
suspect this will be resolved with HTML editor sizing issues
Multipart Article - 'Sections' is used in 5.2 - This has been changed
to 'Body Text' in this release although not specified. Unsure of
which is more user friendly - was there a reason for changing it?
Press Release Content type - 'Description' field does not display
correctly - suspect this will be resolved with HTML editor sizing
Version-Release number of selected component (if applicable):
Steps to Reproduce:
News: change made.
Multipart Article body text: This was changed in the 6.0 time frame,
before the WS3 work began. I'm not sure why it was changed.
The remaining issues should be fixed with the HTML editor sizing
issues in next week's bugfixing
> Multipart Article body text: This was changed in the 6.0 time frame,
> before the WS3 work began. I'm not sure why it was changed.
This was a specific request from Camden Intranet during 5.2 work.
Press Release Content type: Description field has no border when
opened with Edit.
Event Content type: No border for fields currently
labelled "cms.contenttypes.ui.lead" and "Link to Map"
Press Release Content type: The vital Launch Date field is missing.
This used to sit between Title and Ref. Code in Aplaws 5.2 Basic
Properties back-end user interface.
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.