• use a std. ez install: default sorting of children for class image is path_string/ascending
• use multiupload to upload an image
• the image will have its child sorting set to published/descending
• no workflow trigger is fired about sorting

The strange thing is that the sort order is not changed via an explicit call - it is probably a side effect of the usage of the low-level ez4 API which is done by multiupload.

By default images can not have children, so the bug is not having any effect on default installations. But we can imagine cases where the image class is set up to have children