Closed (fixed)
Project:
Image Class
Version:
7.x-1.0
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Apr 2014 at 17:54 UTC
Updated:
31 Aug 2014 at 16:56 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mario steinitzComment #2
Anonymous (not verified) commentedI agree I have the same problem here. After testing your patch it works. Danke Mario
Comment #3
mario steinitzNow that the project using this module is done, here's the refined and cleaned up version of my above patch.
It has corresponding remarks added and forces class strings to be applied as array. The latter was necessary due to problems with a theme function applying further classes to images.
Comment #4
Angry Dan commentedThis patch really needs a commit, no? The module is ineffective without it.
Comment #5
markchitty commentedAgreed, dead in the water without it.
Comment #6
yannickooThanks for the patch!
There is a question: Why should
$settings['class']be an array? I will commit a patch ASAP but I don't get why you are checking for an array. Could you please explain that?Comment #7
yannickooShould be fixed with a4baf33. Please test the next dev version of Image Class so that I can release a new version ASAP.
@Mario could you please explain the array thing anyway?
Comment #10
mario steinitz@yannico:
Sry for the late reply. I've been busy with some other projects recently.
Unlike in D6, the Drupal 7 render arrays use an array of classes for the class attribute.
We had some other modules within the above project, that already stored the display setting 'class' as array. (I honestly can't remember which ones...)
So checking for/handling an array while looping over ALL fields was necessary, to prevent some nasty PHP exceptions.
Best regards
Mario