Bug dbtech_security_watcher_action.account_lock action not phrased

[SeToY]

Hi there,

 

[DragonByte Technologies]

Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future release (4.3.3).

Change log:

Corrected the log phrase for locked accounts (not retroactive)

 

[Fillip H.]

The change isn't retroactive, as it's not possible to retroactively determine whether the lock was an admin lock or user lock.

You can manually correct this by going to the xf_dbtech_security_watcher_log database table, find the action column and change the "account_lock" value to either admin_lock_user or lock_user depending on which lock type you configured.

 

[DragonByte Technologies]

Hello @SeToY,

We hope your ticket regarding DragonByte Security has been addressed to your satisfaction. This ticket has now been scheduled to be closed.

If your ticket has not been resolved, you can reply to this thread at any point in the next 7 days in order to reopen the ticket, afterwards this thread will be closed.

Please do not reply to this thread if your ticket has been resolved.

Thank you.


- DragonByte Technologies, Ltd.

 

[DragonByte Technologies]

Hello @SeToY,

As we have not heard back from you, your ticket regarding DragonByte Security has now been closed.

If your ticket has not been resolved, please feel free to start a new support ticket and link back to this ticket.

If you have time, please leave a review on XenForo.com's Resource Manager.

Thank you.


- DragonByte Technologies, Ltd.