Conflict with PMPRO Paidmembershipspro, 404 eror

[mrkellysch]

When the Badgeos plugin is disabled the checkout works, but when activated it creates a 404 error.

Using the "debug wp_plugin" I got the following debug log:

Location: https://www.mydomain.co.uk/?page_id=207
Status: 302
Backtrace:
File: /var/www/wp-content/plugins/paid-memberships-pro/includes/init.php
Line: #90
Function: require_once
Arguments:
array(1) {
  [0]=>
  string(72) "/var/www/wp-content/plugins/paid-memberships-pro/preheaders/checkout.php"

[mrkellysch]

If it helps find a solution, I have updated permalinks, cleared browser cache, disabled all active plugins, excluding PMPRO and it still comes up with error 404 when I activate the badgeos plugin. I had read on other websites about hooks, and I am wondering if Badgeos hooks onto the same filters as PMPRO?

[mrkellysch]

Found out after a day of testing that it was the badge stack addon, even after deleting this plugin the damage is still done: (plugin issue here: https://github.com/opencredit/BadgeOS-BadgeStack-Add-on/issues/1). Anyone know how to remove it completely?

[mrkellysch]

Oh, and the continued error continues while BadgeOS is active (Error goes away when deactivated BadgeOS), yet BadgeOS and PMPRO worked fine in my clean install, so I know it's definately BadgeStack that has caused this error.

[brichards]

Hey @mrkellysch, this is a very, very odd bug indeed!

You can wipe out all of the data that the BadgeStack add-on introduced by doing the following:

1. Go to BadgeOS > Levels, select All, Bulk Actions > Delete
2. Go to BadgeOS > Quests, select All, Bulk Actions > Delete
3. Go to BadgeOS > Community Badges, select All, Bulk Actions > Delete
4. Go to BadgeOS > Quest Badges, select All, Bulk Actions > Delete
5. Go to BadgeOS > Achievement Types, select Level, Quest, Community Badge and Quest Badge, Bulk Actions > Delete

All the BadgeStack add-on does, as you can see from above, is register 4 new achievement types and a handful of sample achievements for each of those types. This is why deactivating it makes no difference: it only does anything during activation and then never again. This is also why deactivating BadgeOS fixes the issue: without BadgeOS active none of these custom post types exist.

We'll connect with the PMPRO team and see what we can do to identify and resolve this conflict. Thank you VERY much for the thoroughness of your reporting!

Hopefully this resolves your problem. Please report back and let us know!

[mrkellysch]

This fixed it. Thank you, big time. Can you please report here when it's fixed as I have linked to this post from many other forums,may help many others out, thanks again.

[dauidus]

It seems this issue has still not been resolved, by BadgeOS or Paid Memberships Pro. In fact, it is an incredibly simple fix - just get rid of the "Levels" Achievement Type in BadgeOS (or, rename the slug).

[tw2113]

By default, only "badges" gets created with the BadgeOS core plugin. It's the Badgestack starter addon that has a "levels" achievement type included to help get peoples feet off the ground, if I recall correctly.

[dauidus]

Oops... you are correct, sir! I'll contact that plugin's author about the issue. :-)

My apologies.

[tw2113]

All the same people as BadgeOS core.

https://wordpress.org/plugins/badgeos-badgestack-add-on/

Forgive me for sounding a bit dismissive, but I don't view it as as huge of an issue as it may seem. I'd call PMPro's need for "level" as much more integral than Badgestack's which is just quick start help. Remove the Badgestack create'd one and carry on :)

[dauidus]

I agree that its not that big of an issue. But, our small team spent a couple of hours troubleshooting this issue on a development site last night and this morning. I can't help but feel that this issue could have been completely thwarted by some small attention to detail - I'm sure we're not the only ones to come across this issue.

I realize the impossibility of trying to fix every conflict for every plugin out there. But, as BadgeOS and Paid Memberships Pro are commonly used together, it seems you'd want to help those users out by preventing wasted time troubleshooting a silly issue.

Just an opinion, though - and, as a plugin developer myself, I completely understand where you're coming from. :-)

[tw2113]

BadgeOS + PMPro isn't the issue though, it's just when the Badgestack addon comes into play, and there's no guarantee that all 3 would be used. There's also cases where someone would like to include a 'level' achievement type with some sample content, and has no plan to use PMPro.

I feel, even with the time your team spent debugging it, it's an infrequent enough conflict to just handle on the case-by-case basis as they come in.

[dauidus]

I'm completely fine with that. After all, we have used BadgeOS a lot in the past, but never with PMPro. Perhaps then, you could add a small section under the FAQ on the BadgeStack plugin's repository pages quickly explaining the problem and providing the fix. I think that would have helped us out a lot.

Either way, BadgeOS is a great plugin! Thanks for all the work you've put into it, and we look forward to seeing what comes next! :-)

[muhammadatif415]

I have found solution , just rename achievement type "level" . Every thing will work fine