Vasyl Martyniuk
Forum Replies Created
-
@raoulunger thank you for the report. That is an interesting issue and following the trace it is also impossible for this error to occur. I’m wondering if you may have a corrupted AAM installation.
Please try to delete the advanced-access-manager folder and reinstall it again from the official WP.org repository. It is possible that not all files got replaced during upgrade.
@treetex and @gillesgagnon we likely identified the root cause. It may be linked to the custom capability “aam_access_dashboard”. If you have it created on your site, it will trigger the default access denied redirect behavior after user logging in.
We already have a fix that is coming tonight.
@treetex and @gillesgagnon thank you for the report. Please send us exported AAM settings to support@aamplugin.com. You can export all AAM settings on the “Settings” tab. This should be a JSON file.
This way we can try to reverse engineer your setup.
@sukhrajgrewal thank you for the report. We noticed that there are several other users with similar issue that we still can’t replicate. My best guess is that this has something to do with serialization and cached admin menu fails to store in DB.
Is it possible if you can send us a dump of all the settings with prefix
aam_from the_optionstable? I’m interested to see what information is stored in your DB.Please use support@aamplugin.com email.
Thank you in advance.
@cobrains thank you for the report.
AAM Plus Package, AAM Role Hierarchy and AAM IP Check premium add-ons have been deprecated back in Nov 2023 and officially replaced with a single premium add-on in Jan 2024.
Consider either downgrading Advanced Access Manager to version 6 or downloading the latest premium add-on from your license page https://aamportal.com/license.
Also, please do not use public forum for any questions related to premium add-ons. Instead contact us through https://aamportal.com website.
Regards.
@ykato20 thank you for the report. Indeed, the spread operator was introduced in PHP 7.4 for array hydration. We are going to fix it in upcoming AAM 7.0.1 release to keep it backward compatible with PHP 5.6.0.
@doffine absolutely. It got trimmed during merge of
nextbranch tomaster. We already fixed in the upcoming 7.0.1 release.@vincentsq likely WP.org forum already “sealed” your message and it is not longer allowed to be edited. Bummer.
@vincentsq please edit your message and remove mentioning of your website name in the file path. That is not advised to disclose any info about your server folder structure.
@patrick1994 thank you for the additional feedback. Indeed, like any plugin dev shop – we go with the latest WordPress version. It would be too time consuming to do regression tests against older WP versions.
The issue will be fixed in the next minor release. In the meantime you can either downgrade to AAM 6 or upgrade your WP instance to at least 6.7.0.
@bsmolyanov please download the premium add-on from your license page and reinstall it. The zip archive was corrupted. It is fixed by now.
sorry for the inconvenience.
@presscat2015 you are spot on. Actually, the
wp_is_rest_endpointrequires 6.5.0. We are going to fix this issue in the next minor release. In the meantime you can downgrade to AAM 6 or upgrade your WordPress instance to at least 6.5.0.@freqtwo thank you for the report. Please note that we do not monitor WordPress.org forum.
I understand your problem, however, I can’t classify it as bug. It may sound like pointing fingers, but what you are experiencing is due to the way WooCommerce dev team decided to implement their functionality.
When
aam_show_admin_noticescapability is created, AAM checks if logged in user has it assigned and if not, it simply removes all callback functions registered for the following WordPress core hooks:- admin_notices
- network_admin_notices
- user_admin_notices
All above hooks are designed to be exclusively used to display admin notifications. If plugin developer’s chose to rely on these hooks to power functionality that goes beyond original design – there is nothing we can do on our end besides advising either not using AAM custom capability
aam_show_admin_noticesor creating access policy that conditionally assign this capability based on currently viewed admin screen.Forum: Plugins
In reply to: [Advanced Access Manager – Access Governance for WordPress] Not Working@edge24ema thank you for the additional details. However, the Admin Menu service is working as expected on our end and this is a fundamental functionality. If it was not working properly, we would be getting tons of support requests from our existing customer base.
It is likely you may have some sort of database caching that aggressively caches DB queries or you may have some other plugin that removes AAM registered hooks. Try to purge your cache and if this does not help, please try to deactivate all plugins and switch to default WP theme to find out what causes the conflict.