Hey all,

I wanted to get this thing working w/ content taxonomy and so I did :). The problem is I did it without any regard to its existing cck widgets.

So basically the attached patch makes this module work with content taxonomy widgets but not regularly. I didn't have time to get it to work both ways. The widgets show up for text/numbers fields, but wont work right.

It works great w/ CT though :).

CommentFileSizeAuthor
#2 0001-fixed-the-other-text-in-css-settings.patch2.45 KBthat0n3guy
#1 0001-completely-working-with-content-taxonomy.patch23.77 KBthat0n3guy
0001-working-with-content_taxonomy.patch18.98 KBthat0n3guy

Comments

that0n3guy’s picture

that0n3guy commented
StatusFileSize
new 0001-completely-working-with-content-taxonomy.patch23.77 KB

I decided that was a pretty sad patch and took a shot at making it better... Turns out, it was really easy.

Attached is a patch that lets this thing work with content taxonomy without effecting its current features at all.

I would love it if some people would test this guy out. I'll be putting it on a live site soon probably.

that0n3guy’s picture

that0n3guy commented
StatusFileSize
new 0001-fixed-the-other-text-in-css-settings.patch2.45 KB

oops, found an error.

After applying patch at #1... apply this patch (sorry the 2 aren't combined)... that way you can specify the "other" text

danielb’s picture

danielb commented
Status: Needs review » Needs work

That is a massive patch, and I'm not too confident about putting it in. I would prefer to see this implemented in a separate module TBH.

that0n3guy’s picture

that0n3guy commented

Yeah, most of the patch (like 80%) is formapi stuff, so that stuff is pretty simple. This could probably be easily be broken out into a content_taxonomy_widget.module or something. I just didn't have the time.

danielb’s picture

danielb commented

If this goes ahead: #981530: Port Select (or other) module to D7
Then I can turn this project into a package of support modules for integrating the select or other element with other modules.

danielb’s picture

danielb commented
Status: Needs work » Closed (won't fix)

I'm not convinced about this patch, it does not harness the existing element, rather it duplicates the functionality for a specific case. This isn't my idea of the integration patches I'd like to support.

YK85’s picture

YK85 commented
Title: Patch to get this thing working w/ content taxonomy » Content Taxonomy Integration
Version: 6.x-1.6 » 6.x-2.x-dev
Status: Closed (won't fix) » Needs work

Could this kindly remain in the queue for a feature request of Content Taxonomy Integration?
I have set the status to "needs work".
I hope this feature could please be considered.

Thank you!

danielb’s picture

danielb commented
Status: Needs work » Closed (won't fix)

I don't see a point unless you can come up with a reasonable integration patch.

francewhoa’s picture

francewhoa
he/him
Primary language French
Location Sept-Îles, Québec, 🇨🇦
commented
Component: Code » CCK / Field API widget

+1
Any volunteer to contribute a patch/sub-module that meets danielb requirement? We would be happy to contribute testing and documentation.

hachreak’s picture

hachreak commented

+1 :D

elithorkelson’s picture

elithorkelson commented

I recently wrote up some code as a new D7 module that uses Select or Other form functionality to integrate with the Taxonomy module -- I called it Select or Other Taxonomy. If people are interested, I just posted the working code on a thread at the old Taxonomy Other project page. I'd love to know if it works for other people, or if people think it should end up a new module. Personally, I can see danielb's argument for not integrating it into his module, but the case could be made either way.

adam_b’s picture

adam_b commented

I'd love to see this made available by some means. From a non-coder perspective it makes sense for it to be part of this module, but if the code is incompatible then a separate module would be fine.