I posted this issue there first but it was suggested that I might find more help here.

The new, Drupal 7 version of Ubercart uses Views to display its catalog listing and it does not hide empty terms used for the catalog listing like it did in the previous versions (without Views for the catalog). We have imported hundreds of nested taonomy terms for the catalog that will take a while to populate. In the meantime, we need to hide the all terms who do not have any product nodes assosiated with them through out its nested tree.

I found some threads suggesting to enable the "content with term" relationship but this hides all of the catalog terms because there are no products in 1st nest of terms.

Example:

Catalog->Top Level Term->Second Level Term->Products

Because the products are several terms deep it will hide all terms because there are no product nodes in the higher level term levels.

Any ideas on how to accomplish this?

This issue is compounded when using the catalog block because the block automatically filters out empty terms but the pages do not. Both catalog types should match (like UC2)

I have spent more than several hours working on this but haven't had any luck. Any ideas?

Comments

kars-t’s picture

kars-t commented
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed".

If there is new information, please re-open the issue.

--
This issue was edited with the help of Issue Helper

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.