Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
In settings for media gallery in configuration tab it's possible to specified FULL Html format for text. The problem and I don't know if it's a bug or by design, when you create or edit a gallery it's not possible to have by exemple Wysiwig with TinyMCE. You have to input the full code manually. It would be nice to be able to use the input format setting for the main core who is normally available when creating a blog or article node. Even if you go to structure for the content type gallery we are not able to modified the gallery description field, it says it's lock !
Comment | File | Size | Author |
---|---|---|---|
#4 | 0001-1112432-Add-text-format-support-to-the-media-gallery.patch | 2.03 KB | james.elliott |
Comments
Comment #1
David_Rothstein CreditAttribution: David_Rothstein commentedSeems like it would be reasonable to set up this field so that it uses text formats, yes. I can't think of any downsides.
Some of the fields have to be locked because it would break the module if someone removed them or changed them in certain ways. It would be really nice if we could "partially" lock them (rather than lock them completely) but I don't think there is a simple way to do that (it would be great if someone could prove me wrong though).
Comment #2
David_Rothstein CreditAttribution: David_Rothstein commentedBy the way, as described at http://www.drupalgardens.com/content/feature-request-galleries-wysiwyg-e..., one way to work around this limitation for now would just be to add your own custom field to gallery nodes (separate from the description field), and use that one instead.
Comment #3
sw3b CreditAttribution: sw3b commentedYes this is what I did because the actuall body cannot make it. I also agree with you on unlock some fields so that way we can configure them.
Comment #4
james.elliott CreditAttribution: james.elliott commentedPatch attached for this.
Comment #5
David_Rothstein CreditAttribution: David_Rothstein commentedThe update function looks potentially dangerous... what text format will the content get after update? It seems like it could break existing formatting.
We could partially mitigate that problem by forcing existing content to be assigned the site's fallback format (a.k.a. usually plain text) after the update... But I'm not sure if that's easy to do.
Comment #6
Daeluin CreditAttribution: Daeluin commentedsubscribing
Comment #7
chaloum CreditAttribution: chaloum commentedThe patch didnt seem to change the text formatting still plain text
Comment #8
David_Rothstein CreditAttribution: David_Rothstein commentedAh, right, when you view the description after the update it actually will fall back to plain text (since the format is stored as NULL in the database).
The bug I'm thinking of is actually when you go to edit the description for the first time after the update; there, the wrong format will be selected by default (plain text won't be selected, but rather the user's personal default). But that's not quite as serious and really more of a general bug for Drupal core to deal with, in cases where text formats are switched on for a field that's already in use. So this patch seems like it will be good as is.
Comment #9
sunWrong indentation.
Trailing white-space.
Duplicate __ ?
Powered by Dreditor.
Comment #10
keha3912 CreditAttribution: keha3912 commentedor ckeditor...
Comment #11
effulgentsia CreditAttribution: effulgentsia commentedThanks. Committed with #9's corrections: http://drupalcode.org/project/media_gallery.git/commitdiff/8192e20?hp=b6....