Ben Thomson

@LukeTowers are we still going to implement ordering / prioritising with that? I can't quite recall the reason I did this PR (might've had something to do with the backend...

Re-opening per https://github.com/wintercms/winter/pull/905#issuecomment-1552354735.

@msimkunas should this perhaps only occur when in production mode?

@msimkunas this may have an effect on client-side error reporting. Immediately, I can think this might affect the Debugbar plugin, because it has some special handling for exceptions thrown in...

@msimkunas sounds good to me. :)

@diegoflorez this is partially intended, based on the behavior of the previous AJAX framework. Validation errors in the PHP side are returned with a response code of HTTP 406 Not...

Sure, we could use the [PHP SVG](https://github.com/meyfa/php-svg) library. Would be very simple to have it generate text on the fly from what I can see.

I've taken a look into this today, and it might be more difficult than first thought. There's two issues at play: ### Config repository Our [Config Repository](https://github.com/wintercms/storm/blob/develop/src/Config/Repository.php) class is based...

I swear I had fixed this at one point in the October days...

Hi @phpiando - thanks for submitting this PR. My understanding is that this trait already checks if revisionable fields have been changed or not from this line: https://github.com/wintercms/storm/blob/b5f971f9749911ea4ac080c4c4c5123ac87ba2a1/src/Database/Traits/Revisionable.php#L75. The `getDirty()`...