Conflict with Page Builder by SiteOrigin

Hi,

I understand that you may not consider this to be a problem with Paid Memberships Pro as using a widget to create the main content is unusual.

I’m thinking of manually changing the priority of the “add_filter(‘the_content’…” call so that I can use the two plugins together. Can you tell me if there is some problem that was resolved by using priority 5 for the call so that I can see if that will cause any problems with the way we’re using it?

I tried looking at the file history for the content.php file on GitHub, but the oldest version already has the priority set to 5, so I’m not able to see why it was set to 5.

I tried searching through the change log, but didn’t see anything that would seem to be a problem if I change the priority:
Searched for “priority”:
= 1.3.19 =
* Updated the priority of a few actions/hooks so the “besecure” https stuff gets run as soon as possible. Before it was possible that some URLs could be written out with http: on an HTTPS page before PMPro had a chance to fix things. You should have fewer SSL errors on the checkout page to deal with now.

Searched for “the_content”:
= 1.5.2 =
* the_content filter removes any class=”more-link” class from the content if showing an excerpt.

= 1.4 =
* Now applying “the_content” filters on the confirmation message on the confirmation page. e.g. wpautop will be run on the text to automatically add paragraphs.

= 1.3.4 =
* Changed the membership shortcode to apply the_content filters to the return value instead of just wpautop. This allows shortcodes within that shortcode and other filters to be run on the content. (Let me know if issues arrise from this.)

Thanks,
Joe

It occurs to me that because this isn’t a bug, it’s just cluttering up this forum.

I’m mark it resolved and move on.

Hi, Joe. Thanks for posting this and working through. Please note that our lack of a response here doesn’t mean we don’t care. We’re just under heavy load and can’t be as responsive as we’d like.

I think in general, we wanted to run the PMPro filter code on the content as soon as possible since we can potentially remove shortcodes and other things that won’t even have to run after we filter the code. So the theory is lock the content down first, then let people do whatever they want to with the locked down content. So we don’t want to filter out the share link added by a plugin.

However, we would want to filter out the widgets/etc added by this builder plugin.

I am not sure we can change the priority overall. Some people might be relying on that. I can think about it.

But you can change those priorities up on your own site using some custom code… so you don’t have to edit the specific plugins. So

function fix_pmpro_pb_priorities()
{
    remove_filter('the_content', 'pmpro_membership_content_filter', 5);
    add_filter('the_content', 'pmpro_membership_content_filter', 11);
}
add_action('init', 'fix_pmpro_pb_priorities', 20);

Or you can add/remove other filters to update them.

Let me know if this makes sense and helps you.

Thanks for explaining the reason for the early priority, makes great sense.

Updating the priority via an action is a great option. It may be a little slower to let the shortcodes and such run, but my client will be happy that they can use widgets in the content area without messing with the plugin code each time it’s updated.