Posted by gswaim on January 17, 2007 at 11:49pm
Jump to:
| Project: | Links Package |
| Version: | 6.x-2.x-dev |
| Component: | Code: links_weblink.module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | syscrusher |
| Status: | active |
Issue Summary
I hope this is a good place to ask this....
From reading the documentation it looks like this module can be used with the old Weblink module (weblink.module). I am using the Web Links module (weblinks.module) and want to upgrade to 5. It is not available in 5. Could I use the Links Package 5.0 version to upgrade my Web Links content?
Thanks in advance for any help on this!
Grant
Comments
#1
Ber Kessels has deprecated the old Weblinks module in favor of merging into Links Package.
Ber did two different versions of his module (actually, more than that, but the most recent two are relevant here). The older Weblinks had its own table structure, whereas the latest one had a table structure that mimicked that of the Links Package, to make it easy to migrate to Links Package later.
If you're running Drupal 5.0, and you don't have any legacy Weblinks content to migrate, then the modules you need are "links" and "links_weblink". If you are migrating legacy content, then take a look at the instructions in UPGRADE.txt for a detailed explanation of the migration scripts.
Note that one of the migration scripts has a new open issue, which I haven't had time to investigate yet due to business travel. You may want to follow that thread also.
If you're new to Links Package, please do note the difference between links_weblink and links_related. links_weblink is designed to create a node type that "is a link", whereas links_related is designed to add links to nodes of arbitrary types. links_weblink is meant for a Yahoo™-like directory. Note that it's possible for a links_weblink node type to also have related links, though that may be confusing to visitors! {grin}
Jeff Eaton, who has just joined the Links development team, and myself are very eager to create a CCK field type for Links. That will probably cause the eventual deprecation of links_weblink, *but* I am absolutely committed to an automated migration of links_weblink nodes into CCK if and when we ever deprecate links_weblink.
I hope you enjoy Links. Please do note that it's a work in progress. What's there now is stable enough that I use it on my own sites, but it's not 100% feature complete (especially in the global links management area). So do check back now and then for new versions.
Syscrusher
#2
Hi,
Setting this to version 6 dev if thats ok with you.
Web links is also in active development: www.drupal.org/project/weblinks.
How is this Links Package related? And wouldn't it be great to or combine effort, or get these two packages going two directions which both are userfunctionality focussed?
May be some issues are better solved with the Web links module, and others are better solved with the links package?
I do not have the wisdom, but now I see two great products getting improved moving the same track?
Thanks a lot in advance for your point of view.
Greetings,
Martijn
www.trekking-world.com
#3
The Weblinks project and the Links project are not related. It appears to me that Weblinks essentially duplicates the function of links_weblink, which is a subset of Links. I haven't tried Weblinks, so I can't comment on that module's features.
In any case, I think having fields in core in Drupal 7 is going to eliminate the need for both my subset module (links_weblink) and their module (Weblinks) in the future. This doesn't mean Links itself is going away -- quite the contrary, I am committed to moving it forward to Drupal 7 and beyond. But Links may no longer need to provide a dedicated node type specifically to catalog links, as Drupal 7 and Views can combine to do that already. What Links will provide is the things that Drupal core and Views do not already provide.
Kind regards,
Scott