Skip to:

upgraded to bp1.2, have a concern

  • Kunal17


    I just updated from bp1.1.2/wpmu2.8.6 to bp1.2.2.1 on a live site.

    Overall the upgrade went off smoothly (I still have to test extensively). However, the only mistake I made during the upgrade is that I upgraded and tried to activate bp1.2.2.1 while still on wpmu2.8.6 (I forgot to upgrade wpmu before upgrading buddypress). It threw an error about bp_loader already loaded (sorry didnt think to copy the error) and didnt activate. I then went ahead and upgraded wpmu to 2.9.2 and it showed buddypress as already activated.

    Now from first look this break in the upgrade sequence does not seem to have caused any issues. I am probably being paranoid but does anyone think I might come across problems due to this further on? Basically should I revert back to my backup and upgrade again just to be safe?


Viewing 1 replies (of 1 total)
  • I had this issue with iirc 1.2.2 and 2.8.6 on a test install, asked about it here and was told it should clear up with WPMU upgrade to 2.9, didn’t however! but no signs of any problems ever. Eventually the problem cleared up I hink when I probably did one further upgrade or at least during a period of much upgrading and deactivating/activating of plugins.

    I think the response from others is likely to be deactivate all BP plugins and reinstall BP at least I think I went the remove BP altogether route and allowed the system to report BP deactivated due to not available and then installed fresh copy and activated that. Personally I didn’t re-install backups I had no issue with WPMU upgrade and stuck with that.

    However let more experienced members advise you first, but the situation isn’t dire and will be resolvable.

Viewing 1 replies (of 1 total)
  • The topic ‘upgraded to bp1.2, have a concern’ is closed to new replies.
Skip to toolbar