Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember Troubleshooting › Conflict with Live Composer and eMember page protection
Tagged: Live Composer
- This topic has 4 replies, 3 voices, and was last updated 9 years, 12 months ago by Sev.
-
AuthorPosts
-
November 19, 2014 at 8:38 pm #11807SevMember
I’ve got eMember (and eStore and Affiliate) and also a WP plugin called Live Composer (which is a front end drag and drop thing for creating pages without needing to know any coding). It all works well EXCEPT I’ve found a conflict with eMember.
The pages where I am using Live Composer AND that I have protected using eMember (ie user can only access them once they have logged in) – no longer have any protection – they are open for anyone to view.
I’m just wondering if anyone had come across anything like this conflict – and if there were any suggested workarounds. Thanks!
November 19, 2014 at 10:20 pm #66905wzpModeratorOnce you’ve created a page; what happens to the protection attributes?
Does the page, when examined in the normal WP page editor, still show the protection (checkbox) attributes?
What about any protection shortcodes on the page?
November 20, 2014 at 10:47 am #66906SevMemberHi. The page in the normal WP page editor still shows the protection (checkbox) attributes – yet when viewing the page through a browser, it incorrectly shows ALL the protected content (even though not logged in).
Interestingly – when using shortcodes… the Live Composer plugin is a system based on modules (drag & drop) – and one of the modules is an HTML one. So when I drop in an HTML module on the page AND put in the eMember protection short codes ([emember_protected for=2]
Premium Member content goes here….[/emember_protected]) – then that actually works (ie the bit sandwiched between the shortcodes IS protected.
Unfortunately it is the whole page I want protected. So it seems the Live Composer plugin is somehow over-riding the eMember whole page protection. Any thoughts on a workaround? Many thanks.
November 20, 2014 at 10:04 pm #66907adminKeymasterIt seems like that plugin is overriding WordPress’s “the_content” filter output. eMember use this filter to apply protection. Please ask the developer of that plugin for more info on how they are using “the_content” filter.
November 26, 2014 at 12:37 pm #66908SevMemberHi. Thanks for the tip. The developer of the other plug-in (Live Composer) understood – and has now modified the code for me. If anyone else is intrested, here is the mod:
change was done in inc/display-functions.php on line 868:
add_filter( ‘the_content’, ‘dslc_filter_content’, 11 );
many thanks for your help. Problem sorted.
-
AuthorPosts
- You must be logged in to reply to this topic.