[restrict] shortcode not working for us in 2.1.1

  • Resolved itofficer16mm

    (@itofficer16mm)


    4 years, 1 month ago

    I’ve reverted to 2.0 for now. We use the [restrict] shortcode on our home page (and a few other pages), to show different content to logged-in members and to those not yet logged in:

    [restrict level=”!association-member”]
    …
    [/restrict]

    [restrict level=”association-member”]
    …
    [/restrict]

    In 2.1 and 2.1.1, I found that the content within these shortcodes is never shown, neither to those matching the association-member access level, nor to those without.

    Has anyone else had this issue, or is it something specific to our environment?

Viewing 4 replies - 1 through 4 (of 4 total)

  • I’m on 2.1.1 as well, and I receive a critical error when attempting to hit the wp-admin area once the plugin is enabled.

    Plugin Author Joachim Jensen

    (@intoxstudio)

    @itofficer16mm

    Thank you for reporting this. I just manually tested the shortcode like your setup, and unfortunately I am unable to reproduce the problem.

    Can you tell me more about the access level in question?
    Are members added via a synced role? Or if you go to the Members tab, have some members expired?

    @jmomojo

    This sounds unrelated to the issue above. Can you create a new thread an provide some more details, e.g. screenshots of the error, stacktrace from log? That will make it much easier for me to help and resolve the issue.

    Apologies. I did some digging tonight, and used the WP Debug, and found that I was maxing out the memory. Adjusted that in my install, and it is working now. Thank you.

    Thread Starter itofficer16mm

    (@itofficer16mm)

    Thanks Joachim. In this case the access level in question is set up with synchronized role: Logged-in.

    One obvious option would be for me just to write my own “logged in” or “not logged in” shortcodes.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[restrict] shortcode not working for us in 2.1.1’ is closed to new replies.