Alt and Title text that is entered is not carried over to the media [[...]] filter pattern and thus does not show up in the <img> tag. This is a big problem for accessibility, and also for government sites, or other sites which require that.

Proposed resolution

The patch in #89 works and passes tests it applies to 7.x-2.x-dev.
It adds additional alt and title fields, with new help text, to the embedding form options section (where the "current format is" is set. Those fields get populated with the alt and title from the previous forms).

(The patch from #90 might apply to 7.x-1.2. It is similar to the patch from the duplicate issue #1343022-41: Adding alt and title attributes from fields to image markup which is reported to apply to 1.2.)

Remaining tasks

  • (done/ongoing) update issue summary
  • (done) steps to reproduce (see comment #95)
  • (done) screenshots before (see screenshot 11. *no patch* in comment #95 and after (see screenshot 11. in #95, also see steps 13 and 15 in that comment)
  • write tests (see comment #98 and
  • (maybe) manual test for other kinds of media, like files or videos that these additions do not bother those types
  • try patch from #90 and see if it applies to 7.x-1.2.
  • decide if more manual testing is needed:
    • manually test choosing the same image and re-using it in different content. See if it is possible to use different title/alts, while using the same image.
    • manually test using an image field or a reference on the content

User interface changes

New help text and additional fields in a form, with values populated from other steps in the form.

API changes

No API changes.

Original report by @stella

I've read the documentation and looked at other similar reported issues, but can't seem to figure out how the hell to add alt or title attributes to an image uploaded via the WYSIWYG "media browser" button. Here's what I'm doing:

  • Enabled media and media_internet modules
  • Enabled the "media browser" button in my wysiwyg
  • Enabled media input filter on the text format and ensured img tags weren't being stripped
  • Created a new node of type "page".
  • In the body field, clicked on the "media browser" button and uploaded an image from my local machine
  • I then got the display size option but no place to add in alt or title text
  • Saving the image then creates the media embed code but with the alt text attribute is empty
  • Saving the node displays the image thumbnail, but again with no alt or title text.

I've seen suggestions elsewhere that I need to add an "alt" field to my "image" media field type, but having done that, nothing changed. I'm not embedding a previously uploaded image, nor do I have a media image field on any of my content types. I simply want to use the "media browser" to upload and embed images in textareas. However, the lack of alt and title attributes is preventing me from using this module at present.

Any suggestions?

#149 1307054-media-use_raw_value_for_title_and_alt.patch1.25 KBjuampy
#149 Selection_001.png17.1 KBjuampy
#125 two-ways-2013-01-10_1527.png115.23 KBYesCT
#122 Media 2 Image field ALT and TITLE.png7.03 KBFrank Ralf
#99 media-new_alt_title-2012-12-10_1641.png76.63 KBYesCT
#96 media-title-and-alt-attributes-for-images-redid-90.patch5.77 KBYesCT
PASSED: [[SimpleTest]]: [MySQL] 5 pass(es).
[ View ]
#96 interdiff-89-90.txt8.58 KBYesCT
#95 media-s01c-create_page-2012-12-10_0516.png63.41 KBYesCT
#95 media-s02c-upload-2012-12-10_0517.png44.72 KBYesCT
#95 media-s03c-next-2012-12-10_0518.png21.95 KBYesCT
#95 media-s04c-form_alt_title-2012-12-10_0519.png37.01 KBYesCT
#95 media-c05c-form-save-2012-12-10_0520.png21.92 KBYesCT
#95 media-s06c-another_form_save-2012-12-10_0522.png97.07 KBYesCT
#95 media-s07c-format-2012-12-10_0523.png88.26 KBYesCT
#95 media-s08c-preview_in_wysiwyg-2012-12-10_0527.png85.35 KBYesCT
#95 d7-s06-another_form-2012-12-10_0544.png94.3 KBYesCT
#95 d7-s07-format-2012-12-10_0545.png53.92 KBYesCT
#90 media-title-and-alt-attributes-for-images.patch5.95 KBavenhe
FAILED: [[SimpleTest]]: [MySQL] Invalid patch format in media-title-and-alt-attributes-for-images.patch.
[ View ]
#89 1307054-d7-2-alt-text-89.patch2.81 KBjpstrikesback
PASSED: [[SimpleTest]]: [MySQL] 5 pass(es).
[ View ]
#80 1307054-d7-2-alt-text-80.patch1.81 KBjpstrikesback
Test request sent.
[ View ]
#79 1307054-d7-2-alt-text-79.patch2 KBjpstrikesback
Test request sent.
[ View ]
#70 1307054-d7-2-alt-text-70.patch1.78 KBjpstrikesback
Test request sent.
[ View ]
#69 1307054-d7-2-alt-text-69.patch1.74 KBjpstrikesback
Test request sent.
[ View ]
#67 1307054-d7-2-alt-text-67.patch1.32 KBmgifford
PASSED: [[SimpleTest]]: [MySQL] 5 pass(es).
[ View ]
#66 1307054-d7-1-alt-text-66.patch1.19 KBmgifford
PASSED: [[SimpleTest]]: [MySQL] 5 pass(es).
[ View ]
#40 1307054-d7-2.patch2.1 KBredndahead
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1307054-d7-2.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]
#36 media_alt_and_title-1307054-36.patch1.8 KBmfer
PASSED: [[SimpleTest]]: [MySQL] 11 pass(es).
[ View ]
#17 media_alt_and_title-1307054-17.patch1.57 KBDaniel Korte
PASSED: [[SimpleTest]]: [MySQL] 26 pass(es).
[ View ]
#7 media_alt_and_title-1307054-7.patch1.23 KBidflood
PASSED: [[SimpleTest]]: [MySQL] 26 pass(es).
[ View ]


Version:7.x-2.x-dev» 6.x-1.x-dev

Version:6.x-1.x-dev» 7.x-2.x-dev

I don't know why this was moved down to 6.x-1.x-dev, but I'm reporting this problem against 7.x-2.x-dev

The problem is both in wysiwyg and when you use a file field as a media.
It's really a big trouble: the alt attribute is one of the most important thing in web accessibility.
I hope the dev gonna find a solution very fast, because I cannot use the module actually for this only reason...

Title:WYSIWYG media browser image alt and title fieldsWYSIWYG media browser missing image alt and title fields

Tweaking title.

IMO this functionality should exist by default, or there should be clear steps for enabling the functionality.

For the wysiwyg issue I may have a possible workaround. When the image is embeded in the wysiwyg right click on it and "Image properties" (or double click it). There you can define the alt, and in the advanced tab you can define the "Advisory Title".

But this doesn't solve the field issue and a better integrated UI would be great.

Issue tags:+accessibility

By default it sounds like the alt text should be added in the space where the user is prompted to enter the display size. I think it would be good to display the alt text by default and perhaps the title could be enabled through config for those who need it.

But yes, it really should be easier to do this by default.

new1.23 KB
PASSED: [[SimpleTest]]: [MySQL] 26 pass(es).
[ View ]

Here is a first patch that adds two textfields when inserting a media in wysiwyg. This is presented when selecting the format, and allows to set the alt and title. Obviously this needs some more work but I hope it's a step in the right direction.

Subscribing, and... more detail on what sounds like a similar problem (and a contradiction to #5's recommendations above):

If I double-click an uploaded image, the "Alternative text" field in the Image Properties contains the same number that's used in the inserted markup (shown as "XX" here):


If I edit the ALT text field and replace the XX with anything else, the image is no longer displayed once the node is saved.

I think this is a crucial issue. For what reason are these fields not created by installing the Media module?

The patch is not working for me at all. No fields do appear on my file field with the Media browser widget.

I am also missing some place where I could easily administrate Files. The only thing we are able to do currently is deleting files.

Shouldn't we change the category and priority of this issue?

Category:support» feature

If you test patch in #7 be sure to clear the drupal and browser caches. There is a modification on a javascript loaded from the iframe and this require a browser clear cache.

Is there any chance this gets rolled into a release?

Sorry, my fault. I thought it was for both WYSIWYG and the Media field. Would it be difficult to implement this for the Media browser widget as well?

Priority:Normal» Critical

Bumping the priority. This bug rules out using Media on all governmental websites as alt tags are mandatory.

See this issue for a possible solution: #1332500: Alt text doesn't work from wysiwyg

The issue linked in #14 has a link back to this current issue ;-) I guess more and more duplicates of the same issues will pop up soon as title/description and alt attributes from the original ImageField are very widely used. Media should support them as well.

Status:Active» Needs review

Patch in #7 applies nicely to HEAD but I haven't tested out the module yet to see how well this applies.

Agreed that this is a critical issue. Alt tags are low hanging fruit for accessibility of any site, but also important for SEO.

new1.57 KB
PASSED: [[SimpleTest]]: [MySQL] 26 pass(es).
[ View ]

I've updated the patch in #7 to not include the title attribute in the JS function forceAttributesIntoClass. Otherwise every word except the first word in the title attribute is added to the class attribute.

Here's how I solved the problem for the media widget (doesn't solve the WYSIWYG issue.)

There's also

But ultimately this would just be part of the Media module.

hello guys

i am using media module to insert images in wysiwyg editor my input format is filtered html..when i insert images using add media in wysiwyg it does.but when i view the page instead of images i am seeing something like


i dont get it please help me

Do you have "Converts Media tags to Markup" checked for your Text Format at /admin/config/content/formats/?

I've tested the patch in #17 and it works really well. This fix the issue of broken title I had with the patch in #7.

thanks for your reply that solved my problem

@ #18 jonathanmd: Your solution is a great idea but doesn't show any markup. Did you test it under different scenarios already?


What type of markup are you looking for, HTML of the image? There's essentially no change to the image tag other than adding an alt tag or title tag.

All other HTML markup is the same.

<div class="file file-image file-image-jpeg contextual-links-region" id="file-9">
  <div class="content">
    <img alt="An elephant tag" src="" typeof="foaf:Image">

@ jonathanmd : uhm , yeah :) Look, Which part of markup you are hoping to change with your solution isn't really heard to get. :) When I talk about markup in this context, of course I only talk about the awaited alt="" part of the markup and nothing else. I thought this would be clear? Don't get me wrong, but I am not looking for a solution for myself. I just follow the discussion to find the point to start from patching against media or any other module and I just wanted to inform you that it doesn't work over here to help you with report.

But as I already sad before, I don't think, that this, nor the conceptual decision, which it is based on, is the right way for any case. A more flexible point to attach alt="" and title="" like attributes to entities should be preferred. I am not bothering your work-around. I talk about the point it attaches to. In the moment I think about a concept near to Dave Reids field injector to turn any text field to an attribute field which can be injected in any case like -img- or -a- or similar. As a maintainer of link module I would love to see a solution which is DRY and can help more than one situation.

Maybe there should be two points it can be made from @ UI, where the second point, when the image gets inserted into a node will override the first point, where the attributes are set directly to the file entity before... Just thinking ... ... Just thinking ...

Title:WYSIWYG media browser missing image alt and title fieldsMedia browser missing image alt and title fields

Patch #17 works fine in wysiwyg.

A similar patch would be useful when images are published as fields. Any help with that would be greatly appreciated.

In the meantime I'll use the classical image widget, populate the alt+title fields, and switch back to the media browser later (changing the widget doesn't destroy the data).

I wouldn't recommend the solution in #18, because the alt and title fields may vary according to the node type or node language. Sticking to what's already implemented in core is still the safest option, as I have 100s of images to publish.

Can we get these patches and #18 to be added to the media project? Or they need to stay a private solutions which need to be applied on every new release?

Component:Media Browser» WYSIWYG integration

Thank you Dave Reid, but my question is about Alternative Text with the regular widget and not the WYSIWYG.


... I think the issue lies deeper than @ media, and Dave tries to get down to the root of the trouble.
Look here #1291262: Add 'alt' and 'title' tokenized text options for image formatters, and a 'title' option for the generic file formatter

I think that's why he moves this here to a rather soluble issue task ... but not sure yet ...

I'm new to drupal and wondering how I'll use this patch. Can you be of help please. Thanks.

I agree this functionality should be in the Media module itself, but, until it is I use EIM ( which was mentioned in comment #19.

Status:Needs review» Needs work

It would be great if the field names and descriptions matched the proposal here:

Alternative text
This text will be used by screen readers, search engines, or when the image cannot be loaded.
The title is used as a tool tip when the user hovers the mouse over the image.

I had an issue with views where a content type of image being used in a view wouldn't validate as proper HTML.

Looking into why it came down to using the media widget instead of the image widget where the alt tag was never set. I'm assuming that by skipping it that the field in the database got left as NULL and therefore no alt tag was pulled through the view.

The bottom line is that by removing this functionality it caused problems elsewhere in the system so the ability to set the alt and title tag really needs to be brought back into this module as a standard feature.

Status:Needs work» Needs review
new1.8 KB
PASSED: [[SimpleTest]]: [MySQL] 11 pass(es).
[ View ]

Attached is an update that adds the descriptions form #34. There is also an if statement added so we should only show this form if the file is an image. Videos, for example, don't have alt text. The #default_value of '' was removed because code sets that as the default if not supplied.

Can ya'll review?

This may be being handled at #1553094: Alt and Title support for Images or we may need an integration between the two. Either way I think the other issue probably should be committed first.

I just posted a comment on #1553094: Alt and Title support for Images that tried to lay out a plan for integrating alt and title tags. It would be great if people could comment on the validity of that approach.

@redndahead I agree with your flow. Seems sane.

new2.1 KB
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1307054-d7-2.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]

Here is an updated patch that adds support for fields already created in file_entity module.
See the patch located here:

I created a video, no sound, of what the workflow looks like with these patches.

Issue tags:+a11ySprint

I installed and tested the patch in #40. The extra step for adding the alt/title texts is indeed added to the process of adding an image into the node body using the Media Browser button. The test submission was successful and the image contained the alt/title texts in source.

However, this issue also affects images added as file field entries via the "Media file selector". So, as far as I can tell, this is only a partial fix of the issue... unless we break in into two parts, one "RTBC" and the other "needs work".


Status:Needs review» Needs work

The patch no longer applies to the master branch.

$ git apply 1307054-d7-2.patch
error: includes/ No such file or directory
error: js/wysiwyg-media.js: No such file or directory

The patch seems to apply fine to the latest dev code, however #43 is right - this solves the problem when using the WYSIWYG browser, but does nothing for meda uploaded to a file field.

@omar and @mrfelton: see #1553094: Alt and Title support for Images for the field part of this issue.

@redndahead: not sure if it comes from this patch or #1553094: Alt and Title support for Images but the WYSIWYG integration seems only partly solved by #40.
In the workflow of alt/title fields are filled just after upload (~@ second 30) and everything works as expected.

Editing alt/title fields after that, has no effects: neither alt/title show the edited text in the current content—initial entries are displayed, better than nothing :)—nor the file itself is modified.

Editing alt/title for the current content through the WYSIWYG editor itself (WYSIWYG + CKEditor) has no effect either.

What needs to happen to bring this into the next release of this project? It's been inactive since July.

@mgifford, first step would be to reroll #46 against latest dev

Well, there's 2 branches, right. If someone does it might as well be against the git repo, right? --branch 7.x-2.x I expect.


Yes, this is very unfortunate :o( I was very surprised to not have any ALT or TITLE field in the media selector widget. Otherwise, great work on this module.


I just watched this video. Seems like a temporary solution. My question is how do you get back to the ALT and TITLE fields after saving your data initially? For example, is it easy to go back and change the data?


Is there any Patch or Fix for this issue. I am using media 2.0 and it is unfortunate to see media module doesn't have alt and title support. Also it would be a good feature to give user to edit the file name.

@CIsSharp all discussion to my knowledge relies on the 2.x branch -- please look here at a patch #1553094: Alt and Title support for Images

#54 @HyperGlide: Sorry about that. I will change it to 2.x. I tried with latest version of Media (7.x-2.0-unstable6+39-dev) and file entity (7.x-2.0-unstable6+13-dev) without success. It allows to add alt tag and to change the file name but it is not working.

Is this in the latest dev release?

If not what needs to be done - I'm prepared to help, such a basic feature missing from "THE" drupal media module is surprising.

Without this addition it's impossible to get media module to output valid code as the "alt" attribute is a required attr for html5 validation at the very least.

Let's get this in 7.x-2.x DEV and out there ready for the next beta/unstable.

@MJCO thanks for the offer of help.

I believe first we need to complete #1553094: Alt and Title support for Images then re roll and retest this patch.

Please read over that long issue queue and if there are any questions please post em.

Thank you!

#1553094: Alt and Title support for Images is RTBC for file_entity.
Looks like its time to push forward with this. Any assistance would be appreciated as Alt and Title really are critical attributes of an img tag for many users.

Remember - perfect is the enemy of good. Right now we've got a bad solution for everyone wanting to make their sites accessible. Lots of folks have moved to Drupal 7 to make their sites more accessible and alt tags is totally the low hanging fruit of accessibility.

Let's get something good into a release and if we need to perfect it we can do so in a following thread. This thread is over a year old now.

I agree with the above. Is there a list of the current problems not being addressed from the earlier patch other then porting it to the latest dev?

I tried porting the patch, but the javascript has changed so much since the patch in this issue was written that its now unrecognisable, and hard to figure out from the context of that patch where the changes to the javascript now need to be made.

Status:Needs work» Needs review
Issue tags:-accessibility, -a11ySprint

#40: 1307054-d7-2.patch queued for re-testing.

Status:Needs review» Needs work
Issue tags:+accessibility, +a11ySprint

The last submitted patch, 1307054-d7-2.patch, failed testing.

Any development on this issue yet?

See: #1451316: Clean up wysiwyg-media.js

From a quick read I'm not sure we need to hammer attributes into wysiwyg-media.js anymore.

Status:Needs work» Needs review
new1.19 KB
PASSED: [[SimpleTest]]: [MySQL] 5 pass(es).
[ View ]

Just bringing forward the patch in #40 against 7.x-1.x-dev knowing that I haven't changed the version number and it's going to bust.

new1.32 KB
PASSED: [[SimpleTest]]: [MySQL] 5 pass(es).
[ View ]

@jpstrikesback not sure how we'd hammer them in at this point. This patch doesn't include any changes to wysiwyg-media.js and is built against the 2.0 git repo.

Status:Needs review» Needs work

Tested and unfortunately changes to existing/new alt/title text does not get picked up...Tho it is nice to see alt & title working with any file you upload, but they cannot currently be changed via the media browser form in wysiwyg

Status:Needs work» Needs review
new1.74 KB
Test request sent.
[ View ]

OK, found the spot in wysiwyg-media.js that needed attributes added back in. Please test the patch attached, there is work to be done in the media format form because it never pulls any settings out of the tag when editing an already inserted item, that can probably go into a new/existing issue. This get's us the ability to set alt/title per image & override what is set in a field alt/title :)

To see the limitations, add or modify an alt/title and then try to edit it via the media popup again. You'll notice the text in the token does not make it back to the format form.

new1.78 KB
Test request sent.
[ View ]

That one in #69 wont apply/pass, my git settings are funny and I have to manually edit the file paths...this one should apply:

Status:Needs review» Needs work

Status:Needs work» Needs review

trying to reset the testbot

Something is up with the testbot...

got a pretty big queue to handle

A comma is missing after view_mode: formatted_media.type

This will cause the wysiwyg js to fail.

Thanks for pushing this issue forward!

@sylus, it actually doesn't and is important as this bit is in a JavaScript file, where a trailing comma can mess with IE (Internet explorer)

Edit: your right!!! nice catch!!

Hmm are you sure your patch has:

     var element = create_element(formatted_media.html, {
           fid: this.mediaFile.fid,
           view_mode: formatted_media.type
           attributes: formatted_media.options

I think it should be

     var element = create_element(formatted_media.html, {
           fid: this.mediaFile.fid,
           view_mode: formatted_media.type,
           attributes: formatted_media.options

Once I add the comma I no longer get a JS error and TinyMCE loads

of course, I misread your comment sorry, I thought you were saying .options needed a trailing comma! :)

new2 KB
Test request sent.
[ View ]

There we too many command Z's to remove console.log(blah) got me in that spot :) Thanks @sylus!

new1.81 KB
Test request sent.
[ View ]

aaaaaand one more time with a folder structure that will pass...argh


With this patch I think I finally have alt working with media.

So with patches:

1) #79 from this thread
2) #1553094: Alt and Title support for Images or latest release from File_Entity

and in hook_wysiwyg_editor_settings_alter for tinymce

// Allow extra elements for Media module
// See -
$settings['extended_valid_elements'] .= ',img[src|view_mode|format|fid|alt|title]';

I now finally have working alt and title tags! :)

Excellent!! Let's get a few more testers on it and RTBC this baby!

#80 passed, hopefully the testbot will catch up and send results

Status:Needs review» Needs work

Somewhere the values are getting stripped from the alt & title tags in the final render on a published node, they make it thru when the alt/title is in the alt/title field, but not when it's only in the media tag, they still exist but are not rendered, so somewhere there is some validation going on I guess

I'm getting this as well. The patch in #80 works so far as letting me enter Alt and Title text, and they appear in the attributes in the media tag:

[[{"fid":"620","view_mode":"media_original","type":"media","attributes":{"height":220,"width":220,"alt":"Alt Test","title":"Title Test","class":"media-element file-media-original"}}]]

...but the rendered image tag is missing those attributes:

<img height="220" width="220" alt="" title="" class="media-element file-media-original" typeof="foaf:Image" src="/sites/default/files/u2/attraction_test.jpg">

One thing I didn't do was add the attributes to hook_wysiwyg_editor_settings_alter() -- I'm using CKEditor rather than tinymce, so I wasn't at all sure if I needed to do something similar. Anyone been able to get this to produce alt and title attributes on output?

I think the issue is in media_token_to_markup() when it calls media_get_file_without_label() to prepare the item for render, it doesn't have a way to send in the attributes cause it renders it from the file entity properties...tho I haven't looked at this in almost a week, someone please correct me if I'm wrong

cant you override the file object values before passing it to media_get_file_without_label ?

I'm not certain why this works, and by no means am I certain this is the right thing to do it, and I have no idea how to offer it as a patch, but this seems to get my alt and title tags filled in on rendered nodes. Starting at line 179 of

  else {
    // Display the field elements.
    $element = array();
    $element['content']['file'] = media_get_file_without_label($file, $tag_info['view_mode'], $settings);
    if (isset($tag_info['attributes']['alt'])) {
      $element['content']['file']['#alt'] = t($tag_info['attributes']['alt']);
    if (isset($tag_info['attributes']['title'])) {
      $element['content']['file']['#title'] = t($tag_info['attributes']['title']);
    field_attach_prepare_view('file', array($file->fid => $file), $tag_info['view_mode']);
    entity_prepare_view('file', array($file->fid => $file));
    $element['content'] += field_attach_view('file', $file, $tag_info['view_mode']);
    if (count(element_children($element['content'])) > 1) {
      // Add surrounding divs to group them together.
      // We dont want divs when there are no additional fields to allow them
      // to display inline.
      $element['content']['#prefix'] = '<div>';
      $element['content']['#suffix'] = '</div>';
  drupal_alter('media_token_to_markup', $element, $tag_info, $settings);
  return drupal_render($element);

Status:Needs work» Needs review
new2.81 KB
PASSED: [[SimpleTest]]: [MySQL] 5 pass(es).
[ View ]

Thanks @rootatwc & @wrd, that's exactly what was needed. I used what had already been cleared for landing in $settings and placed in the $file object. I also did an !empty() instead of isset() so as not to override a fields default alt/title with an empty alt/title in the edited textarea field.

new5.95 KB
FAILED: [[SimpleTest]]: [MySQL] Invalid patch format in media-title-and-alt-attributes-for-images.patch.
[ View ]

Here is my patch

Status:Needs review» Needs work

The last submitted patch, media-title-and-alt-attributes-for-images.patch, failed testing.

Hey @avenhe, can you add a description of your changes (why, etc) and check your patch applies against current dev with "git apply"?


needs re-roll and interdiff for #90 patch.
also needs issue summary updating, and steps to reproduce

Status:Needs work» Needs review

#89: 1307054-d7-2-alt-text-89.patch queued for re-testing.

with the patch from #89:

0. get drupal and modules
get d7, (I did git clone)
cd drupal/sites/all/modules
get these modules (I did git clones, but could have downloaded tars, or done drush dl)
git clone --recursive --branch 7.x-2.x
git clone --recursive --branch 7.x-2.x
git clone --recursive --branch 7.x-3.x
git clone --recursive --branch 7.x-2.x
git clone --recursive --branch 7.x-1.x
cd media
curl -O
git checkout -b media-89
git apply --index 1307054-d7-2-alt-text-89.patch
git commit -m "89"

1. enable modules: wysiwyg and media
(dependencies also cause enabling: File entity, Chaos tools, Views)

2. configure wysiwyg admin/config/content/wysiwyg
download, unzip wysiwyg (I did tinymce and ckeditor, an older version) and put in correct spot in libraries (make libraries directory)

3. pick ckeditor for full html (could have done filtered html, but would then have to add <img> [edit: add code to see the img tag] to the allowed tags)

4. edit (in that row) and check media browser
get error have to enable media filter "Convert Media tags to markup". do that.
check the media browser button again. saves fine this time.

5. create a page

6. upload an image

7. next

8. form lets enter alt and title

9. save

10. save again

10 *no patch*. save again

11. pick format (if picking default, had to have set the default image file to image at admin/structure/file-types/manage/image/file-display, I'll just pick preview)

11 *no patch*. pick format (preview)

12. see image in the wysiwyg text area preview

13. can toggle the disable rich text to see the html/filter

<p>[[{"fid":"2","view_mode":"teaser","type":"media","attributes":{"height":137,"width":220,"alt":"test jing capture of wysiwyg settings","title":"Test Capture of WYSIWYG word","class":"media-element file-teaser"}}]]</p>

13 *no patch* toggle
shows something like:
<p>[[{"fid":"3","view_mode":"teaser","type":"media","attributes":{"height":137,"width":220,"class":"media-element file-teaser"}}]]</p>

14. save

15. image shows fine. tool tip works. can inspect the html to see
<img alt="test jing capture of wysiwyg settings" title="Test Capture of WYSIWYG word" class="media-element file-teaser" typeof="foaf:Image" src="http://localhost:8888/d7-git/sites/default/files/styles/medium/public/test_0.png" height="137" width="220">

15 *no patch*. image shows fine. no tool tip. inspect and see no alt or title tag
<img class="media-element file-teaser" typeof="foaf:Image" src="http://localhost:8888/d7-git/sites/default/files/styles/medium/public/test_1.png" alt="" title="" height="137" width="220">

new8.58 KB
new5.77 KB
PASSED: [[SimpleTest]]: [MySQL] 5 pass(es).
[ View ]

I looked into applying the patch in 90 and I'm not sure what happened to corrupt it.

This is the changes from it (I think).
I did an interdiff, but it probably does not make much sense... it's here anyway.

I did not test 90, or do a code review.

@avenhe Let us know your thoughts on why your changes from 90 might be a better approach...

looking at the redid-90.patch from #96

+++ b/includes/media.fields.incundefined
@@ -159,21 +158,57 @@ function media_field_widget_form(&$form, &$form_state, $field, $instance, $langc
+    $fields['alt'] = array(
+      '#title' => t('Alternate text'),
+      '#type' => 'textfield',
+      '#default_value' => isset($current_value['alt']) ? $current_value['alt'] : '',
+      '#description' => t('This text will be used by screen readers, search engines, or when the image cannot be loaded.<br />
+        <em>(Notice: this field is not fetched on -all- formatters yet. For example: If the Rendered file formatter will be used, this field is not available at the moment.)</em>'),
+      '#maxlength' => variable_get('image_alt_length', 80),
+      '#weight' => 1,
+      '#access' => $field_settings['alt_field'],
+    );
+++ b/includes/media.filter.incundefined
@@ -388,22 +380,6 @@ function media_format_form($form, $form_state, $file) {
-  if ($file->type === 'image') {
-    $form['options']['alt'] = array(
-      '#type' => 'textfield',
-      '#title' => t('Alternate text'),
-      '#description' => t('This text will be used by screen readers, search engines, or when the image cannot be loaded.'),
-      '#default_value' => isset($file->field_file_image_alt_text['und'][0]['safe_value']) ? $file->field_file_image_alt_text['und'][0]['safe_value'] : '',
-    );

why was this alt section moved to from the file? Does it better get a default value? What is the concern the Notice is addressing?

+++ b/includes/media.fields.incundefined
@@ -159,21 +158,57 @@ function media_field_widget_form(&$form, &$form_state, $field, $instance, $langc
+    $fields['title'] = array(
+      '#type' => 'textfield',
+      '#title' => t('Title'),
+      '#default_value' => isset($current_value['title']) ? $current_value['title'] : '',
+      '#description' => t('The title is used as a tool tip when the user hovers the mouse over the image.<br />
+        <em>(Notice: this field is not fetched on -all- formatters yet. For example: If the Rendered file formatter will be used, this field is not available at the moment.)</em>'),
+      '#maxlength' => variable_get('image_title_length', 500),
+      '#weight' => 2,
+      '#access' => $field_settings['title_field'],
+    );
+++ b/includes/media.filter.incundefined
@@ -388,22 +380,6 @@ function media_format_form($form, $form_state, $file) {
-    $form['options']['title'] = array(
-      '#type' => 'textfield',
-      '#title' => t('Title'),
-      '#description' => t('The title is used as a tool tip when the user hovers the mouse over the image.'),
-      '#default_value' => isset($file->field_file_image_title_text['und'][0]['safe_value']) ? $file->field_file_image_title_text['und'][0]['safe_value'] : '',
-    );

why was this section moved to from the file? Does it better get a default value?

+++ b/media.moduleundefined
@@ -988,10 +984,21 @@ function media_element_process(&$element, &$form_state, $form) {
+  $element += array(
+    '#pre_render' => array('media_pre_render_fieldset', 'form_pre_render_fieldset'),
+  );
+  $element['#theme_wrappers'] = array('fieldset');
+  if (!$element['#value']) unset($element['#value']);
   return $element;
   // @todo: make this work for file and image fields

does this code block accomplish the @todo of making it work for file and image fields?

+++ b/media.moduleundefined
@@ -988,10 +984,21 @@ function media_element_process(&$element, &$form_state, $form) {
+function media_pre_render_fieldset(&$v) {
+  unset($v['#value']);
+  return $v;

This function needs a doc block.

Status:Needs review» Reviewed & tested by the community
Issue tags:-Needs steps to reproduce, -Needs reroll

I tried the redo to 90 patch from #96
It acts like 7.x-2.x without the patch, like screenshot 11 no patch in #95 and the title and alt is not in the media [[..]] filter string.

Based on that, I recommend the patch from #89 and I'll mark it rtbc for 89.

Does the maintainer require tests? If so, mark this back to needs work.
It would be really nice if a test were added so that we could show it fails to add the alt and/title without the patch. [edit: forgot the actual link. adding it.]
This doc page is for adding tests to core, but would be helpful for how to add tests for this, and also it shows how to make a tests only patch and a complete patch that will show pink and then green. This exposes the bug and proves the fix works.

new76.63 KB

Updating the issue summary.

Issue summary:View changes

updated issue summary and used issue summary template

awesome job, thanks a lot YesCT..although i dont require tests, it would be good to start adding some now that testbot is back to life for media..
If someone cares to add some before i commit this, i will definitely not say no

You rock YesCT!

@YesCT: Job well done. Thank you, Thank you, Thank you! :)

There is some more work here to do I think.

A kind person alerted me that this very same approach was taken out, on purpose. So we need to look into that more to see why and what the alternative suggestion is.

Also, we should look at the 1.x branch and see if we can port this (or the inferred better way) back to that.


We'll get there eventually. :)

Leaving it rtbc until we have specific feedback that says this approach is a won't fix (hopefully linking to the issue or commit that took it out) and/or a needs work with the approach that should be used instead.

If this patch works, can it be added to a release any time soon?

YesCT can you elaborate? I'm in favor of this going in now for a major accessibility win and then being improved if a generalized 'extra rendered property' feature request comes forward afterwards...

do any of the patches above work with the 1.x branch? is there a work-around for 1.x?

Patch #89 works great! I like how this associates the data with the file entity so it can be reused. Well done!

i concur with comment 55 in that thread. the solution here is actually very elegant, the alt/title are indeed stored along with the media, but they are merely suggestions during placement of the image that can be overridden on display.

I'm still sorting out all the related issues and approaches.

The patch from #90 (and thus #96 which is discussed in #97) is mostly the same as the patch in the duplicate issue #1343022-41: Adding alt and title attributes from fields to image markup which applies to 7.x-1.2.

In #1343022-54: Adding alt and title attributes from fields to image markup, Frank points out that the media module is removing the image field alt/title fields.

// On image fields using the media widget we remove the alt/title fields

I'm guessing that this is because using the media widget and image fields, images can be reused, and alt and title should be able to be different each time it's used to display an image. <- I dont think that is quite accurate, so please correct me.

Still more thinking to do on this.

Thanks YesCT,

I'm guessing that this is because using the media widget and image fields, images can be reused, and alt and title should be able to be different each time it's used to display an image. <- I dont think that is quite accurate, so please correct me.

This is the case with the patch in #89 for WYSIWYG usage, i.e. it allows one to add a new alt/title to each instance of a image in wysiwyg. You are correct that this is not the case for usage in a field as then it uses the field formatters and storage IIUC.

Regarding the 7.x-1.x branch I believe we can focus on adding new features to 2.x and backporting later.


Issue summary:View changes

add a possible remaining task of testing with other kinds of files.

Issue summary:View changes

updated with info about a workaround for 1.2 and drafts of manual test that might be needed.

I updated the issue summary. And I guess we are (I am) kind of done here until we get someone to commit this or mark it needs work.

To clarify, the remaining tasks in the issue summary are "extra" and might help but I do not think they are urgent or required.

Agree :) and thanks for all your work here YesCT!!

I'm guessing that this is because using the media widget and image fields, images can be reused, and alt and title should be able to be different each time it's used to display an image. <- I dont think that is quite accurate, so please correct me.

This is the case with the patch in #89 for WYSIWYG usage, i.e. it allows one to add a new alt/title to each instance of a image in wysiwyg. You are correct that this is not the case for usage in a field as then it uses the field formatters and storage IIUC.

Might it not be better to allow the file's alt & title text be assigned but allow them to be overridden per usage? This would cover for all three possible scenarios - one set of alt/title tags per image, "default" alt/title tags per image that may be overridden per use, no "default" tags per image forcing them to be set per use.


Might it not be better to allow the file's alt & title text be assigned but allow them to be overridden per usage? This would cover for all three possible scenarios - one set of alt/title tags per image, "default" alt/title tags per image that may be overridden per use, no "default" tags per image forcing them to be set per use.

#89 allows any previously stored alt/title (i.e. in field storage, Tho that is not per instance is it, that doesn't seem to make sense??) to come thru as the default, but allows one to also override those defaults on an individual instance basis when used in a textarea via WYSIWYG media integration.

Status:Reviewed & tested by the community» Fixed

+++ b/includes/media.filter.incundefined
@@ -180,6 +180,14 @@ function media_token_to_markup($match, $wysiwyg = FALSE) {
+      $element['content']['file']['#alt'] = t($element['content']['file']['#attributes']['alt']);
+      $element['content']['file']['#title'] = t($element['content']['file']['#attributes']['title']);

removed t()

and commited

Awesome work everyone!

Nice! Thanks all!!

Thanks, I needed this a lot! A couple of questions:

1) Is this going to be rolled into e a release soon?

2) I have already a few hundred image files uploaded to my site. I also have them populated into some Image Fields which today don't have alt and title attributes. After I update Media with this fix will my existing images get alt and title automatically? If not, what do I need to do in order to synchronize my files' and my images' alt and title attributes?

++ to all!

I would also like to know the answer to #119-2
I know it will not be automagically ;)

Status:Fixed» Needs work
new7.03 KB

Sorry for re-opening this issue but I upgraded to the current dev version of Media 2 (7.x-2.x-dev 2013-Jan-06) and notices some strange behavior.

  1. The alt and title field settings for the Image field are only available when selecting widget type "Image".
  2. There are no alt and title fields available at the image field, regardless of selected widget type.
  3. Even with settings for alt and title as in the screenshot (widget type "Image") and then switching to widget type "Media file selector" both alt and title fields are shown in the Media file selector.

I wonder whether this is the intended behavior.

Media 2 Image field ALT and TITLE.png

@Frank Ralf - this is specific for files fields- not for image fields. The screen shot that you show above is from an image field so you won't see the functionality described in this thread.

Status:Needs work» Fixed

Actually to be more correct.that functionality is for file/image fields that use the media widget.
Those settings come from core image module, but right now media widget does not use them.
Instead, fields attached to image file type provided by file_entity module are used.
If you dont have those fields attached to your image file type, plz make sure you have latest file_entity version and run update.php

new115.23 KB

I did a quick test.
Yep. definitely via the media browser in wysiwyg is different than an image in an image field on the content type.

I'm going to make sure I have everything updated and do a few more tests.


If you dont have those fields attached to your image file type, plz make sure you have latest file_entity version and run update.php

what do you mean "those fields"? the ones for the media browser wysiwyg? (or the ones for the core image field?)

opened related #1885732: Documenting alt and title tags on image fields (so as to not clog up this wysiwyg issue with general investigation on my part.)

@Frank Ralf is what you saw in #122 what I saw in comment 3 there? #1885732-3: Documenting alt and title tags on image fields

Those fields = Alt and title field.
See under Structure -> File types -> Image -> Manage fields

Thanks for testing and clarification!

Will follow the issue at #1885732: Documenting alt and title tags on image fields.

@rootatwc (#124)
Thanks for this information, that was the missing piece of the puzzle.

Is there an upgrade path to convert core Image fields with their alt and title tags to Media 2's file entities?

not, that i am aware of, but wouldnt be that hard to create one

Thanks for the quick reply!

Status:Fixed» Closed (fixed)

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

Status:Closed (fixed)» Active

Re-opening the issue because of the lack of upgrade path... ot whould I open a new one for that?

Status:Active» Closed (fixed)

I would rather call it migrate path.Please open a new issue..

I'm using the latest media 2x and file_entity and I can't see any alt and title fields anywhere.

I have a 'File' field, using media file selector.

At /file-types/manage/image/fields

I have 'File name' and 'File' fields only

At /node/8/edit

I have Select Media|Edit media|Remove media

If I select 'Edit media', a little popup with 'Name' and 'Replace file'.

At /file-types/manage/image/file-display

I have 'Image style' (dropdown), 'Alt attribute' and 'Title attribute' fields

So where are these fields actually displayed so I can fill them in when I upload an image? I can't seem to find them.

I also missed those fields at first. They will show in one of the subsequent steps when choosing a file with Media's "Media file selector" widget.


@Frank Ralf, yes they do now?! Maybe I didn't have the latest version after all. Thanks.

"closed fixed"?

So is this fixed or not?

If it is, where are alt & title in the actual UI?

Can i JUST use it, or do i have to follow some "one meelion simple little steps"-description?

what is the official information about this?

Hi MatsSvensson-

Sounds like you're frustrated. Unfortunately no one here is paid to maintain this module so we all try to pitch in where we can. A number of people have worked on a fix for this and as it currently stands this functionality works correctly in the 2.x branch. I can't speak for the 1.x branch as I'm not familiar with it.

There is documentation that is referenced from the project page. If you don't find it adequate please file an issue with your suggestions or feel free to add to it.

But can i use 2.0?
It says "unstable".

Its pretty confusing to have to choose between a "recommended" release that obviously does not work, and a "unstable" release that everyone says works.

Hi MatsSvensson,

Granted that would be confusing but it is also good to remember that unstable does not equal broken or non functioning, it means it is not stable, APIs, functionality, UX, etc are subject to change without notice (tho in practice you will find plenty of notice in the issue queues).

As to whether you can use it or not, that is kinda dependent on your plan for ongoing maintenance of whatever site you install this in. I am, but that means I have to keep track of changes and re apply patches, watch for functionality removed, whatnot, while I wait for a stable version.


Hi MatsSvensson,

I am using:

File entity: 7.x-2.0-unstable7
Media: 7.x-2.0-unstable7

For your benefit, I knocked up a very quick image with a few screenshots of the stages involved for uploading an image. This is what happens on my new local site for a simple product gallery.

1) Click 'Select media'
2) Browse to file
3) Click 'Submit'
4) Gives you a preview of the image and the elusive 'Alt' and 'Title' fields.
5) Save
6) Not pictured, but after the image is uploaded, when you click 'Edit', you get another popup where you can edit the 'Alt' and 'Title'.

Give it a shot with these versions, see how you get on.

I hope this illustrates things a bit more clearly.

Great info!
Thanks for the help.

Ill give it a try when i get some time for more testing.

Following the steps in #143, I never get 4)
After Submit in 3) it just closes the media popup without ever showing the Alt and Title fields.

This is new since updating media module from 7.x-2.0-unstable7+2-dev to 7.x-2.0-unstable7+38-dev. Before that I had the alt & title fields.

EDIT: Looks like I needed to update file_entity module to latest dev as well. Now they are showing up again.

Issue summary:View changes

Updated issue summary fixed [# problem

Can we use the patch on a Stable version of Media 1.3. How do we apply the patch ? I am new to the concept of Patching drupal modules, I would prefer manual patching.

Id appreciate any guidance. Thanks.

I just updated to Media 7.x-2.0-alpha2 and I have the current version of File_entity 7.x-2.0-alpha2.

I'm still missing my Alt/Title field data. Any help on getting this data back is appreciated. I'm working on a big site and we need the Alt/Title field tags!



Anyone still experiencing this issue should join the testing/discussion at

Issue summary:View changes

small typo fixed

Component:WYSIWYG integration» Code
new17.1 KB
new1.25 KB

I know this issue was closed but since #2142571: Spin-off WYSIWYG support in dedicated module / project got rid of all of this code I have nowhere else to reference it.

The commit added at #116 uses 'safe_value' instead of the raw one. This encodes symbols like double quotes and shows them in the form field. See the following attachment:

This makes that the json representation of the image saved in the database is invalid and therefore the image is not rendered.

Just for reference for people who still have this version of the media module, here is a patch to address this issue.

I am using media 7.x-2.0-alpha3+46-dev and cannot apply the patch from #89. I get this.

can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff --git a/includes/ b/includes/
|index 4e9d64c..cd2a538 100644
|--- a/includes/
|+++ b/includes/
File to patch:

In my dev version (7.x-2.0-alpha3+46-dev) I don't have the file includes/

This file exists in media 7.x-2.0-alpha3, but the patch from #89 fails there also:

patching file includes/
Hunk #1 FAILED at 180.
Hunk #2 FAILED at 380.
2 out of 2 hunks FAILED -- saving rejects to file includes/
patching file js/wysiwyg-media.js
Hunk #1 FAILED at 171.
1 out of 1 hunk FAILED -- saving rejects to file js/wysiwyg-media.js.rej

What is the situation with this patch for 7.x-2.x?


@drupov this issue is closed and the patch was committed please look at

If have other questions suggest you open a new issue.