Closed gamesbook closed 9 years ago
This seems ideal. Error checking isn't so great on this project. I'd be happy to review any pull requests but I don't really have time to develop a fix right now.
It should probably start a database transaction, commit if successful, revert and show a message if unsuccessful.
we just installed version 2.2. The errors seem to be trapped now. The only remaining change would be, I think, to create a different error message for the case when the changes are NOT made successfully. At the moment, success and lack-of-success are both reported the same way.
If a user makes a changes that results in mass-edit creating one or more records that have duplicate entries, then an error is thrown that is not handled.
Is it possible that mass-edit can catch these and rather return a set of messages/warnings as to why the records in question were not altered?