Bug 99043
Summary: | in category-based search, each category is listed twice in the drop-down list | ||
---|---|---|---|
Product: | [Retired] Red Hat Enterprise CMS | Reporter: | Vadim Nasardinov <vnasardinov> |
Component: | other | Assignee: | ccm-bugs-list |
Status: | CLOSED WONTFIX | QA Contact: | Jon Orris <jorris> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | nightly | ||
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: | 2005-08-03 18:26:03 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: |
Description
Vadim Nasardinov
2003-07-12 16:27:03 UTC
My speculation is, the list of categories is not filtered by section. I have two content sections in my setup. They have identical (yet physically distinct) category trees. I am guessing, the drop-down list is populated by querying all categories out of the categories table, without restricting it to a single section. Vadim, can you check what XML files your enterprise.init is specifying for loading categories. The default configuration should load '/WEB-INF/resources/article-categories.xml' into the /content/ section and '/WEB-INF/resources/form-categories.xml' into the '/forms/' section. Change 24890 way back when we were doing 5.2 dev made sure that both these files specified different categories precisely to avoid the confusion in the seach box that is described above. In addition, doing a 'select * from cat_categories' in my newly loaded DB doesn't show any duplicated categories: dan_troika=# select category_id, name, default_ancestors from cat_categories order by name; category_id | name | default_ancestors -------------+--------------+------------------- 28 | / | 28/ 4010 | / | 4010/ 53 | Alternative | 37/50/53/ 38 | Arts | 37/38/ 55 | Arts | 37/54/55/ 4022 | Bugs | 4019/4020/4022/ 42 | Business | 37/42/ 46 | Computers | 37/46/ 4025 | Events | 4019/4024/4025/ 4020 | Feedback | 4019/4020/ 51 | Fitness | 37/50/51/ 4021 | General | 4019/4020/4021/ 49 | Hardware | 37/46/49/ 50 | Health | 37/50/ 44 | Industries | 37/42/44/ 47 | Internet | 37/46/47/ 45 | Investing | 37/42/45/ 43 | Jobs | 37/42/43/ 54 | Kids | 37/54/ 52 | Medicine | 37/50/52/ 39 | Movies | 37/38/39/ 41 | Music | 37/38/41/ 4027 | Other | 4019/4024/4027/ 4026 | Profile | 4019/4024/4026/ 4024 | Registration | 4019/4024/ 37 | Root | 37/ 4019 | Root | 4019/ 56 | School Time | 37/54/56/ 48 | Software | 37/46/48/ 4023 | Suggestions | 4019/4020/4023/ 57 | Teen Life | 37/54/57/ 40 | Television | 37/38/40/ (32 rows) dan_troika=# I have two content sections that load the same category tree. Hence the duplicate. Making sure that no two categories have the same name in two separate category trees sounds like a non-solution to me. Correct me if I am wrong, but the the search interface located under the "Search" tab of the content section page is meant to be restritec to that content section. Therefore, the category tree should also be one used for that content section. I have two content sections: SQL> select section_id, pretty_name from content_sections; SECTION_ID|PRETTY_NAME ----------|------------------------------ 110|articles 161|cs2 Each of them has a separate category tree: SQL> select * from cat_root_cat_object_map; CATEGORY_ID| OBJECT_ID -----------|---------- 167| 161 116| 110 The category tree for content section 110 looks like so: SQL> select category_id, name from cat_categories where default_ancestors like '116/%'; 2 3 CATEGORY_ID|NAME -----------|-------------------- 116|Root 117|Arts 118|Movies 119|Television 120|Music 121|Business 122|Jobs 123|Industries 124|Investing 125|Computers 126|Internet 127|Software 128|Hardware 129|Health 130|Fitness 131|Medicine 132|Alternative 133|Kids 134|Arts 135|School Time 136|Teen Life 21 rows selected. The category tree for content section 161 looks like so: SQL> select category_id, name from cat_categories where default_ancestors like '167/%'; 2 3 CATEGORY_ID|NAME -----------|-------------------- 167|Root 168|Arts 169|Movies 170|Television 171|Music 172|Business 173|Jobs 174|Industries 175|Investing 176|Computers 177|Internet 178|Software 179|Hardware 180|Health 181|Fitness 182|Medicine 183|Alternative 184|Kids 185|Arts 186|School Time 187|Teen Life 21 rows selected. Is there any reason not to filter the drop-down list of categories by section? To avoid confusion, I should make it clear that I ran the queries against a different server instance. Hence the mismatch between the id's in my original post and my previous comment. stale |