bishop81

Has there been any movement on this? I have a client that is experiencing the same problem.

I know this is marked as resolved, and my issue was slightly different, but I thought I’d let you know that the latest Posts and Pages update fixed my issue.

Thanks!

Ok, I’ll read those steps carefully a few times to try and understand how it goes. The real problem is that inheritance was working perfectly at one time. I didn’t change the role permissions or anything, I only performed plugin updates. Now it doesn’t work.

I’ve even tried creating a new role and testing it, but that didn’t work. The page-specific permissions just wouldn’t override the “Role > Page” default permissions. Whether I had default locked down and the page open, or had default open and the page locked down. Nothing I did on the page level was actually being applied.

The user has the same settings as the role. Individual page settings are being inherited when they aren’t supposed to.

The settings are for the role. I’ll check the user now, but I was assuming that changing a user’s role would at least reset any user defined settings (of which we never set anyway).

For the Root > Pages, I have it set:
Backend
List > checked
Add > checked
Edit > checked
Delete > checked

For the Individual Page that should be available:
Backend
List > unchecked
Edit > unchecked

I’ve even tried unchecking things under the main Page settings, and then restricting individual pages, but that doesn’t work for me either.

I’m using version 3.0.7 of the plugin, and have the AAM Plus Package installed.

This was working great until recently. One of the recent updates broke this for me.

I’m having this same problem. When I restrict access to all pages and then allow access to a specific page, that page never shows up for the user to edit. When I allow access to all pages and try to restrict any individual pages, they are still available to edit.

It seems that the ability to act on individual pages is broken since the latest updates.

You’ll find this text in your index.php file:

<?php eval(base64_decode(ZXZhbCh......)); ?>

There’s a bunch more text in that base64_decode line, by the way. I’ve removed it because somebody moderated my post to remove the whole thing. I think it’s important to actually know what to look for and remove, however.

Delete it and upload the clean file to your server.

Sorry for causing somebody to edit my post, the actual “hack code” doesn’t do anything if it isn’t in your file. Also, it’s designed for one simple purpose, but I haven’t figured out exactly how it’s supposed to serve that purpose. Somehow it’s trying to get traffic to some affiliate page or something. Now, I won’t post that link, but it’s listed in the OP.