Red Hat Bugzilla – Bug 100978
Parent content type shown is always the same as the content type name
Last modified: 2007-04-18 12:56:13 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Description of problem:
From the 'Content Types' tab of the Redhat CMS, when selecting any of the
predefined content types e.g. Agenda, Event etc, or selecting any new custom
content types the 'Parent content type' is shown incorrectly.
i.e. if you select the News Item content type its parent is shown as 'News
Item'. If you create a new custom content type called 'Foo' whose parent
content type is 'Article', the parent content type is always shown also
as 'Foo'. When creating new instances of Foo it is clear that
actually 'Articule is being used as the parent content type.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create a new custom content type e.g Test, with a parent content type
selected e.g. Article.
2.After creating the content type its parent will be shown incorrectly.
Actual Results: The parent content type is shown incorrectlya as 'Test'.
Expected Results: The parent content type should have been shown as 'Article'.
Which nightly are you on? This works correctly on the tip.
Thanks for your response.
I'm using the following nightly builds:
These were the latest nightly builds I could find. I'll try checking out the
latest src from CVS and retesting this.
Note that currently the CVS repos appears to be overloaded as I repeatedly
"cvs [checkout aborted]: Error reading from server cvs.sourceforge.net: 0 "
using either the hostnames of cvs.ccmdev.sourceforge.net and
cvs.sourceforge.net. I was finally able to check out the source after a number
I'll validate the issue is fixed and update the bug accordingly.
Yes, that's pretty old.
We don't maintain the CVS sources; the community does with sourceforge. My
understanding is that SF is having scalability problems due to the enormous
number of projects that they serve.
The link http://rhea.redhat.com/faq.html#where-download-ccm directs me to
a) version 5.0 which is old
b) the nightly builds where the latest appears to be *5.3.0.AUTO.07.08.2003*
which has the bug described above in it.
c) CVS which has connection issues currently.
Where can I obtain the latest 'tip' code to retest this issue e.g. a nightly
build from 29th July 2003?
Tested and fixed in the nightly build from the 29/8/2003.