When creating a new config, we can set all its information before hitting the save (Update) button and only at that moment will it be saved.
If setting a branding image before the configuration has ever been saved, an HTTP 500 is raised.
This happens because we:
don't include config owner in Form (so it cannot be changed)
save the the config without committing to DB first
Then add the owner to the config instance
Then save to DB
The file validation mechanism (step2) triggers a save to DB which failed because there's no owner at that time
When creating a new config, we can set all its information before hitting the save (Update) button and only at that moment will it be saved. If setting a branding image before the configuration has ever been saved, an HTTP 500 is raised.
This happens because we:
The file validation mechanism (step2) triggers a save to DB which failed because there's no owner at that time