- This topic has 3 replies, 2 voices, and was last updated 13 years, 5 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eMember › eMember V6.5.5 w/ CouponPress
hello,
I just purchased eMember to use with CouponPress for member management. the theme and content is already complete. just adding member content management. when doing some test, it was found that
– some pages are not being protected, but some are being protected correctly.
– all category pages are not being protected correctly
– posts are not being protected correctly
*** tested on a free trial blocking all the pages, categories, posts, & comments
*** tested on general protection blocking selected pages, & selected categories
please advise, thank you
*Update
– found out that the pages that are not working properly are associated with a “template page” (or page attributes)
– if i switch the template to a “default page” then the protection works correctly
– now i need help to be able to protect the pages associated with a “template page” (or page attributes)
– hope this helps
Protection on custom page template should also work. Can you please post a link to the page in question? What browser are you using for testing?
Just to let you know that you can also use section protection to protect the content on your custom page template pages. Section protection does not separate between template page or normal page so it will work regardless. This page explains how to use section protection:
http://www.tipsandtricks-hq.com/wordpress-membership/how-to-protect-a-section-of-a-post-or-page-88
I am using safari. one apple laptop to modify, and one laptop to view the changes. i will try again tonight. i just hope it is now my couponpress theme that is preventing these the protections… you think it is a possibility?
thanks – alvin
On our test server I tested the protection on a custom page template (explained on this article) and it works fine:
Given that the custom page template is not missing any call to necessary/critical WordPress hooks then I see no reason for it not to work.