Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Currently, if you turn off the 'allow custom thumbnails' for a field, it still appears on the edit form. We need to respect the setting. However, we'll also need to make sure we still read thumbnails if it's been turned off for a field, because of how it's tied into remote thumbnails now.
Also, even if the form's not displayed, we still need to capture and store remote thumbs when that's allowed.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | emthumb-377744.patch | 1.93 KB | andrewlevine |
Comments
Comment #1
alex ua commentedWe need to check and see if this has been fixed by the emthumb issues.
Comment #2
andrewlevine commentedThis has actually not been fixed...will try to get a patch for this next week.
Comment #3
andrewlevine commentedThere are 4 permutations based on two field settings ("Store remote thumbnails for this field" and "Allow custom thumbnails for this field") in which emfield should act differently. 3/4 were functioning properly. Patch fixes behavior
1. Neither is checked. Emthumb does nothing. Already working
2. Both are checked. Emthumb will download remote thumbnail and store it unless a custom thumb is uploaded. Already working (But I added a blurb in the fieldset that explains this behavior)
3. Just store remote thumbnails. Emthumb will download remote thumbnail if available. This was confusing because an empty fieldset would be displayed if there was no thumbnail available. (But I added a blurb in the fieldset that explains this behavior).
4. Just custom thumbnails (not remote). Already working
Comment #4
andrewlevine commentedActually I believe case 1 would display an empty fieldset also...but the patch takes care of that too :)
Comment #5
aaron commentedcommitted. thanks!