Migration from aggregator2

hi zis,

we are using leech heavily in three projects and very likely in a couple of more projects ahead.

while leech is working very fine for us, we are a little bit unhappy with the complexness of handling it and the basic program architecture. we are looking to give it a profound overhaul for the 4.7 version with an eye on the upgrade path to 5.0.

whatever we do here, there will be clear upgrade path from the current leech version and a clear path to a future 5.0 version. there is no decision or even discussion so far about actually doing the 5.0 upgrade though, as all concerned production sites are very happy on 4.7 now.

cheers,

alex

I'm not really sure you addressed the original question. Will there be an upgrade path from aggregator2 to Leech? For instance, many members of my website have off-site blogs which are currently posted to my site via aggregator2. I would like to move from aggregator2 to an actively developed module, with future Drupal 5 compatibility, but I'm concerned that I will loose all the aggregated blog entries. Is there something as easy as installing the Leech module and removing the aggregator2 module, keeping all the current aggregated nodes?

It's not as easy as just installing leech over aggregator2. Unfortunately, I am not familiar with aggregator2. If you have any particular questions to the inner works of leech, I ll be happy to address them. If you are going to convert from aggregator2 to leech, It'd be great if you put up a upgrade recipe here.

hum - I need the exact thing agg2 => leech

Me to, i have 5 websites depending on aggregator for 4.6 (4.7 is not really working) and only reason way they are not yet on 4.7 (or 5.0)

Hi Alex,

I really love Leech which I installed today on a fresh drupal 4.7.
I have a lot of sites that still use massivly patched Agg2 and it would be suprfine if you could help all of us by finding a way to migrate Agg2 to Leech...

I already thought about freezing all Agg2 feeds and switch to Leech, but the "discard feed items older than.." is missing and I would leech a bunch of duplicate content.
If Leech would allow this "discard" option it would be possible to switch from Agg2 to Leech without too much pain. Okay, it may be a lot of work to set up all of your feeds again and freeze the old ones, but it would work.

Thank you for you work. This module is awsome, I love it.

:-)

alex_b said: Unfortunately, I am not familiar with aggregator2.

That's just a bit weird, since the description of Leech bills it as the "reincarnation of aggregator2."

funana said: I already thought about freezing all Agg2 feeds and switch to Leech

Is that possible? I'd be happy to re-create the feeds as long as the existing feed items were still usable in perpetuity. I posted a forum topic re: the continued usability of nodes once their modules have been deactivated/deleted, but I received no responses. In a nutshell, if I delete a module (i.e. aggregator2), will the nodes it once created be usable forever and ever amen, despite drupal upgrades, form api changes, etc. etc.? If so, this is largely a non-issue.

funana said: I already thought about freezing all Agg2 feeds and switch to Leech

Is that possible? I'd be happy to re-create the feeds as long as the existing feed items were still usable in perpetuity. I posted a forum topic re: the continued usability of nodes once their modules have been deactivated/deleted, but I received no responses. In a nutshell, if I delete a module (i.e. aggregator2), will the nodes it once created be usable forever and ever amen, despite drupal upgrades, form api changes, etc. etc.? If so, this is largely a non-issue.

Here's what I learned:
- you can delete the Agg2 module and the nodes will stay untouched BUT you are not longer able to delete or edit them, so pls. don't do that...
- You should just freeze all Agg2 feeds, install Leech and set up the feeds in Leech. There is still an issue with duplicate content then, because Leech will discard no items that have been aggregated with Agg2 before. You can delete the duplicate Agg2 nodes then by hand...

I hardly recommend to switch to Leech. It's a much more better module for aggregation than Agg2 now.

alex_b said: Unfortunately, I am not familiar with aggregator2.

canadrian said: That's just a bit weird, since the description of Leech bills it as the "reincarnation of aggregator2."

True :) The reason is, that I took over leech module from the creator of aggregator 2 module: Marcin Konicki.

funana said: I hardly recommend to switch to Leech. It's a much more better module for aggregation than Agg2 now.

You recommend or you do not recommend? - I am irritated by "hardly".

funana: The way you suggested to upgrade leech should be fine. Freeze aggregator2 feeds and turn on leech. Issues with duplicates could get handled by unpublishing duplicate feed items by hand - if the feed base is not too big, the effort for it is manageable.

Generally, you should be able to integrate the leech feed item node type (which is a node type of your choice) seemlessly with the aggregator2-item node type. I.e. if leech feed item node type is "story" you could create a view that lists aggregator2-item and story nodes.

If you're ready for some fun, though, you could also try this: Leave aggregator2 module installed and define aggregator2-item node type as leech feed item type. (You will have to do this by creating a node template from an aggregator2-item and assigning this template to a feed). If anybody has done this, please let us know! Could be a great strategy to drop-in replace aggregator2.

You recommend or you do not recommend? - I am irritated by "hardly".

I assume that funana really meant to say "heartily"...

I assume that funana really meant to say "heartily"...

Yes, you are absolutely right. English is not my native language...
Trying to improve :) Allways learning.

I recommend switching!

I switch this to a more current request with a bounty:

http://drupal.org/node/154679