eMember – unable to protect custom post types

[nhchui]

I have emember installed and it does not lockdown custom post types. There is no other plugin conflict, because I tried locking down a page and that works fine. The lockdown page also works fine, but I need to have different passwords for different posts. I tried to set the protection in the manage content protection section already.

Is there a way to make eMember work with custom post types or have multiple lockdown pages that use separate passwords?

[admin]

eMember can protect custom post types but you can’t use different passwords for different pages. Read the following two posts to understand how content is protected using membership levels in eMember:

http://www.tipsandtricks-hq.com/wordpress-membership/how-to-add-a-membership-level-in-wp-emember-13

How to Manage Content Protection in WP eMember

Can you post a link to one of these custom post types post that you have protected in eMember’s manage content protection area? What version of eMember are you using?

[nhchui]

I’m using eMember version 8.3.8

[http://www.hellograhamhill.com] all the items on there are the same type of custom post type, but only a few of those need password protection.

I couldn’t even get any of them to be protected using membership levels. The only way I have been able to get them protected at all was through using the lockdown page.

[admin]

Thank you. I need to see if your theme or the plugin that is handling this custom post is properly calling the WordPress’s content filter on these custom post types. I sent you an email to get access to the site so I can check some details.

If the content filter is not getting fired then that is something you will need to fix in that plugin. There is a workaround that you can use to still protect these custom posts. Use the following feature of eMember:

http://www.tipsandtricks-hq.com/wordpress-membership/wp-emember-protection-how-to-enable-site-wide-protection-342

You can also use a URL pattern to protect all the pages that contain that pattern. For example: in your case using “/projects/” in the specific page lockdown field will protect all the custom posts that are projects.

[wpCommerce]

It turns out that these custom posts (the ones you are using) are not firing WordPress’s “the_content” filter at all. A custom post type must use WordPress’s “the_content” filter to make it work properly with other plugins. This is why the standard post content protection is not working.

You can use the workaround mentioned by the admin.

[Author]

Posts