Latest 5.9.4 Has changed the Customizer Settings

@subwebsites,

Alright. One step at a time. Go to AAM page and under Settings Area clear AAM cache.

Keep me updated.
Vasyl

I noticed the same problem yesterday. It looks like the publish_posts primitive capability is being ignored after the change made to AAM_Shared_Manager->mapMetaCaps. Adding publish_posts to the in_array check fixes this problem, but a real fix is probably more involved than that. Let me know if I can do anything else to help.

I just encountered this problem as well.

I updated AAM this morning, and then was unable to Publish an update via the Customizer. Save Draft was the only available option. Temporarily disabling AAM allowed me to publish the update.

I cleared AAM cache per the suggestion above but it did not make a difference.

@shnja,

Thank you for the update. That is quite odd that I’m not able to reproduce it on several sites that I have access to, however I’m definitely going to troubleshoot this more to find the root cause.

I’ll keep you guys updated.

Regards,
Vasyl

Quick update.

Apparently if you create a custom capability customize and assign it to Administrator role, everything works as expected for some custom themes.

I’m looking more into the way WordPress core maps customize capability to the actual capability. Head is spinning…

Regards,
Vasyl

• This reply was modified 5 years, 7 months ago by AAM Plugin.

I thought it might be my theme at first and started to go down that path of adding a customize capability. However, I have the same issue with the default Twenty Seventeen theme (Twenty Sixteen and Twenty Nineteen too).

@shnja,

Ok, after further investigation, I believe that the root cause was found. Please try to install this release candidate https://downloads.www.ads-software.com/plugin/advanced-access-manager.zip.

Let me know if this works.
Regards,
Vasyl

That works. Thanks for the quick response.

Was it just the fix in the Shared Manager or were all the other changes related?

@shnja,

So the answer is more complex and that was my mistake.

The customize capability that WordPress core refers to actually does not exist in default WordPress setup.

If you look deeper into the way WP core maps capabilities, the customize capability becomes edit_theme_options and that was not taken in consideration. So I’ve removed couple lines of AAM code to allow WordPress core map proper set of capabilities.

The entire process of capabilities mapping in the WordPress core is quite cumbersome however I can see underlining reasons why certain implementation decisions were made.

The fix will be included in next release after I do some testing to the new AAM feature – ability to manage access to posts by tags.

Keep me updated if anything.
Vasyl

Thanks for the explanation. I noticed the customize to edit_theme_options mapping as I was stepping through some of the WP core to figure out why an administrator couldn’t publish theme changes ??

Thanks again for the awesome plugin.

Hi. Installed this release candidate and the publish button is back to normal. Thanks. ??

Back to normal thanks!