crashed backend

Hi @tasha34

Thank you for reaching out to Paid Memberships Pro.

I watched your video and I am a little unclear what’s happening here. To confirm, you installed Paid Memberships Pro and then deactivated it and the posts are still not showing on the frontend or was the issue only happening when you installed Paid Memberships Pro?

There is an option to hide posts from non-members inside the Advanced settings of Paid Memberships Pro which can be set to let non-members see restricted posts on archive pages by adjusting the “Filter searches and archives?” option in the Advanced settings of Paid Memberships Pro.

So what occurred was everytime I tried to access something in the backend like pages, post, plug-ins, mailpoet… It would redirect over and over again until it timed out or it would redirect me to my site with a page that says “page not found”. I tried EVERYTHING in the world to make this work for me, nothing worked. I troubled shooted and shut down my Divi in which the plugin performed by not redirecting me anymore. I use a redirection plugin already and shut it off as I was installing PMPro just in case. I read over a days worth of documentation from PMPro to Divi to no avail. I eventually had to reinstate my site from a backup I did just in case from Jetpack.
I really wanted to use the plugin because of it’s integration with Divi and Mailpoet. But it doesn’t seem to be working for me to even try it out, and it is a nightmare to trade membership plugins if something happens. Thanks for reaching out to me, I know your time is valuable and only paying members get your main attention as it should be. So I GREATLY appreciate you responding in the time frame you have.

Thanks for letting me know, this issue sounds to be site specific. I haven’t been able to replicate this with Divi and MailPoet.

I recommend in trying Paid Memberships Pro on a staging environment first (on a clean install) and activate your other plugins to see if there are any conflicts.

We integrate with both Divi and MailPoet and don’t do any redirections in particular within the WordPress dashboard itself. We leverage default capability check functions that WordPress provides.

If you can provide me with exact steps to replicate this, I’d be more than happy to try this out as I haven’t been able to replicate this issue.

I do recommend reaching out to a local WordPress developer to take a look into this further as it seems to be a specific issue to your site. Thank you for understanding.