uc_price_per_role module can not be updated [#1972100]

I have Drupal Core 7.22, UC 7.x 3.4, Ubercart Price Per Role 7.x-1.x-dev (2012-Dec-22)
Wanted to update uc_price_per_role module to 7.x-1.0 (2013-Mar-26) and got this message while running database updates:

uc_price_per_role module can not be updated. Its schema version is 0. Updates up to and including 6000 have been removed in this release. In order to update uc_price_per_role module, you will first need to upgrade to the last version in which these updates were available.

Then tried with uc_price_per_role 7.x-1.x-dev (2013-Mar-09) and got the same message. Any ideas?

Comments

Comment #1

DanZ CreditAttribution: DanZ commented 25 April 2013 at 22:58

Category:	bug	» support
Status:	Active	» Postponed (maintainer needs more info)

This sounds like there's something funky in your database entry that tracks the updates (schema version).

Did you use this module under D6?

Look at the {system} table in your database and find the value of the schema_version field for this module. Does that look OK?

You can probably solve this problem by doing a full uninstall and re-install of the module, but that will delete all of your price and role data.

Comment #2

yakbuttertea CreditAttribution: yakbuttertea commented 25 April 2013 at 23:57

DanZ, thank you for your reply, I have schema_version 0. Is that ok? My current version of uc_price_per_role is 7.x-1.x-dev (2012-Dec-22) is it why the schema_version might not be ok?
I don't really want to do a full uninstall and re-install of the module but if I have to I will...

Comment #3

DanZ CreditAttribution: DanZ commented 26 April 2013 at 00:47

I don't have a good explanation for this. There are 100 installs of 7.x-1.0, and nobody else is having this problem, so I don't think it's an issue with the module.

If you're feeling daring, try backing up your database, then changing that value in the database manually from 0 to 7000, then running update.php. In theory, that will fix it. If not, I'd recommend going to the forums.

In any case, the database update is not an important one. It just cleans up orphaned data that would be there if you created a role, assigned prices for it, then deleted the role.

If anyone else has this problem, please report, as that means that it is a problem with the module.