Hello,

I created new content type and used CCK to create field for it. The I used Category module to create a container and child categories for this content type.

In container setting, I already enabled all related selections in 'Category display settings' and 'Category menu items'. The problem is that the links for pre and next are only displayed on the pages of container and categories, but not displayed on node pages. Also, navigation breadcrumb links did not show on any pages.

Also, I enabled Printer-friendly HTML in 'Category export settings', but that print link only shows for container and categories pages, but not for node pages.

I carefully checked every seeting, but still can not get above problem solved. Is there anything I missed? Thanks a lot for your help.

Regards,
Derek

Comments

huayen’s picture

huayen commented

You can check my site display here:

http://featips.com/node/1

huayen’s picture

huayen commented

Everytime I submitted a node, I got following information:

cac_lite module has been installed, but has not been configured.

In backend administration, there is a ca_lite:
-------
Select one or more containers which limit access.
sac_lite_admin_settings
----------

But both 'settings' and 'access by role' are deactivated, no way to make a setting.

In access control region, I really don't see where to set permission, because my nodes are not accessible to users except administrator.

inforeto’s picture

inforeto commented

The previous and next links, the TOC and the category views are category behaviours set on the container display.

To have nodes show up as book pages, like categories, they must be transformed into actual categories through the "category_transform" part of the module.

On the category settings page, there's a section with category transform options where you select which content type you want to be used for these behaviours.

Once the cck type is selected, the nodes get new tabs with the category or container options.
Read through the other issues if these do not function.

huayen’s picture

huayen commented

Indeed, I already know the answer. ANyway, thank you for your answer. I exactly followed the tutorials on the module homepage, hooking my CCK type with a container, so that all new submitted node will become a category. (no need to manually transform node to category)

However, I think there is still an shortage of category module. If I (will) have >1000 nodes, then I will have >1000 categories. So, on the node submit page, when I need to select parent category for the new node, I would faint since there are >1000 categories in the drip-down selection box........

Am I any mistake?

Category is really a great great module, however, since this inconvenience (not bug), I have to give up it.

I am wondering, why for the drupal embeded book type, every node is not category? Thanks.

inforeto’s picture

inforeto commented

Well, if you are using category to make book pages, yes, the classification needs to be planned carefully.
Otherwise all the subpages would be listed.

I gather the category implementation of active select can be used for this, so try a nested approach.
Have some main classification containers that loads smaller parts of the node list in the drop down boxes.
It worked for me to sort a directory of city, district/neighborhood and streets, because there's a huge number of addresses on them.

For taxonomy usage, it only lists the categories grouped by containers.
You assign these containers to the content types so there's less chance of clutter.

JirkaRybka’s picture

JirkaRybka commented
Status: Active » Fixed

After 2.5 years of silence, sufficient (IMO) answers above, and 5.x version being no more supported, I assume this Support request may be considered as "fixed".

Status: Fixed » Closed (fixed)

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