We've upgraded to amember 4 and it basically looks like our protection shortcodes are being ignored entirely. We have the wordpress plugin installed and activated. We've assumed that if you wrap content with [am4show....] content [/am4show], that's all you have to do. But, now we're wondering if you also have to mirror those same protections in the amember admin under Protect Content > Integrations? In other words, we would have to add a new protection record/config for each and every combination of wordpress usergroup and amember product. Please tell me this isn't true? Shouldn't the shortcode be enough? If the member doesn't "have" the particular products we specify in the attributes of the am4show shortcode, shouldn't they be hidden without any extra work in the "Protect Content" area of amember?
here's an example of the kind of code we're looking at in a piece of content... Where "g10" is a membership group and "p287" is a specific product We're assuming that if the user has a product in group10 OR has the specific product, he will see the download link. Here we're assuming that if the user has neither group product or the specific product, they will see the buy button... And finally, if the user has the specific product, but does not have the membership product in group10, we show them why it's the their benefit to join with a file we pull in from the upgrade shortcode. We've removed that shortcode to make sure it's not interfering and see no change... Thanks for your help.
[am4show not_have='g10;p287;' ] Show buy button [/am4show] Unfortunately, this will only show if the user has an active account with amember, and not with those products. Your gonna need a 2nd set of code for non-logged in member. [am4show notactive=0]content[/am4show] David
okay - I understand that, but this is the bigger issue. On individual blog posts, we want to protect some content and reveal other content as described. ALL shortcodes are being ignored or ALL are being assigned..
Sounds like something is not configured correctly. At this point I would suggest you submit a ticket and let aMember staff look at your installation.