Triggers found by SWAT report
In Magento 2, for all changes in existing entities to properly reflect in the environment, a reindex is required. Specific events that enforce the reindexing process after changes in database tables are called triggers.
Amasty modules do not add their own triggers to Magento. If using triggers is required by a module’s logic, it utilizes Magento Materialized View/Mview native functionality. That way, the triggers are created by Magento itself.
This solution is described in the official Magento documentation as the optimal way of handling such cases and is widely used in Magento’s own code.
Related Articles
Can I send you the files of my website to investigate the issue instead of giving SSH access?
We can work with customer instances by deploying them in our local environment, so you can send us the archived files of your root Magento directory and database the following way: Step 1. Go to your root Magento directory via CLI and run this ...LESS issue on static content deploy. How to resolve it?
The below error when running a bin/magento setup:static-content:deploy command implies that the child theme is not utilizing the Magento LESS to CSS compilation: Compilation from source: ...
Announcements
⚡ Have you enlarged the functionality of the Amasty extension with your own code? Share your improvements with us!
At Amasty, we understand that some of our clients require customized features to perfectly align the extension with their business needs. If you have developed new functionality within an Amasty module and would like to share it, please submit a ticket