# Visually breaking change in package **URL:** \ **Category:** Marketplace\ **Created:** [January 16, 2024, 10:11am UTC](https://forums.concretecms.org/t/visually-breaking-change-in-package/6803 "2024-01-16T10:11:56Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![enlil](https://forums.concretecms.org/user_avatar/forums.concretecms.org/enlil/32/3526_2.png) [@enlil](https://forums.concretecms.org/u/enlil)\ **Post date:** [January 16, 2024, 10:11am UTC](https://forums.concretecms.org/t/visually-breaking-change-in-package/6803/1 "2024-01-16T10:11:56Z")
I have a visually breaking change in a package (image needing a size vs being hard wired). What would be my appropriate action to take code wise, as far as notifying users before updating/downloading the package from MP? What does the download notes input in the MP upload interface do? I’ve never actually used that?? Edit: For instance, I see package /elements/install.php and uninstall.php in use. Is there an update or upgrade.php element that handles this? ---
**Author:** ![mnakalay](https://forums.concretecms.org/user_avatar/forums.concretecms.org/mnakalay/32/6276_2.png) [@mnakalay](https://forums.concretecms.org/u/mnakalay)\ **Post date:** [January 16, 2024, 10:39am UTC](https://forums.concretecms.org/t/visually-breaking-change-in-package/6803/2 "2024-01-16T10:39:29Z")
I am not convinced anybody reads download notes or upgrade notes. If your image’s size used to be hard-coded but now needs a specific size, is there a reason why you can’t have a default fallback value in case the size is not defined in the parameters? There are no update or upgrade elements unfortunately. Maybe you could check if the install element would be used during an update? It wasn’t in the past but it might have change? ---
**Author:** ![enlil](https://forums.concretecms.org/user_avatar/forums.concretecms.org/enlil/32/3526_2.png) [@enlil](https://forums.concretecms.org/u/enlil)\ **Post date:** [January 16, 2024, 10:48am UTC](https://forums.concretecms.org/t/visually-breaking-change-in-package/6803/3 "2024-01-16T10:48:31Z")
I wondered the same thing about the install element. I’ll have to try and see what happens. Fallback is a bit of a conundrum. The size input was always there, just not used in this context. Could have been set to 20px and had no effect. Suddenly, there will be 20px images. Nothing that can’t be fixed in moments. Just hoped there was a streamlined way to notify, short of opening a support request against my own package to include an answer for those who may come looking… ---
**Author:** ![JohntheFish](https://forums.concretecms.org/user_avatar/forums.concretecms.org/johnthefish/32/3767_2.png) [@JohntheFish](https://forums.concretecms.org/u/JohntheFish)\ **Post date:** [January 16, 2024, 10:57am UTC](https://forums.concretecms.org/t/visually-breaking-change-in-package/6803/4 "2024-01-16T10:57:28Z")
Even fewer people read the support requests. After a core upgrade the core puts out an updated message with info about the update, so perhaps that mechanism could be used. May take take some digging to discover how it works. ---
**Author:** ![EvanCooper](https://forums.concretecms.org/user_avatar/forums.concretecms.org/evancooper/32/4597_2.png) [@EvanCooper](https://forums.concretecms.org/u/EvanCooper)\ **Post date:** [January 19, 2024, 2:07am UTC](https://forums.concretecms.org/t/visually-breaking-change-in-package/6803/5 "2024-01-19T02:07:22Z")
When you update an addon in the dashboard, it shows what you have entered for the addons version history before you actually update the addon. If you put some notification at the top of your version history in BIG CAPS OMG OMG or something that’s probably a reasonable way to catch your users’ attention before they do the update.