COR-667: Media Assets Not Updating

[MKwenhua]

Purpose: Since the media title will be replacing id for asset urls most of the "not updating" issues have been resolved. But there was still a risk of someone updating an asset with a different extension meaning posts that use the asset will not update.

I cover this in detail in a Cortex issue: cortex/issues/456

JIRA:
COR-667

Changes:

• Changes to setup

  • n/a

• Architectural changes

• add a validation to check to see if the new asset matches the content_type of the previous asset

• Migrations

  • n/a

• Library changes

  • Will probably need to bump up a new version

• Side effects

  • Assets can no longer be switched from something like an image to an mp4

Screenshots

• Before
  n/a

• After
  n/a

QA Links:
n/a

How to Verify These Changes

• Specific pages to visit

  • n/a

• Steps to take

  • create a media content type
  • try and create new content type, expect to get an error

• Responsive considerations

  • n/a

Relevant PRs/Dependencies:
n/a

Additional Information
cortex/issues/456

[toastercup]

What's this used for?

[MKwenhua]

Originally before we replaced id's with parameterized Titles updated assets were storing new images on updates since the AssetFieldType id would be different each time. This caused a few issues beyond just storing a new set of images on each update.

But it's purpose is less important now that we use Asset Title instead of ID.

[toastercup]

I'd say we probably don't need it anymore, since we're using the Media Title. You can go ahead and remove these bits. Thanks!

[MKwenhua]

Ok sounds good, but this branch wont work on it's own without asset_field_type_id, but it will when merged with the Media Title story

[toastercup]

I'd suggest merging in the Media Title story, then rebasing this branch with develop. Also, would you mind updating the PR title to follow guidelines?

[MKwenhua]

Ok will do

[MKwenhua]

@toastercup ok merged with the media title branch and removed asset_field_type_id method

[ElliottAYoung]

@MKwenhua What is the status of this PR? There's been no activity for the last month

[ElliottAYoung]

@toastercup @MKwenhua
With the existence of #57 what should we do with this PR?

[toastercup]

@ElliottAYoung once #57 is merged and verified by a PO, we can close this and delete its branch