I've been thinking a little about the weblink module and how I might implement it on my site. I think there are three types of weblink posts.
1. Site recommendation - "Hey I just found this cool site, you should check it out". The weblink module fits this use very well. User's create content of type weblink and it is added to the site and to the directory.
2. Reference in a post - The user is posting to his/her blog and makes reference to a URL. I guess it would be cool if these links were automatically 'detected' and added to weblink queue for possible classification or addition to the weblinks taxonomy.
3. As commment to a post - Readers often comment with a simple recommendation to look at another site. If these types of comments were treated differently than a general comment it could be classified and added to the taxonomy as well as to the comment thread.
Cheers to all!
- Joe
Comments
Comment #1
adrian commentedWe are working on a new version of the weblink module to be released around the same time as 4.3.0
Simon/Ber have written code that is able to filter node content and extract links out of them , and assign certain terms to them / use a template to fill in their details.
The module is also capable of replacing neighbour and cloud modules.
Comment #2
arsart commentedhow we can reorder links output on weblink/view/n
to view links, last published, on a top of this page.
Comment #3
adrian commentedthat is either a support question, but more like a feature request.
please make a seperate feature request for that
Comment #4
joe lombardo commentedDid this get added to weblink.module? It sure sounds cool :-)
Comment #5
Bèr Kessels commentedSummarising this and giving new title:
A new module should grep fro weblinks in user posts and make new weblinks out of them.
Comment #6
joe lombardo commentedI was about to post a request for just such a feature and was doing my homework to make sure it didn't already exist, how funny to see that I had the same idea two years ago :-)
Is this still considered in scope for the weblink module? Or is it being considered as a separate module.
Cheers,
- Joe
Comment #7
Bèr Kessels commented+1 on that feature. but -1 on putting it in weblink.,odule
please make it a linkharvester.module (or any other name). I will be happy to ship it with the weblink module, though!
Comment #8
Bèr Kessels commentedStill a usefull feature.
Comment #9
syscrusher commentedI agree, Ber! This feature is already partially implemented in the Links Package as part of links_related.module. It's not completely done yet, but it is definitely on its way. :-)
Scott
Comment #10
eaton commentedAnd that's why links.module is awesometastic.
Comment #11
RayZ commented@Scott: Any progress? I too think this would be a wonderful feature.
Comment #12
moshe weitzman commentedseems to me like this is in links_related.module. mark as fixed?
similar functionality is in the relatedlinks.module, fyi. see http://drupal.org/project/relatedlinks
Comment #13
jo1ene commentedYes, links_related will make embedded links into related links to be displayed at the end of the node or on the links tab. So the first point of this issue is now seemingly (it's hard to tell since it's so old) covered:
"List embedded links
If enabled, a list of links contained within the article text will be appended to the end of the content, when in full-page display mode. This listing will also appear as part of the separate links tab (if that feature is enabled)."
I would like to take this request a step further and suggest that such related links are made weblinks - as in nodes according to links_weblinks. For example, in the Amazon package, when you define a related book for a node, it creates an unpublished Amazon node from it. You can then go in and publish it if desired.
In this situation, you may want to specify a related link then have it also appear in your weblink directory. Maybe not. But if it's created as unpublished, it won't upset anything and folks can go into the content admin area and publish them - or delete them - in batch.
As it stands now, you would have to create a weblink node separately, in addition to the related link. Not fun...