We need to retire image assets which are no longer used on the redesigned consumer pages. - Remove references to image assets in the constants files. - Write a migration to delete retired image assets.
Once Fireplace replaces the consumer pages, we should file probably also remove Image Assets from the Edit Listing page.
Updating the constants will actually remove the Edit Listing fields automagically. The formset is based on the constants.
blocked on fireplace being live
Priority: -- → P5
Don't forget to remove the db columns, the apis, the tests and the model code etc.
Regarding the hue code: I wouldn't remove it until UX figures out what they want to do with the feed. Not all of the image assets are going away, and I'd be hesitant to speculate that they won't want assets with generated backgrounds.
In my talking to UX, they don't. It'll be user-supplied content and/or screenshots with SVG filters.
The image assets are user-supplied and they looked like crap until we started generating backgrounds for them.
It turns out that the feed is probably going to use hue detection on the client side. We can remove all image asset-related code in the project.
Component: General → Code Quality
No longer depends on: 847679
Priority: P5 → P4
Summary: [fireplace][redesign] Retire old image assets → Remove image assets
Fixed in https://github.com/mozilla/zamboni/commit/a0d1b693ed53ff8ddb51bdca49f89775eb94c2d9 STR: - Check that the app edit listing 'Media' section no longer references 'image assets' and that uploading a screenshot still works.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Verified as fixed in https://marketplace-dev.allizom.org/developers/ on FF26 (Win 7). Postfix screencast http://screencast.com/t/1d9B2UMwpPE Closing bug.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.