With Mediafield moving on its own and being deprecated (see #1201936: Move the media field to a non-required submodule), the alternative should be clearly highlighted at least in the .info file, not just marking its status as "deprecated". It's misleading and doesn't provide users with a clear alternative.

This possibly could also be mentioned every time a new Mediafield instance is created.

CommentFileSizeAuthor
#1 explain-mediafield-deprecated-1324316-1.patch839 byteserikwebb
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

erikwebb’s picture

erikwebb CreditAttribution: erikwebb commented
Status: Active » Needs review
FileSize
explain-mediafield-deprecated-1324316-1.patch839 bytes
askibinski’s picture

askibinski CreditAttribution: askibinski commented

+1 Yes, that would be very helpful!
I was just wondering why it was deprecated when I found this issue.

aaron’s picture

aaron CreditAttribution: aaron commented
Status: Needs review » Reviewed & tested by the community

Looks good to me

Dave Reid’s picture

Dave Reid
he/him
Primary language English
Location Nebraska USA
CreditAttribution: Dave Reid commented
Status: Reviewed & tested by the community » Fixed

I tweaked the text a tiny bit to say "Deprecated by the core File field type.".

Committed to 7.x-2.x with http://drupalcode.org/project/media.git/commit/38e6292

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) CreditAttribution: commented
Issue summary: View changes

Add possibility of warning on field creation.