Hi,
i created a vocabulary "languages" and made it default for a new content type called job offers.
But when i enable the active tags, the ajax field autocompletes only terms from the forums vocabulary (the list of forums), same with the popular tags proposals.
And when i submit, a new term is not inserted anywhere, neither in my languages nor in the forum vocabulary.
This is astonishing, cause within the forum, it works quite nicely. There i use the taxonomy role module for the admin section and a special administration vocabulary. Everything works there as expected. Autocomplete and proposals refer exactly to the chosen vocabulary.
Do you have a clue why the active tags ignore the other vocabularies in my new content type(permissions are set now freely for all vocabularies) and only looks for the forum categories?
I changed all possible or impossible settings, cleared the cache, gave all permissions, but without a result.
Thanx
Bernd
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | active_tags-6--1-multi_auto_url_correction.patch | 938 bytes | dragonwize |
| #3 | active_tags.js_.patch | 528 bytes | borzoj |
| #2 | active_tags.js_.patch | 528 bytes | borzoj |
Comments
Comment #1
batbug2 commentedYeah, i have the same issue
Comment #2
borzoj commentedI think the problem is in the way JS extracts the vocabulary ID set in PHP. The suspect place is in active_tags.js, line 70:
var vid = context.substr(20,1);
To me this seems to assume the VID to be one character long and will fail for any vocabulary with ID >=10.
Please try my patch.
Comment #3
borzoj commentedOnce again, with the correct status I believe.
My fix is a one liner that will fix the way JavaScript extracts the vocabulary number when generating the url for taxonomy/autocomplete.
Comment #4
batbug2 commentedThe patch works for me! THANK YOU!
Comment #5
Bilalx commentedSame here, the patch is working.
Thank you!
Comment #6
dragonwize commentedcommitted, thanks for the patch and testing.
Comment #7
shadysamir commentedI'm still having this porblem. The widget should populate from VID=11 but it populates from VID=10 instead
Comment #8
shadysamir commentedSorry forgot to change status. I hope "active" is correct since the patch is now committed into 1.2
Comment #9
dragonwize commentedDebugging I found an issue with some new code in 1.2 that will affect forms with multiple vocabulary fields. The fix is nice though because this same area was also an issue with the content_taxonomy integration as well, so I got to kill two bugs with one.
shadysamir please test this patch.
Comment #10
shadysamir commentedWorking fine. I have the same vocabulary used several times in multiple content taxonomy fields. I also have popular terms enabled for this vocabulary (even though they're not showing with CT widget)
Comment #11
dragonwize commentedThanks. Committed. Rolled 1.3 as this was a critical fix.
Comment #12
catofcheshir commentedThere are
var vid = context.substr(20,1);in active_tags_popular.js in 1.3 :(Comment #13
catofcheshir commentedComment #14
dragonwize commentedFixed and committed. Will be in the next release when #325467: Popular tags are not popular & SQL group by issues on pgSQL and MySQL 4 is committed.