Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author thomstark

    (@thomstark)

    Hi. Please upgrade to Eyes Only version 1.7.1 and let us know if this resolves your issue. Thank you!

    Anonymous User 10899148

    (@anonymized-10899148)

    Hello,

    I might have time to help you, please send me the latest version of the “Front-end Builder” plugin.

    halfcj

    (@halfcj)

    When user registers when attempting to access ‘hidden’ content, they get a message that says they do not have permission to update WooCommerce!? (which isn’t even activated, just included in the theme)

    Then when they go back to home and then navigate to access the hidden page again (once logged in) they then are told they do not have permission to view this page, because they are directed to https://~/wp-admin/profile.php, not https://~.com/hidden-page

    Does that make sense?

    Can you tell me what is happening. I cannot see how to resolve this.

    Plugin Author thomstark

    (@thomstark)

    No it doesn’t make sense, because you haven’t stated what your problem has to do with Eyes Only.

    I am trying to hide a button with eyes only. But if put the shortcode in two separate text elements before/after the button, it does not work. If I recreate the button in a text/html element then the frontend builder breaks and I screws up my layout, and makes it so I can’t move elements or delete elements after the eyes only code

    Plugin Author thomstark

    (@thomstark)

    This is not a conflict. This is a limitation of WordPress’s shortcode functionality. You can’t separate an opening and closing shortcode tag in two separate fields that each render shortcode output separately.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Conflict with "Frontend Builder" plugin’ is closed to new replies.