Closed (fixed)
Project:
Related links
Version:
master
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
23 Oct 2006 at 19:50 UTC
Updated:
9 Jan 2007 at 22:17 UTC
Jump to comment: Most recent
It would be nice if there were more configuration options for each link type:
Also, it would be great if taxonomy vocabularies could be activated/deactivated for use with taxonomy links.
Here is a patch to add these features.
| Comment | File | Size | Author |
|---|---|---|---|
| relatedlinks.module.patch_9.txt | 18.32 KB | colan |
Comments
Comment #1
Zen commentedMost of the UI additions in this patch have been committed to CVS - thanks :) The rest will be dealt with in http://drupal.org/node/91543 .
-K
Comment #2
colanOne more thing:
if (!isset($default)) {should be:
if (!isset($defaults)) {...in _relatedlinks_get_type_defaults(). (You forgot an "s".)
Comment #3
Zen commenteddefault to defaults - fixed :)
Cheers,
-K
Comment #4
(not verified) commentedComment #5
Anonymous (not verified) commentedThanks for your work, being able to deactivate vocabularies is exactly what i was searching for. I've updated the related_links module, executed update.php and see all the wonderful new config options in admin->settings->related_links. Great.
However, I now get the following PHP error on any page that wants to display the block for related terms:
* warning: array_merge(): Argument #2 is not an array in /home/figu/public_html/www.figu.org/modules/relatedlinks/relatedlinks.module on line 144.
* warning: Invalid argument supplied for foreach() in /home/figu/public_html/www.figu.org/modules/relatedlinks/relatedlinks.module on line 727.
The block is displayed properly when only parsed links are shown. Any help is appreciated.
Thanks,
Stephan
P.S. Sorry if this is the wrong way of asking for help, I actually didn't want to file a new bug report, since I don't know whether this really is a bug or not.
Comment #6
Zen commentedStephan: Please see: http://drupal.org/node/102971
The best way to get help is to:
a) Search the issue queue for the module and if you find your issue there, add a comment to it..
b) If you don't find your issue, open a _new_ issue.
Cheers :)
-K