[Idea] Maybe let site owners know when new image sizes get introduced in an upgrade.

[abivia]

The problem

Upgrading to 9.1.0 went fine, along with an upgrade to Hummingbird 2.0, except the them now looks for image sizes default_lg and default_sm (replacing default_s).
In turn, the generated page has a srcset of the form " 216w, {the medium image}, 336w", thus causing alt text to appear due to the missing images.

This is the result of 0cdb6d45c47b7c9197bbe469778ad6581a4c2dde

The solution

Ideally, the upgrade to 9.1 adds the new image sizes. Less ideally, the store admin is warned that they need to add the new formats to the image settings.

Additional context

No response

Do you plan to work on this subject?

• I'm willing to contribute a formal specification.
• I'm willing to provide any wireframes or design assets required for this feature.
• I'm willing to submit a Pull Request that implements this feature.
• I'm willing to help verify that the implemented feature works as intended and produces no unintended side effects.

[tblivet]

Thanks for reporting this caveat 👍

We already display a message at the end of the update to warn users that, if images do not appear correctly, they need to regenerate them. But if I understand correctly, you’re saying that when new formats are added between v1 and v2 for example, they are not picked up automatically. Is that correct?

I think this is something we should discuss with @Quetzacoalt91. Maybe we should handle it in the migration script for the update we need to think how to handle it better.

[abivia]

That's my experience. But after I posted this, it might be my issue, as something is clearly broken on my end. I added a new store and store group and things are messed up (no currency, can't change logo, etc.) I'm reverting to a backup and giving it another shot. I'll update here if the problem persists. Since I couldn't find this report anywhere else, it might just be specific to this install. [sad face]

[abivia]

Okay, I've done a clean reinstall (UpdateAssistant was out of date, so I updated that first), and the new image formats weren't there. The new multi-store problem persists, but that's a different issue.

Also, on a detailed review, some of the sizes of existing image types has changed too.