- This topic has 1 reply, 2 voices, and was last updated 8 years, 9 months ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 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 › apr/eMember – working with Visual Composer plugin
Tagged: Visual Composer
Hi, we’re using the Visual Composer page building plugin [https://vc.wpbakery.com/] on our site and we’re adding wp eMember as well.
It’s easy to add the eMember shortcodes to protect content inside simple text blocks. But it’s not easy to protect any other elements I might want to add. It is possible to protect another element, but it involves rather annoying workaround. I have to go back to the Classic Mode editor, find the element I want to protect and add the emember shortcode there. That turns the element I’m protecting into a text block, so if I want to go in and edit it’s settings, I have to go back to classic mode, remove the emember shortcodes, switch back to the visual editor, make the changes, switch back to classic editor and then reinsert the emember shortcodes.
I’ve tried adding the opening shortcode in one text block before the content I wish to protect and then put the closing short tag in another text block after the content, but it doesn’t work.
Ideally, I’d be able to do that or even have an extra tab on the controls for the row element so I could easily set up permissions on the row level.
Does anyone know of another workaround for this situation?
Thanks.
You should be able to protect everything because that section protection is just like any standard WordPress shortcode.
https://codex.wordpress.org/Shortcode_API
Does that plugin parse the WordPress shortcodes correctly on all the elements that it offers? You should ask the developer of that plugin why a standard simple WordPress filtering is not working on certain elements.
We can add specical code (if that plugin needs it for shortcode rendering). That developer needs to tell us what special code is required for WordPress shortcode to work in his plugin’s content.