Categorization messes with tag links
ChristophWeber - September 5, 2008 - 00:27
| Project: | Frequently Asked Questions |
| Version: | 6.x-1.7 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
When I switch on categorization in faq - which I like very much, awesome feature! - some of the links (but not all) from the tags at the bottom of my pages are changed from taxonomy_vtn/term/N to faq/N. It seems like taxonomy_vtn and faq modules are fighting over these links. What I want is consistently correct behavior, i.e. all tags linked to taxonomy_vtn/term/N, regardless of faq settings. How can I achieve this?
For completeness, I am still using taxonomy_vtn 6.x-1.0rc2 because it has not caused any issues otherwise.

#1
Only terms within the FAQ vocabulary will have the links changed to 'faq/N'. This is a feature, not a bug.
I've made this feature configurable. So please try the attached patch or the latest dev release (available later today).
Cheers,
Stella
#2
Thanks for your quick reply, stella. The altered code works great.
The patch didn't go on cleanly for me, and of course it was the crucial new checkbox which was left out. However, after some manual fiddling I've got faq.admin.inc where it should be, unchecked the "Enable FAQ category links" box and everything now works the way I need it.
In my opinion this is a patch which should go into the official module to give admins a choice. Just my 2 cts.
Thanks again, I am VERY impressed by the quick turnaround!
Christoph
#3
When the next official release is made, it will be included.
Cheers,
Stella
#4
Awesome! Thanks again, Stella, I truly appreciate your work!
- Christoph
#5
That worked great for me as well. Is there any way that it can add the FAQ links instead of rewriting them? I'd like to have both and theme them differently!
#6
z allen: You could do that from within your theme I think. It's not something I intend on adding to the faq module, sorry.
Cheers,
Stella
temp
Automatically closed -- issue fixed for two weeks with no activity.
#7
Automatically closed -- issue fixed for two weeks with no activity.
#8
Released in 5.x-2.12 and 6.x-1.8.
#9
Released in 5.x-2.12 and 6.x-1.8.