[master] Category 6.x

Started on it already, actually.

HEAD will be recieving the first part of the 6.x port sometime soon.

I'm going to go ahead and [master] this.

I'm excited about 6.x. It has a lot of new functionality that will allow making Category a lot simpler, cleaner, and more efficient.

subscribing

Thanks for the confirmation and the work bdragon! This is a terrific module, looking forward to v6.

Subscribing.

First batch of changes committed. It's nowhere near working, but I got the database schema history converted over to the new system.

Committed another gob of changes.

I'm liking the Drupal 6 API changes.

How is the progress with this ?

I'm going to start work on this. Bdragon, please let me know if you're still active as well - if not, then I'll re-assign the issue to myself.

Please do, I got NOWHERE with this.. :(

I've tackled most of the database changes, and I'm now getting stuck into updating the wrappers. This is a biiig job! Will post a patch when I've made more progress.

Thank you for the update and work.

subscribing

subscribing as well :)

subscribing

tried out the HEAD for Drupal 6 on a fresh install, getting this error:
user warning: Table 'db_dir.category_cont' doesn't exist

is there a seperate SQL file that could be used?

If I am testing this out too early, just let me know. I know you are still working on it, and wanted to thank you.

also while enabling it I get this error on the modules page:
warning: Invalid argument supplied for foreach() in dir/includes/common.inc on line 3164.
warning: Invalid argument supplied for foreach() in dir/includes/common.inc on line 3085.

Do you know if category 6 will solve any issues when this module becomes big e.g. we use category on the revisionworld website and have some 8000 pages but the site grinds to a halt (memory timeout) when we try to add anything and looking through previous threads it looks like the bigger the site gets the more problems it will have.

Any suggestions?

OK - after many long hours of coding, here's the first preview of the category module working with Drupal 6. Yay!!!

Listing all the changes in this code will be quite a challenge, as it's a fairly thorough rewrite of the module, possibly taking more inspiration from D6 core than from D5 category. Some of the new features that you can see already in Category D6:

1. Admin pages improved to reflect the changes in the book and taxonomy UIs for D6. E.g: drag-and-drop is enabled on the container and category overview pages, and paging is improved on the category overview pages. As with D6 taxonomy, drag-and-drop is disabled for multi-parent containers.
2. The AJAX select widget in the D6 book module has been ported over to category, for the 'container' and 'parent' select boxes on add/edit category/container node forms. This will be used instead of activeselect.
3. The category/container node form is now more finely-grained in its fieldset grouping of elements, to improve usability.
4. As in D6 taxonomy, the 'hierarchy' option for containers is now maintained by the system, rather than being a user-defined setting.
5. Distant parents has been made less ambitious, and also less buggy. You can now only define one other container as an 'allowed distant parent' for each container. Categories can only have distant categories as their parents, not distant containers.
6. No more 'description' field for categories or containers - node teaser is used for this purpose instead (only use of it is in RSS feed descriptions, anyway).
7. Various other usability improvements in D6 core reflected in D6 category - e.g. 'synonyms' and 'related categories' moved into 'advanced options' fieldset.
8. Category-to-node associations are now revisioned, as in D6 taxonomy. Note that other category and container information is still not revisioned.

This first version is working pretty well, but it still has some bugs to be ironed out, and so far it's only the absolute core category system. Many things are still left to do, some of which are:

1. Provide an upgrade path from D5
2. Make category selection for distant-parent containers AJAXified
3. Upgrade the book and taxonomy wrappers (work in progress - but not included here)
4. Upgrade the category-related modules. I'll be tackling the main ones when I get a chance (i.e. category_menu (big performance and stability improvements in the pipeline), category_display, category_export, category_legacy).
5. Upgrade the other modules, in the 'contrib' sub-directory. I don't see myself getting around to these, so if anyone desperately wants them upgraded, please volunteer to do it yourself.

Testing, reviews and feedback are most welcome. With some community help, I'm hoping that CVS commits and alpha releases will be happening soon.

Sounds great, thanks for getting this started Jeremy.

I'd love to jump and convert some of these but timing wise we are committed to going forward on our project still using Drupal 5 and therefore i am still mostly working on fixing up category for Dr5. I am sure it won't be longr after we release our site that we'll be looking to migrate to 6.

That all being said - i like your upgrade priority list above especially #1 as this would be my biggest concern at this point. Although #5 scares me a little since for every site i have done using category the most important module to me is category_transform - which i think falls into the contrib category.

I guess if some of these and other non-cat modules come along; i'll likely jump in and do cat_transform.

Peter Lindstrom
LiquidCMS - Content Management Solution Experts

Just downloaded your D6 alpha and plugged it in after reading your documentation.

Boy am I glad I have been spending hours pouring over all the drupal modules and finally finding this to get this functionnality. From what I see, this is a well known module but I am new to Drupal so there :)

I had been playing with CCK nodereference to try to simulate this. For the sake of future readers also looking for this functionnality I am listing some keywords I can think of so that search engine will reference them to this page : addnode, add_n_reference, nodeassist, cck, nodereference, autocomplete, node family, node relativity

I will be doing more testing over the weekend on this D6 version and provide some feedback then

Hey, how does one "apply" the patch provided above? I just see files (not .patch files)... Do I just put them in the category directory and override the ones currently in there? (I tried that but I am getting errors about missing functions, etc).

Any help would be great.

@cyclops2.0: Nope, forget about the old category directory with its files. That won't work. Just delete the old directory's content and replace it by the new ones that are rolled into the zip file.

Thank you a lot Jaza that you have picked up the development again... please don´t leave us ever alone again....

no catpathauto, cattransform, catbreads and catviews is a real sucker so - maybe we can make it a group efford to recode them...

D6 Alpha1 of the category module is now released: download it from the module's main page, or from CVS. Yay!

Update to my previous todo list:

1. Provide an upgrade path from D5 — TODO
2. Make category selection for distant-parent containers AJAXified — DONE. The new distant-parent selection is based on the AJAX select in the D6 book module, and it no longer depends on active select. It's pretty cool - give it a try.
3. Upgrade the book and taxonomy wrappers — IN PROGRESS. Taxonomy wrapper is pretty much done now (working more reliably than ever), but book wrapper is not yet started, and is going to be much tricker (due to the new book/menu entanglement in D6).
4. Upgrade the category-related modules — TODO
5. Upgrade the other modules, in the 'contrib' sub-directory — TODO

Finishing off the rest of these items (except for the last one, which has a longer timeframe) will lead us into the beta stage of Category D6. Testing and feedback of Alpha1 is welcome.

PS: I also wrote a new little module, called 'category_resave', which calls node_save() for every container / category / tagged node on your site (or it can be run per-container). I just whipped it up in order to make debugging the taxonomy wrapper a bit easier. With one click, it will re-generate all the wrapper data on your site - should also work for re-generating menu items, when I get round to category_menu. Very handy!

You can find category_resave in the alpha1 release of the module (under 'contrib').

good work jaza!

subscribing...

Hi! This module is great, thank you Jaza and bdragon for your work. I'd like to help with porting to D6 as I need D6 version for my site.
Starting with category_display seems logical to me because it is marked TODO on your list and I need it.
Is it ok for me to start working on this or have you already started it youself? Is there anything I should know before starting?

Etzel: I am currently working on the book wrapper, and on category_menu and category_display (these three are very closely linked). So if you could wait until I have those modules finished, it would be super. These three are also quite tricky, as there have been significant changes to the D6 version of the book module - I'd rather tackle the emulation of these changes myself.

Ok, I'll wait. Thanks for the reply.

I wonder if the book wrapper is really needed. Haven't seen many modules dependent on the book.module.

The category uses book for navigation and several things not found in taxonomy.
Indeed, the modules depending on book would integrate to category.

Alpha3 of the Category module for D6 has been released. What's new in this release:

• Category_menu for D6 is here! Category_menu now has:
  • An improved UI on container node forms, with much AJAXy and jQuery goodness thrown in
  • New restriction: you cannot apply category_menu functionality to containers with multiple parents enabled. This makes the menu maintenance code much simpler and much more reliable.
  • Menu settings for assigned nodes are now saved against content types, rather than against containers (although they're still configured through the container editing UI, to keep everything in one spot). I.e. previously, you used to say "I want all nodes tagged with a category from container x to get a menu link", whereas now you say "I want all nodes of this content type to get a menu link (when I tag them with a category from container x)". Once again, makes things simpler and more reliable under the hood.
  • Each container now has its own menu, and the menu links for each category are stored under the container's menu. Previously, all the category_menu-generated links on the entire site were kept under one menu.
  • For top-level containers, you can now specify ANY menu link on the site as that container's "menu parent".
  • And, of course, it's all built on top of the new D6 menu system - which means that it will (at least, it _should_), for the first time, actually scale to thousands of menu items without breaking your site.
• Book wrapper is here! The book wrapper doesn't depend on category_menu "as such", but it basically won't do anything unless you have category_menu installed and generating menu items. This is because the D6 book system uses the menu system to store hierarchy information. The main features of the D6 book module are (a) maintaining the book table, and (b) providing standard book-module navigation blocks.
• New "menu wrapper", which is exactly the same as the core menu module, but minus menu_form_alter() and menu_formapi(). This is because the 'menu-on-the-fly' feature in these functions conflicts with category_menu.
• Plus, of course, plenty of bug fixes. Keep testing, and keep reporting those bugs - all your help is much appreciated!

Notes:
- category_menu doesn't yet set breadcrumbs, it will do this soon.
- there is currently no wrapper install / uninstall script, but you can enable / disable them yourself by renaming the .module and .info files to .module.renameme and .info.renameme, or something like that.

Alpha 4 is now available. What's new:

• Category_display is here! Features:
  • New JavaScript goodness in the UI, to hide elements when they're not needed.
  • This module now depends on category_menu, and it uses the menu hierarchy to help with rendering most of the elements that it displays.
  • Got rid of the 'link to prev / next distant containers' settings, as I don't particularly find them useful, and as they would have been a lot of work to port. If anyone desperately wants them back, feel free to submit a patch.
• There is now an upgrade path from Drupal 5, for category, category_menu, and category_display. I've tested it on a D5 -> D6 site, and it seems to work pretty well. More testing probably needed.
• Wrapper install / uninstall functionality has been ported to D6. Wrappers are still installed by default, but can now be toggled on/off as in D5.
• Numerous bug fixes. More testing from interested coders is welcome.

Which other modules does this Alpha 4 not work good with ? What I know there was problems with a few, I think Views was one of them ?

I'm reading the docs in the category web site.
In the docs section, there is a tutorial about using views with category.
I can't find in the "containers edit" the "category view settings box" to select the custom view that I created.
My doubt is: does this button exist in the Drupal Category 6.x-2.0-alpha4? This function would be very useful.
Is There another way to do this or the view settings box will be added into the next upgrade?

Let me preface this by saying that I am a newb to drupal (using ver. 6.3). I apologize in advance if these questions seem trivial, but even after reading the tutorial (which no longer seems to match the current version of the module) I'm really lost.

What I'm trying to do is create a hierarchy of classification and have that show up in the navigation menu:

Reviews
- Books
- -Fiction
- -NonFiction
Artilces
News
- Local
- National

I've tried making "Reviews", "Articles" and "News" containers. What do I have to do to make these three Containers show up in the navigation menu? I've tried so many different settings w/in the menu links section that I can't even begin to relate them all!

Thanks for your help!

subscribing

Hey I need help. I have installed this module on my latest drupal page, now my entire website is not working. I am getting following errors. Can anyone help me out or got similar errors and got through?

Fatal error: Call to undefined function category_link() in C:\xampp\htdocs\mysite\sites\all\Modules\category\wrappers\taxonomy\taxonomy.module on line 44

Thanks in advance!
nyctech

This module is nowhere near ready for use. I installed it on my test site, could not get either containers or categories to show in the menu and then attempted to uninstall it. I had to disable half the other modules on the site to complete the uninstall, and "container" and "category" were still listed under taxonomy. Additionally, none of my books have the admin fields for book outlines.

It might have been a good module for Drupal5, but it's definitely s**t on Drupal6.

I have had the same problem. The 'custom menu' setting for a top-level container is ignored.

Although the container edit page apparently saves OK, no menu setting is applied and the entries have gone on re-opening the edit page. Attempting to preview the page produces the following errors:

* warning: array_intersect() [function.array-intersect]: Argument #2 is not an array in /home/xxxxxxxx/public_html/modules/category/category_menu/category_menu.module on line 187.
* warning: array_flip() [function.array-flip]: The argument should be an array in /home/xxxxxxxx/public_html/modules/category/category_menu/category_menu.module on line 188.
* warning: array_map() [function.array-map]: Argument #2 should be an array in /home/xxxxxxxx/public_html/modules/category/category_menu/category_menu.module on line 188.

Afraid I don't know enough about this to suggest a solution!

confirmed .. category menu basically does nothing