ALL my commercial / hidden information became open!

@deyneko,

It does not sound good man. Let’s figure it out.
Double-check how the access settings are defined on the Posts & Terms tab. Also, please explain in more detail what exactly you are protecting and how did you define access settings.

You can always contact us directly if you have any sensitive information to share.

Regards,
Vasyl

Hello,
I had the same problem the setup was reset and all page came available to user.
I setup again one by one each configuration access per page.

Thank you @gusray you confirmed the problem. For this reason I guess not only we two have the problem.
Yes, I had the same.
Shortcodes, which I put inside articles to hide or show text pieces work OK.

But after the last update all business articles were unchecked in “Front Access Settigns” ie the parameter “Limit” for “visitors” was unchecked in each publication.

It was not big problem. The big problem was that teaser messages disappeared in all publications too. I wrote these teasers in HTML. In such way a visitor could see a variant of an article but if he/she entered the site he/she would see full text or “business variant” of the article. I.e. in teaser I wrote what a visitor will see if he/she buy an access.

I tried to load backup of 2 days old database – no result!
Then I just put all commercial articles to a private status or set a password as a temporary solution.
It is easy to say… I worked near half the night fur such easy temp solution!
Now I am in a prostration and really confused… what to do?

It seems I will not go back to this plugin. I would use more natural and reliable solution for an access management.

@deyneko,

Sorry to hear about your pain. WordPress community is huge. You are free to go and find a solution that suits your needs. We can wish you only good luck with your venture.

The only reason why would the teaser message disappeared is because it most likely was defined for the API level too and because AAM 6.0.0 no longer has a separation between frontend, backend and API levels, migration script, by default, prioritized API access setting over any others as following:

array_merge(
  $normalized['backend'],  // Lowest priority
  $normalized['frontend'], // Higher priority
  $normalized['api']       // Highest priority
);

@gusray, we believe the cause was identified and more technical details are here https://forum.aamplugin.com/d/369-notice-undefined-offset-1-service-content-php-on-line-509.

Basically the problem occurs with posts and pages that had explicitly defined HIDDEN option. The fix is already in place and we are doing the final tests to make sure that all is covered properly.

It is going to be included in the official 6.0.1 release.

As for now, you would have to redefine access settings to your pages.

Thanks.
Is there any possibility of do a backup of the setups for restore when happen a problem like this?

@gusray,

The upcoming update 6.0.1 that is scheduled for tonight should fix the problem.

I’ll keep you updated if anything.

Regards,
Vasyl