I'm trying to locate in the .module file where I can disable the display of the listing of the selected options on the node view page.

I'm choosing to use the main taxonomy integration so that I can use those for other modules that rely on the taxonomy data.
I would like to remove any display of the selected info on the front-end.

Essentially, I'm only wanting to use this as a backend feature to integrate the options in a much nicer way than the backend on the taxonomy/categories.

Thanks for your help.

Comments

rconstantine’s picture

rconstantine commented
Category: support » feature

I'm changing this to a feature request as I think this could be generally useful to choose whether to list the selected items on a node or not. Are you using them as tags? I think I made an option for that - i.e. regular taxonomy table entries get made.

Anyway, to answer your question, look at the function called 'cck_taxonomy_ssu_field'. There is a case 'view' which is what does the displaying of the CCK data in the node. IIRC that is.

So you should just be able to comment that whole section out.

himerus’s picture

himerus commented

after several hours playing around with my taxonomy, and the .module file, I tried everything in the module PHP file to get it to work to no avail....

HOWEVER, after realizing I had forgot one place, I went back to Content Types, then edit my selected content type, then select display fields, and then turn all the dropdowns to hidden.... I'm a retard! lol

I think this solves my prob just fine now, I just have to remember and document the steps for my own use on this particular project.

Thanks for a quick reply though!

Note: A quick feature to auto set those to hidden for users in my situation might be beneficial, as I've never heavily implemented any CCK stuff or used heavy taxonomy setup in any of my prior Drupal projects.

Thanks again!

himerus’s picture

himerus commented

but in reply to your message, I did comment out the entire section of the 'view' switch statement, and had cache disabled, and it still showed up no matter what I did....

that portion was driving me crazy, but I've reverted the code to original state, and fixed it with my settings mentioned above.

Might want to test out commenting out that section on your end to verify if something is a lil wonky there. I also tried the CONTENT_CALLBACK_NONE in the cck_taxonomy_ssu_field_settings() function after uncommenting the callback section, but that didn't seem to what I wanted either.

Thanks!

rconstantine’s picture

rconstantine commented
Status: Active » Fixed

I don't know what I was thinking. If you leave out any section in a CCK field module, CCK uses its defaults, which I'm sure is why it was still showing up. So instead, perhaps in the view case that I mentioned, you could unset each of the fields, or something.

Anyway, if your method works without side effects, good for you. I'd be interested in a more thorough explanation of your use-case so as to evaluate what I might be able to do with this module that could open up options for others. Marking as fixed.

Anonymous’s picture

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

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