Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We need to create an upgrade path from 6.x-1.x to 6.x-2.x
We need to create an upgrade path from 6.x-1.x to 6.x-2.x
Comments
Comment #1
MisterSpeed CreditAttribution: MisterSpeed commentedsubscribing
Comment #2
pribeh CreditAttribution: pribeh commentedHi there, just checking to make sure whether or not there will be an upgrade path from 1 to 2 that will preserve the activities from version 1 in such a way that they can be seamlessly used with the activity 2's publisher templates. If not than I just might start using activity 2 for a site that I'm running and work with erasing all the old 1.0 activities of the site's users.
Thanks.
Comment #3
sirkitree CreditAttribution: sirkitree commentedIt's definitely something I'd like to have before we make a full release, however I've not much time or need to work on this myself. I've just posted some code that will allow you to create activity records on an existing site #529318: Generate activity on an existing site + reset activities option. which might give someone some ideas on how to go about writing a migration path from 1.x to 2.x.
Comment #4
saturnin CreditAttribution: saturnin commentedsubscribing
Comment #5
dgtlmoon CreditAttribution: dgtlmoon commentedping
Comment #6
geshan CreditAttribution: geshan commentedIt would be great if there is a solid upgrade path.
Comment #7
Scott Reynolds CreditAttribution: Scott Reynolds commentedHere are some notes for a db update
This is the tricky part that probably needs to happen first
These notes fail to address at least to other parts of Activity. The Activity Comments will need their own upgrade script in that module. And the activity user opt out settings will somehow need to be preserved.
Edit:Please note that I have very little motivation to create an upgrade path. I am not a maintainer of the 1.x branch and I have never nor will I ever run 1.x on any site. So I don't have a need for this and it happens to be quite a bit of work. I don't plan on doing all this, but I will review patches to ensure the semantics of the messages are preserved. Perhaps one day I will but I don't envision it. And I don't personally have a problem creating a official 2.X release without an upgrade path.
Comment #8
okday CreditAttribution: okday commentedsubscribing
Comment #9
moscheIT CreditAttribution: moscheIT commentedsubscribing
Comment #10
Steven Jones CreditAttribution: Steven Jones commentedsubscribe, we'll be needing this, and might be able to devote some time over to implementation.
Comment #11
sirkitree CreditAttribution: sirkitree commentedI don't think we're ever going to get this. We've created a way for regenerating activity messages and I think we're going to just stick with that method. Please reopen if you come up with a patch and we'll review it, but I don't think either Scott or myself are going to write one.
Comment #12
codevoice CreditAttribution: codevoice commentedSorry to reopen this, I know sirkitree made himself clear, but what have you other subscribers done as far as upgrading? I'm in the same boat, on 1.x in a very, very active site and would like to upgrade, but with no option to do so I'm stuck.
So, looking to discuss work-around, hacks, whatever you guys managed.