Home>Support>Plugin Conflict That Results in 502 Error

Plugin Conflict That Results in 502 Error

Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

I have the SiteOrigin Page Builder plugin setup on a clients site, as well as the Paid Memberships Pro plugin. About a week ago I started getting a 502 error whenever a customer tried to signup for a class using Paid Memberships Pro.

I discovered that if I removed the

add_filter( 'the_content', 'siteorigin_panels_filter_content' );
line from /plugins/siteorigin-panels/siteorigin-panels.php file the page would load correctly and the 502 error was gone.

I realized that it was conflicting with the

add_filter('the_content', 'pmpro_membership_content_filter', 5);
line in the Paid Memberships Pro plugin file.

I’ve tried setting the order as some support pages have suggested (adding a number at the end, as the 5 above is a default) but with no luck.

The page is https://seejakeandjanetrain.com/sign-in-sign-up/ and the issue is with all of the “select” buttons on the right side. Any help would be greatly appreciated.

Thank you.

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 8 years, 5 months ago Alex S
    Hi, I Work Here

    Hi Josh,

    So, to clarify, have you tried increasing the priority of siteorigin_panels_filter_content to be lower than pmpro_membership_content_filter? If not, try changing the 5 to 11 (SiteOrigin Page Builder uses the default filter priority which is 10).

  2. 8 years, 5 months ago Josh Eisenberg

    Alex,

    I did try changing the priority a few different ways, with no luck.

    I was able to solve the issue on my own. What I ended up doing was adding

    remove_filter( 'the_content', 'siteorigin_panels_filter_content' );

    in a newly created page template, and applying that template only to the pages that had the 502 error, which luckily weren’t using Page Builder.

    I’ll close this thread. I just wanted to share my solution in case anyone else needs it.

    Thanks!

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More