- Issue created by @charles belov
- First commit to issue fork.
The instructions for adding a custom or legacy (pre-Media module installation) media field are incorrect. It would be good to correct them so that they reflect what actually occurs in Drupal. On the help page, it would also help to not try to save verbiage at the cost of clarity.
As they stand, the instructions require the administrator to guess at the missing steps or distinguish between two options without understanding what the differences are between those two options.
Steps:
Result: See the following instruction:
Use Media reference fields for most files, images, audio, videos, and remote media. Use File or Image reference fields when creating your own media types, or for legacy files and images created before installing the Media module. For more information, see the Media help page.
Expected result: Additional information both about creating your own media types and for handling legacy files and images
Actual result: Additional information both about creating your own media types, but only a repeat of the previous message concerning handling legacy files and images with no further information about that.
The instructions at /admin/help/media include the following:
Creating custom media types
The Media module gives users with the Administer media types permission the ability to create new media types in addition to the default ones already configured. Each media type has an associated media source (such as the image source) which support thumbnail generation and metadata extraction. Fields managed by the Field module may be added for storing that metadata, such as width and height, as well as any other associated values.
and
Use Media reference fields for most files, images, audio, videos, and remote media. Use File or Image reference fields when creating your own media types, or for legacy files and images created before installing the Media module.
Expected result, based on the instructions: File and Image are options
Actual result, which the instructions need to be changed to match: Neither file nor image is an option.
Expected result, based on the instructions: File and Image are options
Actual result, which the instructions need to be changed to match: Nothing appears to be relevant
Expected result, based on the instructions: File and Image are options
Actual result, which the instructions need to be changed to match: the following possibly relevant items appear in the list:
File
Media
Image style
Expected result, based on the instructions: File and Image are options
Actual result, which the instructions need to be changed to match: Nothing appears to be relevant
Expected result, based on the instructions: File and Image are options
Actual result, which the instructions need to be changed to match: the following possibly relevant items appear in the list:
File
Media
Image style
In other words, I don't see any difference between choosing Content or choosing Other. Is one better than the other? I don't see Image as a standalone item in the drop-down list. So at this point I'm not sure what to do. Will choosing using Media provide the desired functionality? I don't know.
Improve the instructions on /admin/structure/types/manage/page/fields/add-field to be brief and accurate.
Add more detailed instructions for legacy files and images on /admin/help/media to be more step-by-step and accurate.
On /admin/help/media, it would help on the instructions for legacy files and images to split out the instructions for legacy files from the instructions for legacy images rather than trying for brevity, even though it results in redundancy. That way the administrator doesn't have to parse all the "or"s.
Improve the instructions on /admin/structure/types/manage/page/fields/add-field to be brief and accurate.
Improve the instructions for legacy files and images on /admin/help/media to be more step-by-step and accurate.
Active
11.0 🔥
Last updated
Makes Drupal easier to use. Preferred over UX, D7UX, etc.