Mass Update and Triggering Hooks

Please report bugs and any annoyances here. Kindly include all possible details: steps to reproduce, expected result, actual result, screenshots, ... etc.
Post Reply
G Scott
Posts: 20
Joined: 2018-02-25 00:02

Mass Update and Triggering Hooks

Post by G Scott » 2024-10-12 15:52

I am having the following problem with the Mass Update plugin:

When configuring a mass update and selecting the "Trigger update hooks" option, that particular mass update command ceases to work.

It should be noted that commands where the "Trigger update hooks" option is not selected, still work.

For clarity, I can see the command in the menu, I can select the changes to the table rows I've selected. When I press the Confirm button, the ajax request is successfully sent to the ajax-mass-update-XXXXXXX.php file and that file appears to successfully make the curl request. However, the records do not update with the previously selected value and I get no error messages.

I'm stumped. Is there any way of troubleshooting from here?

G Scott
Posts: 20
Joined: 2018-02-25 00:02

Re: Mass Update and Triggering Hooks

Post by G Scott » 2024-10-13 13:25

After some debugging, I discovered the problem was caused by my field type not being supported by the mass update plugin.

The field I was trying to do a mass update on was a multi-choice selection field, whereas the mass updater can only handle single-choice fields.
So, this was causing table_dml.php to throw a validation error.

I then changed my field type to a single drop-down list - the mass updater worked and triggered hooks.
However, a new problem appeared. I had a date field of updated records got emptied each time I did a mass update.
I believe this is because I have configured AppGini to use the following date format yyyy-mm-dd, but table_dml.php expects a different format from the date combo box - dmy?

So, I've had to make the date field a read-only field to get around this problem.

The Mass Update plugin needs better support for the different field types. Or at least, better error handling because I have spent quite a long time trying to figure out what the issue was.

Post Reply