Since uc_recurring and authorize.net ARB where closely tied in the 1.0 branch to allow sites using that gateway to migrate from 1.0 to 2.x there needs to be upgrade path.

Comments

univate’s picture

Priority: Normal » Major
EvanDonovan’s picture

If you were not using the uc_recurring 1.x module, is this issue not relevant?

Are there still plans for this?

univate’s picture

Since there are 200+ reported installs of uc_recurring 1.0 and since to upgrade you can't just delete this module and install the new one, you need a way to get your data from 1.0 to 2.x with recurring payments continuing as normal.

I assume people will want an upgrade path. I guess I am hopping one of these 200 installs is interested in some of the new stuff in 2.x and is willing help get the upgrade working.

Of course as with any module, upgrades are only important for those that are running and older version and need to move to the current version.

jerry’s picture

Affects me; subscribing.

apaderno’s picture

Issue summary: View changes
Priority: Major » Normal
Status: Active » Closed (outdated)

I am closing this issue, since it's for a Drupal version no longer supported.