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.
Minor maintenance update for ImageField for Drupal 6. This version increases compatibility with PHP 5.3 and fixes minor notices. Upgrading is recommended for all users of ImageField.
Changes since 6.x-3.10:
#1215730 by qtbeee: Terminology update: don't say "Resolution" when we mean "Dimensions".
#1146670 by kenorb: ImageField: PHP 5.3 compatibility for tests.
#1142620: imagefield_widget_validate does not exist.
The 3.10 release of ImageField is an extremely minor update to make ImageField match its parent module FileField's version. As always, be sure to upgrade FileField and ImageField to matching versions.
The 3.9 release of ImageField fixes a critical bug that would prevent images from displaying if using the PressFlow Drupal distribution. As usual, ImageField 3.9 must be updated at the same time as FileField 3.9.
The 3.8 release of ImageField is being released to match the 3.8 version of FileField. Both modules should be updated at the same time. The 3.8 version of FileField fixes a major problem that would prevent Google Chrome users from being able to upload a file. This version of ImageField also fixes several minor bugs.
This version contains no new changes since ImageField 3.6. It is being released to match the 3.7 version of FileField. See the ImageField 3.6 release notes.
This release provides compatibility with the changes to the SimpleTests included in FileField 3.6. Other than that, it includes some minor fixes and prevents the module from accidentally disabling itself when updating other modules. Note that there are no ImageField 3.4 or 3.5 releases. The use of 3.6 is intended to match the current FileField release version.
This version of ImageField fixes two security issues related to setting up a new field and access to the thumbnails generated on the node form. It also makes a few corrections regarding administrative tasks and files with non-Latin characters.
This version of ImageField fixes problems discovered after 3.1 was released. Note that you should always maintain ImageField and FileField with the same version numbers, so be sure to download the latest version of FileField also: http://drupal.org/project/filefield.
Final release of ImageField for Drupal 6 to correspond with the FileField 3.0 release. This is a minor update from RC1, no database updates necessary. FileField module must be upgraded to version 3.0 at the same time.
This release of ImageField corresponds with the RC1 release of FileField. While not necessary to upgrade both simultaneously, it is highly recommended that FileField is updated at the same time with this version.
This version adds the "Default image" feature back to the Drupal 6 version of ImageField.
This version of ImageField fixes a few critical issues and several minor cleanups. We're shooting for a final release of FileField and ImageField next week, you can help by testing out the latest versions of ImageField and reporting any problems to the ImageField Issue Queue.
This release contains no new database updates from beta2. Though any users updating from an alpha version are strongly encouraged to make a database backup before upgrading.
This version improves upon the bug fixes in beta1 and is very close to a stable release. There are no known issues with this release and APIs are solidified. Please file any problems with this version to the ImageField queue.
Upgrading to FileField Beta2 at the same time is highly recommended, but not necessary.
This release is identical to the 2.5 release but fixes a bug in an update function that caused the update to fail if using table prefixes. Because the 2.5 release was available for such a short time, I'm including the previous version's change log also.
The beta1 version of ImageField for Drupal 6 fixes a significant number of bugs and adds a few new features. FileField beta1 must be updated at the same time for this version to work. Users of the alpha versions of ImageField are encouraged to upgrade with caution (make a backup of your files directory and the database). New users should definitely use this version. Users upgrading from Drupal 5 should definitely use this version also, since it fixes the upgrade path from Drupal 5.
#130701 by DarrenOh, Cannot see the image in Preview. I'm not really maintaining this branch per se, but I'll take Darren Oh's word that the patch is a good one.
Totally a super alpha release that just barely works. It'll probably break your site, crash your server and burn down your house so MAKE A BACK UP OF YOUR FILES DIRECTORY AND YOUR DATABASE!
BUG: Fixed Default Value / Default Image fieldsets
BUG: Fixed Default Value Display
BUG: Improved Tokens table appearance on field settings form
BUG: Added node param to hook_field_formatter
FEATURE: Added Max Number of Images setting for multiple values.
Default image support should be fixed now.
There should be an Empty Image filter for views now.
The delete checkbox value should be maintained between uploads.
Development version of the new imagefield 2.0. This version includes ajax-upload, token support and other features. While unstable, this version is receiving all new fixes and features. Please try this version before requesting a feature.
This release brings most of the features from imagefield 5.x - 1.x to imagefield for 4.7.x - 1.x.
changes
-per field directory support
-imagecache integration per field for cck <= 1.2
-custom alt and title field support
-support for private files without enabling upload.module
There were several issues with imagefield 5.x-1.0 and cck's new default values handling.
The 1.0 release only seems to work with CCK <= 1.2. This release should work with 1.3.
This is the 5.x development release. Pending further cross platform testing I will make a stable release.
If anyone has windows servers can can confirm the module is working with apache and iis I would appreciate it. Also testing against pgsql would be appreciated, but content.module itself doesn't support pgsql well currently so be warned if you're testing.