aporter

Hi,

We will be implementing 7G rules, this is currently being prioritised and will hopefully make it into the next full release.

We normally release monthly, but if unexpected issues come up they could be more frequently e.g smaller bug fix releases.

We will also be adding 8G at a later date.

Best Wishes,

Ashley

Hi,

Can you check what events are filling it?

Others have complained about this and for them it was filling up with failed login attempts, which means their sites were being brute forced.

Now you can either look into preventing them brute force attempts which will stop the logging.

Or if you don’t care about the attempts you can either ignore them and change the automatic cleanup time, or prevent them from logging at all.

By default logs older than 90 days are removed, you can change that time by adding this constant to your wp-config:

define(‘AIOWPSEC_PURGE_AUDIT_LOGS_AFTER_DAYS’, 10);

That will remove logs older than 10 days.

Or if you don’t want to log some or all events you can use the following filter:

‘aios_audit_log_record_event’

Best Wishes,

Ashley

Hi,

Sorry that the message is causing confusion.

In the past we have had users who setup some options in the plugin, but them options did not work as they may not have been on a server that supported .htaccess

But they had accidentally set them options up to block them selves

But as the options did not work they didn’t notice anything and assumed they were being protected.

When we then ported them rules to the PHP firewall and they suddenly started working, they then got locked out and didn’t know how to get back in.

So we started disabling the rules we updated, so that users could login, double check the settings wouldn’t suddenly lock them out and then turn the rules back on.

So to answer your questions you had some of them rules turned on, they have now been turned off.

You can view the rules in the Firewall section of the plugin.

The button on the notice will turn them back on for you.

Hopefully that clears it up for you, if not let me know and I can help.

Best Wishes,

Ashley

Hi,

The above is not an error message but a notice.

In the past we have had users who setup some options in the plugin, but them options did not work as they may not have been on a server that supported .htaccess

But they had accidentally set them options up to block them selves

But as the options did not work they didn’t notice anything and assumed they were being protected.

When we then ported them rules to the PHP firewall and they suddenly started working, they then got locked out and didn’t know how to get back in.

So we started disabling the rules we updated, so that users could login, double check the settings wouldn’t suddenly lock them out and then turn the rules back on.

Hopefully that clears it up for you, if not let me know and I can help.

Best Wishes,

Ashley

Hi,

If your having a problem with the plugin then please open a support request and our support team are more than happy to help.

If the audit log is taking up a huge amount of space it’s likely because of failed login attempts and is something you may want to look at preventing.

If you don’t want to resolve that, then you can use the filter “aios_audit_log_record_event” to prevent all logging to the audit log.

Note doing that will prevent some features and future features from working.

Best Wishes,

Ashley

Oi,

Se você tiver algum problema com o plug-in, abra uma solicita??o de suporte e nossa equipe de suporte ficará feliz em ajudar.

Se o log de auditoria estiver ocupando uma quantidade enorme de espa?o, provavelmente é devido a tentativas de login com falha e é algo que você pode querer evitar.

Se você n?o quiser resolver isso, poderá usar o filtro “aios_audit_log_record_event” para impedir todos os logs no log de auditoria.

Observe que isso impedirá que alguns recursos e recursos futuros funcionem.

Muitas felicidades,

Ashley

Hi,

AIOS version 5.2.2 was just released this should resolve your issue.

Best Wishes,

Ashley

Hi,

AIOS version 5.2.2 was just released this should resolve your issue.

Best Wishes,

Ashley

Hi,

AIOS version 5.2.2 was just released this should resolve your issue.

Best Wishes,

Ashley

Hi Manuel,

Version 5.2.2 is going through testing right now so once everything has passed it will be released.

Rough ETA some time this week or next.

Best Wishes,

Ashley

Hi,

You can download old copies of the plugin here:

https://www.ads-software.com/plugins/all-in-one-wp-security-and-firewall/advanced/

You should install 5.1.8, as 5.1.9 introduced a security bug so it’s not recommended that you use that version.

Best Wishes,

Ashley

Hi,

Looking at the TFA admin menu I can see this one displays via the role “read”.

The reason being this needs to be available to non admins so they can setup TFA for their accounts.

If you don’t use TFA or you don’t want some roles to use it, you can go into the TFA settings:

WP Security -> settings -> Two Factor Auth

You can then use the “Make two factor authentication available” section to hide this menu for each role you disable.

Best Wishes,

Ashley

Hi,

If you want to restrict the menu to one role you can use the following define in your wp-config.php:

define(‘AIOWPSEC_MANAGEMENT_PERMISSION’, ‘YOUR ROLE HERE’);

When does the code your using above run? is it via a filter/action

Best Wishes,

Ashley

Hi,

Under what conditions do you want to hide the menu?

Best Wishes,

Ashley

Hi,

Sorry about the delay.

This has been fixed in our development version which can be downloaded here:

https://gofile.io/d/Qvn1J1

It will then be available in the next release.

Best Wishes,

Ashley

Hi Both,

Sorry about the delay.

This has been fixed in our development version which can be downloaded here:

https://gofile.io/d/Qvn1J1

It will then be available in the next release.

Best Wishes,

Ashley