Download & Extend
Activity » Issues

Create an upgrade path

Posted by sirkitree on March 5, 2009 at 5:43am
Project:Activity
Version:6.x-2.x-dev
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

We need to create an upgrade path from 6.x-1.x to 6.x-2.x

Login or register to post comments

Comments

#1

Posted by 63reasons on July 14, 2009 at 11:08am

subscribing

#2

Posted by pribeh on July 24, 2009 at 10:41pm

Hi 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.

#3

Posted by sirkitree on August 2, 2009 at 4:23pm

It'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.

#4

Posted by saturnin on September 10, 2009 at 4:14pm

subscribing

#5

Posted by dgtlmoon on October 26, 2009 at 1:47am

ping

#6

Posted by geshan on November 12, 2009 at 3:29pm

It would be great if there is a solid upgrade path.

#7

Posted by Scott Reynolds on January 18, 2010 at 10:23pm

Here are some notes for a db update

  1. Mapping Activity to the new Activity table
    • aid and uid stay the same
    • module becomes type
    • operation becomes op
    • all nid become NULL columns to be filled in later step
  2. Activity targets
    • drop the role field
    • add the amid field that will be filled in at a later step
    • change target_uid to uid
    • Change all uid == -1 to uid = 0
  3. Generate messages and store them away
    This is the tricky part that probably needs to happen first
    • For each message and for each role, activity_token_replace($activity) to get the message and store it away in the activity_message table. in order to do that we need to have an activity_load($aid) as well that is just a bit simplified (no activity_invoke or comments)

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.

#8

Posted by okday on March 5, 2010 at 2:55am

subscribing

#9

Posted by moscheIT on June 23, 2010 at 8:11am

subscribing

#10

Posted by Steven Jones on August 20, 2010 at 9:50am

subscribe, we'll be needing this, and might be able to devote some time over to implementation.

#11

Posted by sirkitree on September 11, 2010 at 11:41pm
Status:active» closed (won't fix)

I 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.

#12

Posted by thehandyman on February 18, 2011 at 3:42am
Status:closed (won't fix)» active

Sorry 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.

nobody click here