Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember General Questions › Protection and Custom Post Types
- This topic has 7 replies, 5 voices, and was last updated 8 years, 11 months ago by
admin.
-
AuthorPosts
-
February 5, 2011 at 7:06 am #2648
cflyrun
MemberCan custom post types be protected through the settings configurations, or must they be protected by each individual page/post?
Also, can comments on protected pages be restricted as viewable only by those with subscriptions to view particular pages? I currently have a member site, looking to switch to eMember, and currently use a shortcode on each custom post type I want to restrict access to, and have a special template type for those custom posts that implements a line of PHP code so that only those logged in can view comments.
Thanks in advance,
Daisy
February 6, 2011 at 2:58 am #28753amin007
ParticipantNope, custom post types can only be protected individually from the “Manage Content Protection” menu.
By default comments on a protected post or page is also protected. However, you can choose to individually protect the comments for different membership levels (similar to protecting individual posts and pages).
February 6, 2011 at 9:16 pm #28754cflyrun
MemberI’m not sure if this answers my question – are you saying that they *can* be protected individually from the Admin section of the eMember plugin?
Currently I have templates set up for custom post types with php code versions of the shortcodes used to protect parts of pages (I’m using PHPurchase and am trying desperately to get away from them since they switched).
I guess I’ll just play around with it and see…
Daisy
February 7, 2011 at 1:19 am #28755Ivy
MemberHi Daisy, You need to use the “Manage Content Protection” menu to protect the custom post types.
Membership level > Manage Content Protection (Tab at the top of the page).
September 17, 2015 at 9:00 pm #28756rrestani
MemberI have the same issue. I have gone to membership level > Manage Content Protection and custom post type are not protected.
September 17, 2015 at 11:47 pm #28757admin
KeymasterIs this custom post triggering the “the_content” filter like all WordPress posts and pages do? Some developers develop custom post type that doesn’t trigger the standard WordPress filter and action hooks. Or they put the content outside WordPress “the_content” area.
Our plugin can’t hook into that content if it doesn’t follow WordPress’s architecture for a post or page.
September 18, 2015 at 4:12 am #28758rrestani
MemberI don’t know what you mean by trigger the “the_content” filter but when I look at the code in chrome it is inside the content area like a post or page would be.
soundtoenlighten.com
September 18, 2015 at 6:14 am #28759admin
Keymaster“the_content” is a filter that needs to be wrapped around the custom post content. If you ask the developer of that plugin/theme, he will understand and be able to answer the question.
-
AuthorPosts
- You must be logged in to reply to this topic.