• ResolvedPlugin Author Jason Coleman

    (@strangerstudios)


    Please upgrade to 1.7.0.2 as soon as possible. Especially if you installed PMPro fresh from version 1.7 or 1.7.0.1.

    There was a huge bug with the DB generation in version 1.7 and 1.7.0.1 of the plugin, which was causing issues on fresh installs of PMPro 1.7 or 1.7.0.1 (if you upgraded from an earlier version, you would have been okay).

    Issues included not being able to change someone’s level, checkout not redirecting, and changing of levels just generally not working across the plugin.

    Upgrading to version 1.7.0.2 that was just pushed out should fix your problem. Please open a new support thread here.

    Needless to say, this was a big issue and should have been caught in testing. We are updating our testing methods to catch things like this in the future (i.e. doing more testing on fresh installs of the plugin and specific upgrade paths).

    Thanks and sorry for the trouble this has caused.

    http://wordpress.org/extend/plugins/paid-memberships-pro/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Just updated to 1.7.0.2 and the blog completely crashed :)) worked fine on 1.7.0.1, where could I download that from?

    Downloaded version 1.7.0.1 again, tried to update again, blog completey broke, installed 1.7.0.1 the third time, everything works.

    Plugin Author Jason Coleman

    (@strangerstudios)

    Upgrade to version 1.7.0.3. Some testing code left behind in 1.7.0.2 might have bogged down smaller servers/hosts.

    Sorry for all the updates.

    Ok, thanks.

    I have the same problem. I have upgraded to version 1.7.0.3. and I still getting this error

    Fatal error: Call to a member function cancel() on a non-object in /public_html/www.mysite.co.za/wp-content/plugins/paid-memberships-pro/preheaders/checkout.php on line 981

    There is now a further update 1.7.0.4 that should resolve this. Please let us know if it does not, thanks.

    @zaone, @le roux – just checking back to make sure that you are now on 1.7.0.4 and the issue is resolved.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Please Upgrade to 1.7.0.2! Critical DB fix.’ is closed to new replies.