Bug 113591 - Categories available from assign categories are not the same as those visible via categories admin screen
Summary: Categories available from assign categories are not the same as those visible...
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: APLAWS-usability
Version: nightly
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact: Daniel Berrangé
URL: http://aplaws-ws3.ccm-demo.redhat.de/...
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-15 17:04 UTC by Lindsay Ould
Modified: 2007-08-01 18:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-08-01 18:47:37 UTC

Attachments (Terms of Use)

Description Lindsay Ould 2004-01-15 17:04:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET 
CLR 1.1.4322)

Description of problem:
I changed the names of some of the categories yesterday to reflect 
the category purposes that are used in APLAWS and to see how these 
display in the summary page.

The list I see in the assign category step is different from the one 
that is in the category admin screen and if I add a new category this 
is not available to assign

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. create new item
2. select assign category step
3. select sections: content and categorisation tab
4. compare two lists of categories    

Additional info:

Comment 1 Scott Seago 2004-01-15 17:17:05 UTC
We've recently redone the underlying categorization API to change the
way we handle category purposes. The item categorization step has not
yet been updated to reflect this.

What seems to be happening currently is that the categorization step
is showing the default category root for the /forms content section,
even though we're currently within the /content content section.

Comment 2 Scott Seago 2004-01-22 20:39:54 UTC
Thi sshould be  resolved as of the recent rewrite of the categories
authoring step.

Comment 3 David Lawrence 2006-07-18 03:05:14 UTC
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.

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