Hello, I am a recent Drupal convert and have a nice site up and ready to load content

Background to trying your module: I have a 3 tier menu tied to my categories (using various menu modules). When I add a story only the first branch of my taxonomy_super_select appears in the desired format - the others appear as the default list). I have not used CCK and don't know what it is!

So I found and downloaded your product. It says it merges CCK and category menu function - right?

But I see I need module 'content' AND there's an install file (cck_taxonomy_ssu.install) - I have never had to run an install on any module yet - how is this done.

Do I load 'content' first and will that damage my category module usage?

Thanks very much - sounds like you've done something needed.

Regards
Zaph www.morethanoil.com

Comments

ZaphMann’s picture

ZaphMann commented
Title: Need more info on dependenciy and CCK » Need your help
Component: Documentation » Code
Status: Postponed (maintainer needs more info) » Active

OK, I worked out that 'content' is part of CCK and installed that module and enabled content, Content Taxonomy, and your module, but nothing happens when I go to add content I just get the default ugly long lists of my vocabularies.

Are there other steps?? Do all the other CCK modules need to be enabled??

Please help.
Thanks
Zaph

rconstantine’s picture

rconstantine commented

Hmm. Two things come to mind. First, I'm not sure whether this module can coexist with Content Taxonomy or not. Second, be sure to read the CCK docs because you will need to enable some of the CCK sub-modules for CCK to be of any use at all. The content module is just an API for sub-modules to use.

Within the CCK module group, I have enabled all of the sub-modules that came with CCK, but you should be able to choose which ones you want. I don't think my module relies on any of the sub-modules, but perhaps I've forgotten something.

So far as modules that need activating, you just need Content, from the CCK group and Taxonomy from the Core-optional group. Once those are activated, you can activate CCK Taxonomy Super Select Ultra also in the CCK group.

You also need to create a vocabulary for use with this module. Then, you need to add the CCK Taxonomy Super Select Ultra field to either a custom or existing content type. How to do this is documented in the CCK docs.

If you do all of this and still have trouble, let me know. Support is not a substitute for the documentation of all relevant modules. This module doesn't really do anything special outside of regular CCK stuff, so I didn't think it needed a README. If a lot of other people have this problem, though, I'll reconsider that idea.

ZaphMann’s picture

ZaphMann commented

Thanks for that help - I'll print and be sure to carefully follow the steps outlined, then let you know.
Regards
Zaph

ZaphMann’s picture

ZaphMann commented
Title: Need your help » ALMOST!!

I resolved the issue as to why it wasn't working and found that there were several steps that, though probably second nature to you, were uncharted for me (I document them below so you can add to a readme or something). BUT it doesn't quite work as needed - I wonder if this minor problem (which is a major limitation oin my site's design) is easily resolvable...

The problem: I have seven major vocabularies organised under one menu - that 'master' menu is also a vocabulary, but it doesn't contain any terms. The other vocabs are linked to it by it being the Parent (menu) Item for each of the 7 vocabs. This works seamlessly for my menus and in the default content drupal categories if I select my MASTER for taxonomies, under story say, it shows the 7 just fine (but as ugly lists) which is why I wanted your module.

But with your module, when I go to Content management » Content types > Story and add a field in which I select my MASTER in your mod, none of the 7 menus and their terms show up.

If I select one of the 7 vocabs it works just great (except it only allows me to check the two sub layers - but I could live with that). BUT I can ONLY select ONE of the 7 and I need all of them to be options...

I don't want to create 7 story types and 7 blog types etc.. it would be ugly and disfunctional as many stories need to be tagged across terms in different Vocabs...

>> I guess I could make the Master vocab contain all the 7 vocabs (and all their terms) as terms - that could be several days' work (unless there's an easy way) and would it bring other issues I wonder? - like depth of terms, would your checkboxes sink a level too low?

>> Or maybe there's a way to check more than ONE radial box in your fields? (It doesn't let me at the moment)

I also tried creating a field under taxonomy with activeselect (same problem - also inferior, as it only allows 1 selection) and Checkboxes/Radios (same problem - also inferior as it allows multiple selects but doesn't collapse/expand menus or show headings)

---- now to the steps a newbie wouldn't know:

After loading up CCK Taxonomy Super Select Ultra to the modules folder & befoe it will work:

1. You need to install CCK module suite and activate the sub-module 'content' AND at least one field type module (- text.module
- number.module
- userreference.module
- nodereference.module) you may as well activate them all.
Once those are activated, you can activate CCK Taxonomy Super Select Ultra also in the CCK group.

For this module Content Taxonomy is irrelevant as are the other sub modules you see.

The CCK Taxonomy Super Select Ultra module works from vocabularies - so you must have one built already.

Then, you need to add the CCK Taxonomy Super Select Ultra field to either a custom or existing content type (like Story or page). How to do this is documented in the CCK docs (but where?) so here's how:

Go to Administer » Content management » Content types
Under Operations (Right hand side) edit a content type
add a field, title it and scroll down to CCK Taxonomy Super Select Ultra select radials,
select a vocabulary, save and it will take you to field settings,
save and it will take you to 'manage fields'
give it a weight and 'update'
THEN go to add content and select the content type you added the CCK Taxonomy Super Select Ultra to (say story) and hey presto!

rconstantine’s picture

rconstantine commented

I usually create README files and I've actually surprised myself by not doing one this time. I'll work on one when I get a chance since you are right in thinking that these steps should be documented here.

Anyway, to try and answer some of your questions:

- This module understands any depth of vocabularies, so make them as deep as you like. I doubt that multiple parents works, though.

- What you have done in tying several vocabularies to one overall vocab is irregular and I'm not sure how much trouble it would be to get it to work. What I could use from you is a zip file of screen shots with the various problems you are having. File attachments on drupal.org don't allow .zip files, so add a bogus extension at the end, or gzip it if you can.

- There are currently no provisions in the code to deal with multiple vocabs at once, so simply changing the radio select of vocabs to checkboxes wouldn't do you any good.

- Could you explain what you mean by

except it only allows me to check the two sub layers

? If you mean what I think, then you should find a checkbox that says something like allow parents to be selected or something like that in the admin of the content type field. This will allow both leaf and branch terms to be selected, not just leaf terms.

- Could you describe what your vocabulary is used for?

- You could probably transfer all existing vocab terms to your main vocab with just a couple of SQL queries. If you decide that's what you'd like to do, I might be able to help.

ZaphMann’s picture

ZaphMann commented
Title: ALMOST!! » Making it work with 'false' vocabulary menu parent

Ryan,
Thanks for the quick response, much appreciated. From what you say, your sql query could be the answer, but I'll first go through your response, point for point, along the way I'll try to describe the 'irregular' design (the result of which is very user & admin friendly). You can see the design element at the site www.morethanoil.com (the 'TOP vocab' is Energy Topics), but you can't see the CCK issue unless you are adding content (story) which requires a user reg. (Oh and you mentioned screenshots - before we get to that (I don't know how to do it), let's see if I can be clear enough.

- This module understands any depth of vocabularies, so make them as deep as you like. I doubt that multiple parents works, though.

1a. That's good, the depth of each of my 7 vocabs is 3 levels (TOP-Sub1-Sub2), but as I say they are functionally under another vocab so it would then be 4 levels.
1b. There aren't multiple parents, I used a module to generate identical menu entries for all my taxonomy, then in Administer » Site building » Menus the 7 Menus are assigned to the MasterMenu as Parent Item. So one parent of seven.

- What you have done in tying several vocabularies to one overall vocab is irregular
Perhaps I should have just built it under one vocab, but at outset I was worried about two factors:
- I had seen in my initial reading, mention of some limit of 3 levels only for some modules (but I can't locate this anymore - maybe I dreant it!)
- More importantly, the taxonomy needs to 'direct' the content buildiing of the site, so contributors will need to select from these vocabulary trees, but the default Drupal taxonomy is just a long list - holding down the ctrl key and scrolling down to select from > a hundred non-indented terms of different levels was not going to work. So I broke them up logically to ease it a bit. Then hit upon modules like yours...

- There are currently no provisions in the code to deal with multiple vocabs at once, so simply changing the radio select of vocabs to checkboxes wouldn't do you any good.
Yes, I see that would be the case.

find a checkbox that says something like allow parents to be selected or something like that in the admin of the content type field. This will allow both leaf and branch terms to be selected, not just leaf terms.
This is precisely as it is, and has noting to do with the MasterVocab issue above, as in this instance I only selected one vocab: VocabA (3 level VocabA - Sub1 - Subsub1, Sub2 - Subsub2 etc)
First instance it gave me a 3 tier menu with checkboxes only beside the Subsub terms.
Then I checked Display parent terms as selectable form items , which worked in that it
now added checkboxes for the Sub level, but NOT the VocabA itsself.

- Could you describe what your vocabulary is used for?
As per above, consistency between, menus, taxonomy and content tagging.

- You could probably transfer all existing vocab terms to your main vocab with just a couple of SQL queries. If you decide that's what you'd like to do, I might be able to help.
Thanks. I don't know that language, or how to make it happen at my host. I do have a very good relationship with them though. I also have Phpadmin access.

I have one new idea, perhaps I could create seven fields in a CCK group, each one your module pointing at each of the seven vocabs... is this sane?

Thanks again, this is a great supportive world of open source - I go to my first meeting tommorow for the local druplers...!
Zaph

rconstantine’s picture

rconstantine commented

which worked in that it now added checkboxes for the Sub level, but NOT the VocabA itsself.

So you need the vocab as a tag as well? What about the parent of the seven vocabs? If not, then turning the seven vocabs into one large vocab should give you what you want.

I also have Phpadmin access.

Right, that's what you'd use. I can help you figure out the queries to run. Meanwhile, take a look at the tables that begin with term* as well as the one called vocabulary. You should be able to see how the tables relate. Essentially, what needs to happen is to change the heads of the seven vocabs into terms of the main vocab and remove the vocab-head status of the seven. The seven may already be terms of the main, so all that would need to be done if that is the case is to remove their own vocab status.

With so few terms, you might not need queries, just some point and click tinkering. I'll refresh my memory on the tables...

Um, okay, here you go. I'm making some assumptions as to how you've created your vocabs...

Backup your database before doing the following. Google phpmyadmin on how to do that.

First, go to the 'vocabulary' table. Delete (via the red 'X') the vocab for each of the seven vocabs you have, but write down any names or whatever if you think you'll need them.

Second, go to the 'term_data' table. Here you will find all of the terms, their term id (tid) and their vocab id (vid). Make sure you can see all rows (if not, enter a large number just after the 'show' button, and enter 0 for the 'starting from record#' box). Print this out for reference.

Next, go to the 'term_hierarchy' table. This is just a list of tid & vid pairs. Your task here (by clicking on the pencil in each row) is to make sure that the parents are okay starting at your BOTTOM-MOST term, all the way up to the main vocab. I assume that each of the seven vocabs is fine internally, so you just want to make sure that the head of each vocab is in fact a term and that it points to the main vocab.

Once that is all okay, you go back to the 'term_data' table and change all VIDs in the seven vocabs to match the main vocab.

So for example, your main vocab is VID=2, and your seven vocabs are 3, 4, 5, 6, 7, 8, 9, then you'll change all 3s, 4s, 5s, 6s, 7s, 8s & 9s in the VID column to 2. That will place all terms, formerly in several vocabs, into one. [Oh, I just had a thought--if you do the 'first' step, and then skip to this one, you may be able to manage (make sure all terms are where they should be) via the drupal interface for categories where you created the vocabs in the first place. The reason being, all terms will now be under one vocabulary and should all show up there when you go to edit it. Does that make sense? This stuff is hard to put in words.

In summary, where you now have a slight disconnect between your main vocab and the seven with their terms, you want to bring the terms of the seven under the main vocab and make sure that if you were using the vocab names of the seven AS TERMS, that real terms exist to take their place when the changes have been made.

One caveat to consider is in how your menu works. Is that a module that REQUIRES separate vocabs for each branch? If so, you really can't change how you've got your vocabs set up. That's why I have been so cautious myself not only in how I create modules, but how I select modules that are already out there. They need to work together and share common data. If one module needs data in a different way than another, then I either need to modify one, or make something else.

As for

I have one new idea, perhaps I could create seven fields in a CCK group, each one your module pointing at each of the seven vocabs... is this sane?

You could do that, but you might get people a little confused. However, you could provide a little help message to them when you create the content type so that they know what to do with them.

ZaphMann’s picture

ZaphMann commented
Status: Active » Fixed

Ryan, It is now resolved, this is just to let you (& others) know how:

All terms are now under one vocabulary, whereas before they were under seven vocabs with an eighth 'master' vocab.

The Problem: The key design element was that in using the taxonomy menu module I generated menus to match my taxonomy automatically. The problem came in that, with 7 seven vocabs and menus I needed a topmost menu, so I created a master vocab (which auto generated another menu) then made that the parent of the other 7 menus.

What that doesn't achieve is including the 7 vocabs under teh 'topmost' master vocab (the module is a one way street). So when it came to making content tagging user-friendly, and needing to be able to tag even the 7 vocab names, I realised (after trying many modules) that I would have to get all the terms under one vocab.

Challenge:
1. Not to lose the functionality of design I'd achieved with various menu modules (simplemenu, dhtml menu... ) and some minor php code changes...
2. To use phpmyadmin to muck with the database (scary for novices like I)

The Steps: (all in phpmyadmin with my database selected, obviously)

Backed up database at host (though I know not where the backup went...)

Opened 4 tabs in my browser and navigated each to a different table of the database:

1. The 'term_data' table. Here you will find all of the terms, their term id (tid) and their vocab id (vid), I made sure I could see all rows & printed this out for reference.

2. The 'term_hierarchy' table. This is a list of tid & vid pairs which determines the menu layers in effect (whereas term_data determines which overall vocab a term is in) , & printed this out for reference.

3. Vocabulary table. Here I would delete (via the red 'X') the vocab for each of the seven vocabs, but I did this last, after having confirmed that the new sub-menu of master equivalent was functionaing in the same way with my installed modules)

4. Menu table. (having taxonomy menu module active meant that menu table options were being generated which were then unused and DO NOT go away graciously when disabled in Drupal admin menus, so I needed to clear this up to)

After some missteps, I realised that I first had to create 7 'term_data' table entries of the same name as my 7 vocabs, with vid = master vocab, so that I could then point all the terms to the appropriate level in the The 'term_hierarchy' table. If I didn't do that first, auto menu generating module would get confused and things went missing.

Once done, I found that I didn't need any module for neat tag content entry except taxonomy_super_select. It also turned out not to be good to use the drupal interface as an alternative at any time because of host caching not giving me what was there at that moment.

It's quite a task, with identical menu names and vocab term names one affecting the other, to keep it all straight. I made the changes manually (using the pencil button) because I don't trust my sql command knowledge and also because I was doing it incrementally, checking for module compatibility etc.

All done, and thanks to each of you, especially Ryan Constantine for most help on this. You can check out the site at www.morethanoil.com

Regards
Zaph

rconstantine’s picture

rconstantine commented

Glad to hear you got it working. So I guess the taxonomy menu thingy worked out with your new taxonomy? Great!

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)