Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URLs doesn't get clickable on description #30

Closed
AntoineTurmel opened this issue Nov 18, 2012 · 7 comments
Closed

URLs doesn't get clickable on description #30

AntoineTurmel opened this issue Nov 18, 2012 · 7 comments

Comments

@AntoineTurmel
Copy link
Contributor

When you put a link on a description (either plain or using DokuWiki syntax), the link show up but is not clickable.

@selfthinker
Copy link
Collaborator

I'm not sure that is a bad thing...

@AntoineTurmel
Copy link
Contributor Author

Well the user can still put links after plugin template, but sometimes you may wants to mentions in description that this plugin connect to this website giving a link to it..

@selfthinker
Copy link
Collaborator

In general it's always a good idea to have data in it's purest form. If we allow links in the description, it's data with "sub data". It also depends on what you might want to do with the description. In the current situation there won't be any problem. But what if you might want to link the description somewhere (in the plugin table or in one of the "pluginnews" boxes)? You wouldn't have the freedom to do that.

The advantages of allowing links might outweigh that. But you can never be sure what people might want to do with that data and at least we should think about its possible implications.

@AntoineTurmel
Copy link
Contributor Author

Ok, so maybe we can add an option to parse the description for links and render them with a <a href> tag ? So we can enable this parse by option either on an entry, table, pluginnews ?

@splitbrain
Copy link
Collaborator

No having entries that behave differently makes the problem @selfthinker described even worse.

Supporting links would either require to parse them ourselves or to run a whole new parser/renderer process on the description which is not a good idea performance wise.

@HakanS
Copy link
Collaborator

HakanS commented Nov 22, 2012

IMHO we should follow "It's better when it's simple"

Plugin/template authors should use their few words of description to describe features of the extension. Sometimes mentioning "WikiPedia" or something similar conveys a lot of information but I don't think a link is necessary. Naturally they should pay proper credit on the extension homepage but not in the description.

Issue #25 and #27 are more useful to our community

@Klap-in
Copy link
Collaborator

Klap-in commented Jun 26, 2015

summary: won't implement because simpler text is better and performance wise.

@Klap-in Klap-in closed this as completed Jun 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants