Posted by morningtime on May 16, 2009 at 7:36pm
Jump to:
| Project: | Category |
| Version: | 6.x-2.0-beta2 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
When viewing a category which has Page nodes belonging to it, no nodes are showing up. Only the category introduction shows up. This happened after upgrade to Drupal 6.12, but I don't know if that was really it. The mentioned do list on other taxonomy term pages. Of course its all set up correctly, and the Page nodes clearly have the right category tag. But that category page is just empty.
Where can I see why nodes aren't being listed?
What lines in the category.module should I look for?
Using Drupal 6.12
Comments
#1
I disabled the "Category Display" module, and now the node listings have returned on category pages.
Why does that happen? It's not clear to me what Category Display does, I can't find any settings, or info in the readme?
#2
And also, the INSTALL.txt contains certain non-existant links:
"Go to 'administer -> settings -> category' to change the settings for this module." There is no such thing as "administer -> settings" in Drupal. There is no 'category' entry under Site Configuration either, where it would be expected. I think the admin url to 'category display' settings is missing?
#3
Final not, the drupal URL admin/settings/category definitely does not exist.
#4
The link should be admin/content/category - obviously an oversight in Drupal 5 -> Drupal 6 porting. This needs to be fixed, if someone roll a patch (I don't have time now, but might get to this later).
There are only few settings in there, though. The Category display behavior (including node listings on category pages, various navigation elements and such) is on the container node, as it affects all categories in a container, but may be different for other containers. Go to your container (top-level page of the tree), click "Edit", and look into the fieldset "Container information", and "Navigation Display" in there. The changes then apply to all categories in that Container.
Also note that some features of Category Display (the Table-Of-Content tree in particular) are now dependent on Category Menu, which in turn may need it's menu structures to be refreshed through the Category Resave tool after upgrade. I would like to highlight my patch waiting at #457590: category_resave needs to use Batch API, and improve usability, which makes Category Resave more usable.
Also there's a bug in update script, which made categories on nodes broken on my site on 5.x->6.x upgrade: #409996: Node's asscociated categories don't show up on node and category page - this might be also part of your problem, but only when your previous version was 5.x.
EDIT: My 6.x testing site is 6.11 now, so perhaps there's some new problem I don't know about.
Category display module have quite a few serious bugs at this moment (Category for 6.x is only just a beta, after all), including #458972: Navigation links PREV/NEXT on categories broken, category_menu_tree_all_data() needs cleanup and #457364: TOC (tree) display missing. I've recently posted quite a few bugfixes to the issue queue, so feel free to test patches and share results in corresponding issues.
The status "needs review" means that there's a patch attached for testing, which is quite not the case here. Also this is more of a support request, but I leave "bug report" for now, due to the INSTALL.txt fix needed.
#5
Now my testing site is on 6.12, and still the listings on category pages are OK. So this is either some sort of misconfiguration, or else more information is needed to reproduce the problem (in order to finally see, track down, and fix the bug).
#6
Seems like I see the problem finally - please verify:
IMO this is a flaw in UI workflow. The Category Display module have a setting, whether to list nodes on category pages, or not. The default is not. Unfortunately, the whole fieldset with Category Display settings (which is on the container's edit form, inside "Container information") is hidden (via JavaScript) until you enable auto-generated menu links, because *some* of the features are dependent on these.
Having nodes listed on category pages is just natural, and doesn't depend on anything, yet it's disabled by default [on new containers]. So on the container edit, you need to enable generated menu links in the menu-related fieldset, so that the Category Display settings become visible, then enable node listings for category pages in there, and then disable menu links again (if you don't want these) - the Category Display settings become invisible again, but once you've set them, they're still there (only just hidden). Now you can submit your container edit, and it should work.
This behavior is really counter-intuitive, and it took me good 30 minutes to figure out, why my experimental categories show nothing - quite a flaw in usability. Having Category Display module enabled due to other containers on the site needing it, yet having menu links for the container in question disabled, is a reasonable use case too. And it only makes sense to disable content listings, after something else is provided/enabled in category_display.
So, in the end, my opinion is that we should just change the default in category_display, so that it shows nodes by default, to ensure that the module being merely enabled doesn't change the display in such an unexpected way.
Going to roll a patch as time permits (which is not today, but I hope soon).
#7
Another category_display default to be possibly adjusted: #409996: Node's asscociated categories don't show up on node and category page
#8
I now addressed the default at #484624: Fix all broken category/container previews, and add category_display defaults, and INSTALL.txt at #484084: Update README.txt and friends - so the bugfix part moved away from this issue. The rest is a support request (I believe), so setting the status that way. If mxistence post no more updates to this issue, it may be closed after some time, I believe.