Hi,
I am building a site where i need to associate several different vocabularies and tags to the Biblio nodes. The problem i am experiencing is that every time i add a new tag of any of my created vocabularies to a biblio node it also gets added (duplicated) into the biblio keywords. This happens both if i have a vocabulary associated to biblio in the biblio settings ("Biblio Keywords" vocabulary) or even if i remove "Biblio Keywords" vocabulary as it still gets added directly to the biblio_keyword and biblio_keyword_data database tables.
The duplicated tags can be removed using the "Biblio settings - Keywords" administrative interface and the state of the site then becomes correct again but the tags of vocabularies not associated with the keywords should not be affecting them. Moreover, every time i just edit and save a biblio node, the biblio keywords get populated again with any tag of any taxonomy vocabulary, so i have to remove them again and again. I am not sure if this is a bug or a feature, but it would be nice to at least have an option in the configuration to limit the keywords added to a biblio node to those added to the "Biblio Keywords" vocabulary and not all aditional taxonomy vocabularies that may be associated with biblio nodes.
I have made a workaround by deleting the Biblio Keywords vocabulary and commenting the lines 91-105 of biblio.keywords.inc (Biblio 6.x-1.4) but it probably brokes some things related to the correct handling of keywords and it probably also brokes the use of the "Biblio Keywords" vocabulary, that i wish i would not have had to remove...
Despiste of that, i love this module, so thank you very much for making it and specially for the latest additions and changes like the improved views support (this part will also greatly benefit with the possibility to use more biblio fields, like the publication year for instance, in views filters and sorting).
Thanks again and any help will be greatly appreciated.
Comments
Comment #1
rjerome CreditAttribution: rjerome commentedI believe this issue has been addressed. There is a new admin option (in the keywords section) in the -dev version which allows you to turn off the copying of terms to the biblio_keyword database. Maybe you could try the -dev version (before I make a new release) and see if this solves your problem.
Ron.
Comment #2
jrgonzalez CreditAttribution: jrgonzalez commentedThanks!, i have tried the -dev version and the keywords are no longer copied, so it works perfectly now for my current project (problem fixed).
Still (as a suggestion), i ideally think that the copy of keywords is not a bad thing, but that i should be limited to a selected vocabulary, maybe allowing to activate / deactivate the creation/synchronization with a specific taxonomy vocabulary ("Biblio Keywords") that is kept in sync with the biblio keywords. This would allow us to have a taxonomy vocabulary for keywords tagging while not mixing the keywords data with other vocabularies for other kind of tagging that is not keyword-related.
Juan Ramón
Comment #3
jrgonzalez CreditAttribution: jrgonzalez commentedHi, i have updated to the new updated -dev version (to see if i got the sort by year in views patch...) and the problem is happening again :S. Maybe some change in between re-introduced the behaviour of copying keywords even if the option is not active in the settings. And i made the big mistake of not saving a copy of the previous -dev version :S
Comment #4
rjerome CreditAttribution: rjerome commentedI'll check to see if something got merged in by mistake.
Comment #5
rjerome CreditAttribution: rjerome commentedIt's fixed now. A minor change on my part had an unexpected result :-(
Ron.
Comment #6
jrgonzalez CreditAttribution: jrgonzalez commentedIt is still failing to me, i have downloaded the latest -dev and the tags are still copied to keywords ignoring the settings.
After that I thought that maybe the latest -dev version was generated prior to the fix so i also downloaded some files that seemed different/newer from the CVS (biblio.module, biblio.keywords.inc and biblio_theme.inc) but it fails too :S. Maybe i missed something else newer on the CVS but i will try to test it again when i am back of a short two day work travel i have to do. Anyway, thanks for all the hard work.
Comment #7
rjerome CreditAttribution: rjerome commentedI'm not sure why you are still seeing this problem, I did test it on my end and they only got copied if the option to copy them was specifically selected.
Maybe try clearing the Drupal caches and test it again.
Ron.
Comment #8
jrgonzalez CreditAttribution: jrgonzalez commentedYes, i have just come back and it worked fine without even doing nothing so it was surely a cache issue or something like that.
Thank you very much again!