![]() ![]() Get the module on GitHub at #magento #magento2 #php #ecommerce #opensource #github This is an essential tool for online store owners, as it provides complete transparency and control over backend activities. If you find that a change was made in error, you can quickly restore the previous state and undo any undesired modifications. Revert modifications: One of the standout features of the Magento 2 Admin Activity module is the ability to revert changes made by admin users. For example, if an admin edits a product's price, the system will log the change and show you the exact field and value updated. Track fields that have been changed: With this module, you can control and monitor any modifications made from the backend. Monitor page visit history: The Admin Activity module also keeps track of each admin's page visit history, giving you insights into which parts of your website they've accessed, how often, and when. This feature enables you to see who has been trying to access your store's backend without proper authorization, along with their IP address and login information. Record failed login attempts: Security is a top priority for any online store, and the Magento 2 Admin Activity module helps you maintain it by logging failed admin login attempts. It also allows you to keep tabs on mass updates made by multiple administrators simultaneously. Track every admin activity: With this module, you can track all actions performed by your store admins, such as adding, editing, deleting, printing, and viewing records. So, how does the Magento 2 Admin Activity module work? Although the original repository has been archived, this long-term fork continues to provide the same valuable features and welcomes improvements through pull requests. The primary goal of the module is to ensure that you have a clear understanding of what's happening in your store's admin area. This Magento 2 module is designed to help you easily track and monitor various activities within your online store's backend. That's where Magento 2 Admin Activity module comes in. You may have multiple admins with different levels of access, and it's crucial to know who made specific changes and when. One of the challenges in managing an online store is to keep an eye on the activities performed by various admin accounts. Get the module on GitHub at #magento #magento2 #php #opensource #rabbitmq #github Requeue the failed messages to their origin queue Admin grid to manage the messages with the retry limit reached The message is dropped because its queue exceeded a length limit The message expires due to per-message TTL or The message is negatively acknowledged by a consumer using basic.reject or basic.nack with requeue parameter set to false. Messages from a queue can be "dead-lettered" (or republished) to an exchange if any of the following events happen: If not, the message goes through a waiting period and is then returned for another try at processing. If the limit is reached, the message gets stored in a special table for manual handling later on. This module changes that by introducing a retry limit. When using Magento's default behavior, if there's an error during a certain process, the message gets discarded and won't be tried again. This uses the "dead letter exchange" feature of RabbitMQ to retry failed attempts. The Magento 2 Message Queue Retry module (which describes exactly what it does - why don't all devs name their modules like this? □). Ever want to retry a message queue item in Magento? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |