Bug 116962

Summary:	Authoring kit details panel on CT page confusing / not for admin
Product:	[Retired] Red Hat Enterprise CMS	Reporter:	Richard Li <richardl>
Component:	ui	Assignee:	Daniel Berrangé <berrange>
Status:	CLOSED RAWHIDE	QA Contact:	Jon Orris <jorris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	nightly	CC:	sseago
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-03-05 19:37:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	113496

Description Richard Li 2004-02-26 21:41:43 UTC

Description of problem:

The authoring kit details panel is:

a) extremely confusing (full of random class names)
b) fragile (there's no validation on component name, for example, so
if you create an invalid component, it gets saved, and you are unable
to author any Content item because the authoring kit wizard
instantiates all authoring kit components)

Solution:

I propose that we remove this panel altogether. IIRC, this was
actually an early APLAWS fork. I'm not sure why it's back in. Dan, can
you comment?

Comment 1 Daniel Berrangé 2004-02-27 10:42:46 UTC

Yeah it was a temporary hack because there was no way to add generic
assets to all authnoring kits. Since i created the
'ContentAssetInitializer' concept its basically redundant & dangerous.
I also think it will break CMS because it doesn't refresh the item.jsp
page to include the components. I had thought about making its
visibiloity a config option (bug 116148), but I think we'll be safer
removing it altogether.

Comment 2 Richard Li 2004-02-27 13:58:15 UTC

removed @40839