Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Christian Wach

    (@needle)

    Hi Matthew,

    Can you be a bit more specific about your environment – which version of WP, BP etc? BTW, I recommend not deactivating the plugin unless you’re preparing to delete it. If you want to upgrade, simply replacing the plugin files avoids the issue (as the plugin info states).

    Cheers, Christian

    Thread Starter matthewnelsonj

    (@matthewnelsonj)

    Thanks for responding.

    I do plan to delete it. Your plugin is 0.6.3 and I’ve already deactivated BP. on WP 4.2.4

    Plugin Author Christian Wach

    (@needle)

    If you’ve already deleted BuddyPress then it’s a given that Class ‘BP_XProfile_Field’ isn’t defined. I’d suggest that this isn’t specifically an issue with this plugin, given that it is entirely dependent on BuddyPress. Having said that, I can see that the code could be more defensive. Thanks for the report, I’ll bear this in mind for the next update.

    Cheers, Christian

    Thread Starter matthewnelsonj

    (@matthewnelsonj)

    I now realize the problem, and it’s one of those seemingly obvious ones:

    although I got this error while BP was still installed, it wasn’t activated. So any deactivation/deletion needs to be done in specific order of BP_Xprofile sync first, and then BP. I’d suggest you add a quick note about this alongside the update/installation notes.

    Thanks for your help.

    Plugin Author Christian Wach

    (@needle)

    I’ve added code to prevent the fatal error in the development repo. It’ll be included in the next release. Thanks again for the report.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘deactivation fatal error’ is closed to new replies.