Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I made a number of changes to my installation of image.module and wanted to share. Here's what I added:
Image frame path: [text]
Path to the directory, relative to your Drupal installation, containing the frame images to be used for the full size images. If this value is empty it is ignored. The frame is constructed from the specifically named images in the said directory (9images). A picture is worth a thousand words, so see the bottom of the attached screen shot.
Image thumbnail IMG style: [text]
CSS styles to include in the DIV tag for thumbnails. This will style the image tag if present.
Image thumbnail DIV style: [text]
CSS styles to include in the DIV tag surrounding the entire thumbnail. This will apply a style to the entire thumbnail, which includes the title and the description (see the next two changes). This combined with the IMG DIV allows you to create polaroid-style thumbs. Again, see the screenshot.
Thumbnail Titles: [yes|no]
Should the image title be displayed underneath the thumbnail image?
Thumbnail Descriptions: [yes|no]
Should the image description be displayed underneath the thumbnail image?
If anyone is interested, I'll post it.
---
Ben
| Comment | File | Size | Author |
|---|---|---|---|
| image-module.jpg | 62.12 KB | abelware |
Comments
Comment #1
Icarus-1 commentedPlease do, these all sound like things I'd want to use.
Thanks
Al
Comment #2
bruno commentedI'm also interested. It's looking great. But I'm wondering if using a customized version of image module's theme functions in your theme isn't a better approach. I have concerns that we end up with an infinite number of options for image rendering in image.module to suit all needs ;-)
Comment #3
abelware commentedbruno:
> I'm wondering if using a customized version of image module's
> theme functions in your theme isn't a better approach.
I was wondering what you guys thought, which is why I didn't initially post my module or a patch. I am somewhat new to Drupal (a couple weeks) and am just now piecing the whole puzzle together. I didn't mess with my theme (Interlaced) because there is nothing image specific in there and the module is what lays out the images. So my way was the most expedient way of accomplishing the task. It may or may not be the best way.
The admin changes were extremely simple and the changes for the other options were just a few if { . . . } statements. No database or theme changes were needed. If all those fields are left blank, they are ignored.
Thinking about it a bit, using a customized theme requires that the user hack up their theme, whereas all of these options are available entirely through the web interface and have no effect if they are not used.
Ben
P.S. I also added an admin field to control the text (or none at all) that is shown in the navigation bar at the top.
Comment #4
inquilab commentedplease post your hacked image.mod- sounds good, I was trying to hack image.module as well, it does require tons of development still...
prateek
Comment #5
inquilab commentedplease post your hacked image.mod- sounds good, I was trying to hack image.module as well, it does require tons of development still...
prateek
Comment #6
nautis commentedI dig it. Hope you post it somewhere to download.
- Matthew
Comment #7
Stefan Nagtegaal commentedThanks to Walkah's image-api/module this doesn't have to anymore... Mrking as fixed
Comment #8
(not verified) commented