Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter eLeXeM

    (@elexem)

    Hey, Vasyl; toyed with that some more @ http://wp11007907.server-he.de/lrdproto/blog/2018/07/29/test-fuer-aam-shortcode-s/ and noticed a li’l detail that tells us that not the_entire_ short-code-rendering of AAM has difficulties. If you have another look you will notice that at least the line
    [aam hide="visitor"]a message to <b>HIDE from visitor</b>s.<br />[/aam]
    gets actioned properly (i.e. hidden away from not-logged-in-users) – so something must be disturbing the other aam {dofor} “role” couplings somehow, but not your entire shortcode provision.
    I think that is good news, no?

    Let’s hone in on this 🙂
    P.S. I also attempted if the shortcodes looks for the roles “nice name” rather than the systemic name 🙂 but that wasn’ the culprit either.

    Cheers – LX

    Plugin Author AAM Plugin

    (@vasyltech)

    Hi @elexem,

    Thank you for the details. I’m publishing a new AAM version tonight that has a bug fix for the AAM shortcode that possibly is related to your issue.

    Feel free to contact me directly if anything.

    Regards,
    Vasyl

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Can’t seem to get shortcode/s to work?’ is closed to new replies.