Dizkus

I think the top request for quite a bit of time has been some docs on the categories module. I have fumbled around the module with not much luck in getting anything useful yet myself. I have searched around and not found even the most rudimentary how to or insight by anyone who has configured it. I am beginning to wonder if this is something deliberate, or just my frustration talking after 3 yrs of on and off testing of the candidates.

Can we maybe use this thread for some basics and tips from those of you with long term exposure to the module? I am not talking on info for developing a new module. I am thinking of just how to go about basic tasks with current value added module collection; faq, downloads, reviews, links, news, quotes. etc.

The pnDocs site has a space for info on categories, but it is empty, unlike other areas. I would be willing to offer better feedback for what seems to be a centerpiece or major feature in the new system, something better than "fumbling around." I for one would be grateful for this kind of info and support!

I fear that they don't know how it works themselves ...

Please.

--
;)

What kind of tips are you looking for? The question is a bit open ended....

-Mark

Hi Mark, thanks for responding,
to just get to it...
-Basics of creating a site wide category for modules
-Basics of creating a specialized category for one module -
(though the basics of a site wide might cover this)
-creating a sub category
(does the need to touch the database still hold /per an earlier thread?)

Really just some basics, I have been in and out of touch with .8 over the past few months with no real time to learn this stuff, but with things around here moving on, I would like to keep up.

Outside of basics any other tips would be based on what you have been able to make/configure with it so I guess that would still be open ended to all who would want to add anything. (like things you find out later because you started a particular way - something that only experience using "Categories" would tell you...)

Thanks again.

--
;)

There is no such thing as a single global setting. However you can take a category tree and use the category registry to set all modules to use this particular category tree. This then means that all modules will use the specified category tree, thus creating the effect you want.


Just create the categories you want in the category manager and use the category registry to assign this category tree to the module which should use this category tree.


Create a new category (in the category admin view) and assign the proper parent to it. It will then be created as a sub-category of the parent you supplied.


No, that bug has been fixed in the current SVN code.

Hope this helps ...

Greetings
R

I'll cover some background first. The categories module is more than just a solution providing categorisation of content items - although one of it's functions is to do just this.

The categories module at its most basic level provides a heirachical tree of 'categories'. These categories don't have to be related in any way and can be used for many purposes.

In a default install of the categories module thare are three main sections to the category tree. The first labelled 'General' provides a set of general purpose 'categories' to simpify management of list-type controls within modules.

For example let's say that i'm working on a web-based helpdesk system. In the category tree I have the category paths "/General/Pending Status Extended" and "/General/Pending Status Basic". Rather than build various static drop-downs in my template I can build a drop-down using this part of the category tree. If I then want to add another status I add it to the category tree and all my controls now contain this new item.

In theory the categories module could provide content to just about every drop-down list box, radio control within a site.

This covers the general purpose categories. I'll post the content categorisation next.

-Mark

Onto the content categorisation side of things. By default the categories module ships with a sample category tree (in /Modules/Global). There are two general scenarios in which content could be categories (and several that fall between the two).

Scenario 1) A single category tree used across all content modules e.g. let's say I run a games site. I could create a category tree that looks like the following and then assign reviews, downloads and other content items to a category covering the platform that it's relevant too.
Xbox - Original
- 360
Playstation - PSOne
- PS2
- PS3
PC
etc.

Scenario 2) A category tree is established on a module by module basis (as with .7x - due to seperate category systems). e.g. I run a technology blog site that, in addition to the blog, provides some downloads and web links relating to the blog. I can setup a category tree as follows
News - Products
- Shows
Downloads - Utilities
- Drivers
Web Links - Manufacturers
- User Communitities
etc.

more in the next post....

-Mark

The categories registry is how a module ties into the categories tree. The entries in the categories registry tell module X which categories to use. So scenario 1 is setup by telling each module to look at the same part of the categories tree where as scenario 2 is setup by telling each module to look at a distinct part of tree

By default, when installing any of the value addons, they setup the requirements for both scenarios e.g. when the news module installs it creates the category path /Modules/News (for use with scenario 2) but creates an entry in the categories registry to point to /Modules/Global. Thus when you look at a default install the news module uses the default global categories (Sport, Science etc.).

-Mark

Lastly category attributes...

A category can have multiple attributes that add additional data to the category. This data may be used by a module for any purpose. A site owner can add additional attributes for thier own use if desired.

An example of a category attribute in action is available within the news module. Should a category assigned to the news module have the attribute topic_image this attribute value will be used as the image source for a graphic for this category. This mirrors the topic image within the old .7x topics module.

Hopefully this covers many of the initial questions relating to the categories module....

-Mark

These are all Great! Thanks. I been busy, but the theory behind the practical has been helping. Thanks Robert & Mark.

As a side note, I have come back to an observation that I have had about PostNuke for a few years. Sometimes I wish the "News" module was called "Article" or "Posting." In .8 can you just rename the folder to rename the module? I like that "Sections" was renamed to "Pages."

I am enjoying working with this, Thanks Again, and don't stop, It's all good. :)

--
;)

You can simply rename the display name of a module in .8
Just go to Administration > Modules and edit a particular module to assign another name.

--

You can change the display name in .76x too.

-Mark

Well Yea, there is that too. ty

--
;)

OK,

What are acceptable values for "Property Name" in the Category Registry?
Can Modules be listed more than once in the Category Registry? (can a module have multiple trees available to it?)

If you use User editable categories, with a default root category, do you have to set the root of that category tree ("Users) as the default for all content modules in the Category Registry?

How are user Editable categories available along side Site wide categories? Are They?

Edit:
I think I see some of the answers to these questions, but for clarification, they are asked as is.



edited by: TakeIT2, Feb 09, 2008 - 12:23 PM

--
;)