Installation
Below are the instructions for installing the latest version of the categoryi module (CVS HEAD), with the latest version of Drupal (also CVS HEAD):
- Copy the category folder and its contents to the Drupal
modules/directory. Drupal should automatically detect it. - Go to 'administer -> modules' and enable category (and category_menu, category_display, category_export, and category_legacy, if applicable).
Note: for each module that you enable, all necessary database tables will be automatically created, using Drupal's new.installfile system. You no longer need to run thecategory.mysqlscript (which is why this file no longer exists). - If you wish to use taxonomy-dependent Drupal modules (e.g. forum, image, glossary) with this module, you must install the taxonomy wrapperi module. There is now a script available to perform this installation for you. To run the script, go to 'administer -> settings -> category', and in the 'wrapper install / uninstall settings' box, click the 'install now' link for the taxonomy wrapper. If you experience errors with this script (usually due to file system permissions problems), see the instructions for installing the wrapper modules manually.
- If you wish to use book-dependent Drupal modules (e.g. export_dxml) with this module, you must install the book wrapper module. The procedure for doing this is similar to that for installing the taxonomy wrapper module. To run the book wrapper installation script, go to 'administer -> settings -> category', and in the 'wrapper install / uninstall settings' box, click the 'install now' link for the book wrapper. If you experience errors with this script (usually due to file system permissions problems), see the instructions for installing the wrapper modules manually.
- If you have existing taxonomy terms and vocabularies, or if you have existing book nodes, you can import them as categories and containeris using category_legacy. To do this, go to 'administer -> category legacy', and follow the instructions on that page. It is recommended that you enable the taxonomy and book wrappers before performing an import. Additionally, using the taxonomy wrapper with existing taxonomy data is not recommended - either import your existing taxonomy data first, disable the taxonomy wrapper, or delete your site's taxonomy data. You are able to leave the book module enabled, and continue to use your book data, if you wish (but as with taxonomy, it is recommended that you disable book).
- Go to 'administer -> access control' to configure access privileges for this module.
- Go to 'administer -> settings -> category' to change the settings for all modules in the category package. You might also want to change the node type settings for the category and container node types, at 'administer -> settings -> content types'.
- Go to 'administer -> categories' to start managing your categories and containers. You can create new categories and containers from here, or you can go to 'create content -> category' or 'create content -> container'.
- You can assign content to categories by configuring your containers to be associated with various node types, and then creating or editing nodes of those types.
Note: content with assigned categories will only have its categories displayed if category_display is installed, and if your containers are configured to show categories on assigned nodeis, and if the taxonomy wrapper is installed.
Fixed
Install instructions (on this page and in the categoryi package) have been updated to indicate that only the category.mysql script now needs to be run. In the future, please submit problems like this as bug reports using the drupal.org issue tracker: http://drupal.org/node/add/project_issue/category.
Jeremy Epstein - GreenAsh
no need for mysql
I downloaded today's version 3-27-06. there's no categoryi.mysql file. we don't need it any more right? we use category.install right? I checked and the tables were created. If this is right please change the install instructions. Thank you.
Simple question?
Newcomer here, so maybe it's a too simple question.
Since Categories is designed to supercede and replace book & taxonomy modules, is it ok to disable the taxonomy and book modules after installation of categories and legacy import?
No
It is recommended that you replace the core taxonomy and book modules with the wrapperi modules (the wrapper install scripts will do this for you), and that you leave the wrapper modules enabled permanently on your site. The wrapper modules allow taxonomy- and book-dependent modules to function, by mimicking the old API, and by maintaining the old database tables.
If you disable the wrapper modules after installation, then you will not be able to use a number of popular modules that depend on taxonomy (and book, to a lesser extent), such as forum, image, and glossary.
Wrappers, Taxonomy & Book Modules
Hi Jaza,
It still is not crystal clear for me. I went to 'administer -> settings -> categoryi' where I was instructed to enable the Taxonomy and Book Modules in order to install the wrapperis. I endabled the modules, clicked the link to install the wrappers, and now the category settings page reports the wrappers are installed. Do I leave the book and taxonomy modules enabled, or do I disable these two modules?
Thanks.
Paul
Enable
Leave them enabled.
What you need to understand is this: the wrapperi modules are replacement files for the taxonomy and book module files. When you install them, the old 'taxonomy.module' and 'book.module' files are replaced with the wrapper module files. So as far as Drupal is concerned, the wrappers are the "real" taxonomy and book modules. If you disable taxonomy and book (when you have the wrappers installed), you are disabling the wrappers.
When you have the wrappers installed, go to the 'administer -> modules' page, and look for taxonomy and book in the module list. You will see that they have a different description to the "real" taxonomy and book modules, but that they are listed on this page as the taxonomy and book modules. This is a visual re-inforcement of the whole 'wrapper' concept, which I hope you now understand better.
Thanks
for this explanation. It is good to undertand exactly how the term wrapperi is being used in the drupal community and what it means with reference to drupal modules.
As a relative Drupal newbie, I decided to install Drupal 7.3 and use categoryi rather than attempt to learn taxonomy only to turn around and then convert to/learn category.
So the system I'm installing has nothing loaded in the old book and taxonomy modules. I can install the wrappers but is there any advantage to doing so? Other than of course being able to use "old modules" like image, forum and glossary.
Which one is image dependent on? Book or taxonomy?. I'd rather leave taxonomy off in my fresh install if at all possible. Or is that not practical? Are there too many other modules that presume it is present that may not have been "converted" to look for category?
Installation failure on Slackware 10.2
Are there any specific requirements (as in versions of Apache, PHP or MySQL) for the Category Module? It seems unwilling to run in the Slackware 10.2 environment (1.3.33/1.3.35, 4.4.0/4.4.2, 4.1.14/5.0.21) that Drupal 4.7.0 runs perfectly in.
When I enable the "categoryi" module in /admin/modules, I get a blank screen in response to the click on 'Save configuration'. Enabling the other eight modules as well eventually results in errors like
user warning: Table 'drupal.category_legacy_map' doesn't exist
query: SELECT * FROM category_legacy_map WHERE id_type =
'category' AND redirect_type = 'taxonomy' in
/var/www/drupal-4.7.0/includes/database.mysql.inc on line 120.
Apparenty none of the category-specific tables have been created. I am about to go through the .install files to see if things can be patched up manually, but that is obviously not the preferred approach. Any thoughts on what might be going wrong?
Some details...
Hi,
You wrote for Step 7 :
Go to 'administer -> settings -> categoryi' to change the settings for all modules in the category package.
By default, do we need to change something ?
Reading this, we do not know if we can ou should/must/have to change something... ;-)
legacy import times out
I have a large legacy vocabulary I'm trying to import. However, when I run the legacy settings import script, it times out, and only converts a small portion of the vocabulary. I tried separating out the items into a cron, but only managed to mangle things even more.
Also, when I view a built categoryi page, it times out during the menu build as well. Anyone know how to work around this?
Administration > Categories menu item disappeared
I've just installed the Category Module and the wrapperis for both the Book and Taxonomy modules.
When I go to fiddle with the categories in Administration > Categories I can no longer see the the Categories menu item. (I'm running 4.7.5) Which means I can no longer edit or add categories.
If I uninstall the Taxonomy wrapper module I can edit categories but not if it's installed.
Has anyone had this issue or can anyone explain what I can do other than uninstall the Categories Module?
MISSING category_menu.mysql & category_display.mysql
I tried to run
mysql -u username -ppassword drupal categoryi_menu/category_menu.mysql
and
mysql -u username -ppassword drupal category_display/category_display.mysql
but category_menu/category_menu.mysql & category_display/category_display.mysql do not exist! I navigated to the directory and sure enough there aren't any files there. All I see are category_menu.module and category_display.module and category_display.css.
What do I do now?