Download & Extend
Drupal.org project link filter » Issues

Allow to give a custom text for the link

Posted by jonhattan on August 11, 2009 at 10:18am
Project:Drupal.org project link filter
Version:6.x-2.2
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:needs review

Issue Summary

It could be very nice to use this syntax in addition to current one:

api.module|"The API module"

so if the pipe character is present after the matching pattern, the following text is used as the text for the link, instead of the project name.

Login or register to post comments

Comments

#1

Posted by z.stolar on August 11, 2009 at 1:32pm

Yes it would!

I'd happily apply a patch, if one is supplied.

#2

Posted by jonhattan on August 13, 2009 at 1:17pm
Status:active» needs review

so a patch is supplied :)

Note I'm not good at all with regexes. Anyway the tests I've made all have worked fine.

AttachmentSize
custom_title.patch 1.62 KB

#3

Posted by Arshad Chummun on May 30, 2011 at 7:25pm

I applied this patch to the 6 branch and it works. Thanks.

But after using it for some times, I find typing | and the quotes difficult and not really easy in terms of usability.

I think something like api.module(Api module) is easier.

What do you think?

#4

Posted by z.stolar on May 30, 2011 at 7:33pm

After a second thought, I tend to not agree with this addition. This module is simple to use, and does a fairly good work at what it's aimed to do.
I feel that adding complexity (a.k.a. features) to it may damage it's ease of use.
Of course - I guess using this syntax won't be compulsory, but still - simplicity has it's advantage.

In any case - I'm not determining anything, just adding my 2 cents.

#5

Posted by z.stolar on May 30, 2011 at 7:33pm

After a second thought, I tend to not agree with this addition. This module is simple to use, and does a fairly good work at what it's aimed to do.
I feel that adding complexity (a.k.a. features) to it may damage it's ease of use.
Of course - I guess using this syntax won't be compulsory, but still - simplicity has it's advantage.

In any case - I'm not determining anything, just adding my 2 cents.

#6

Posted by Arshad Chummun on May 30, 2011 at 7:57pm

I have found some use cases for this, which make me want to go "for" this addition.

  1. Sometimes, a module name might not fit the context.
    eg. "To create complex layouts in Drupal, you should use this module" where "this" here would be a link to the panels page, as opposed to using the module name which will print Panels.
  2. Dopl has support to link to nodes as well, which is really helpful when you want to link to handbook pages. In this case, the whole title of the node is used. Same case as in 1 when you want to fit into the context and don't want to print the whole node title.

But I agree that too much features will make the module complex and harder to get into Drupal.org. I think if we can found a way to make this feature accessible and easy to use, it might be a good addition to the module.

Fight! :)

nobody click here