lcollong
FabriKant d'applications web
Hi,
This is related to the new log form plugin. As I've explained here : https://fabrikar.com/forums/index.php?threads/new-logging-function.51827/#post-277312 , it is sensitive to the rank it appears in the plugin's list.
For example, if you have a form with no plugin. You add a log plugin with default setup. Then you add an upsert plugin to this same form (rank #2 so).
If you do something with the form (edit or create for example), the log plugin is triggered (rows added in the fabrik_log table) but the upsert is never triggered.
Then, if you add again a log plugin with same parameters to the form's plugin list and finally delete the first one, you'll have the upsert in rank #1 and the log in rank #2. In this situation, both the upsert and the log plugin will be triggered.
The idea could be to always put the log plugin in last position. But if you have a redirect plugin or a manual redirect in an onAfterProcess one, the log'one would never be triggered.
This is related to the new log form plugin. As I've explained here : https://fabrikar.com/forums/index.php?threads/new-logging-function.51827/#post-277312 , it is sensitive to the rank it appears in the plugin's list.
For example, if you have a form with no plugin. You add a log plugin with default setup. Then you add an upsert plugin to this same form (rank #2 so).
If you do something with the form (edit or create for example), the log plugin is triggered (rows added in the fabrik_log table) but the upsert is never triggered.
Then, if you add again a log plugin with same parameters to the form's plugin list and finally delete the first one, you'll have the upsert in rank #1 and the log in rank #2. In this situation, both the upsert and the log plugin will be triggered.
The idea could be to always put the log plugin in last position. But if you have a redirect plugin or a manual redirect in an onAfterProcess one, the log'one would never be triggered.