For some reason all my thumbnails are showing up super-narrow, as shown in the attached picture. This occurs both within an album and when looking at all albums I have in Acidfree.
I tried changing my Theme, but I have the same issue in Garland. I also tried disabling Outline and TinyMCE which are my two other "problematic" modules. Always the same result.
Not sure if it's related but I also had another issue, with a 500 Server Error and it seems that a bunch of the files were created twice. But I'll post that separately. Looks like another guy had a 500 error so I'll put it there.
Thanks,
Patricia
| Comment | File | Size | Author |
|---|---|---|---|
| Acidfree-mini pics.jpg | 23.29 KB | PRFB |
Comments
Comment #1
hd commentedExperienced the same problem with an old modified Bluemarine theme.
Comment #2
skizzo commentedHad same problem with album
display. Solved as described in
http://drupal.org/node/155791
Comment #3
Critical Tinkerer commentedI have the same problem and have tried it on Bluemarine and Zen. It seems to be a problem in acidfree.css.
Here are some screen captures:
http://www.photongraphics.net/drupal/
The first capture shows the top level album view. The third capture is the the view of a single album.
The second capture shows the inspector of Firebug (a Firefox plugin) and seemed to indicated that the clipping occurred in div.acidfree-cell < div.clear-block (blue highlighted) or in div.acidfree-cell < div.clear-block < div.content (yellow highlighted).
However, fourth capture would seem to indicate the that clipping is occurring in div.acidfree-cell.
Hope this helps.
Comment #4
Critical Tinkerer commentedFor the record, all photos where uploaded after upgrading to image-5.x-1.3 and running update.php. Acidfree-5.x-1.x-dev, was downloaded and re-installed yesterday.
Comment #5
vhmauery commentedFor reasons not entirely clear to me, the default Acidfree theme sets a fixed height and width to each cell. I am not a CSS expert by any means. I could probably make things look right in one browser on one platform, but I didn't write the theme, which does look great on all browsers and platforms. But in order to set the correct fixed sizes, it reads in the information from the image module. However, if the Image module returns sizes of zero for whatever reason (forgetting to run update.php, a botched install, API incompatibilities, bugs in Acidfree, etc.) Acidfree will create a div that is zero plus padding in height and/or width. This is why hardfocus is seeing wide and short thumbs (I bet you left the height setting empty in the Image settings). As for PRFB's issue, I am not sure, but the first thing I would do is ensure that the image module settings are correct.
I am not sure that Acidfree can support only having one of the Image size fields set. Only one set means scale the image so that it is that width or height and does not give information about what the other dimension will be. If you want images to be no bigger than 100 on each side (but keeping aspect ratio), set both height and width to 100. This gives the Acidfree information that it needs to create a proper bounding box around the thumbnails.
I will add this test to the items Acidfree looks at when running acidfree/test
Comment #6
Critical Tinkerer commentedvhmauery on July 22, 2007 - 05:23:
...Acidfree will create a div that is zero plus padding in height and/or width. This is why hardfocus is seeing wide and short thumbs (I bet you left the height setting empty in the Image settings). As for PRFB's issue, I am not sure, but the first thing I would do is ensure that the image module settings are correct.
Well, you hit the nail on the head. I added in the width setting and that fixed everything. Fo the record, the only reason I left it out was the following:
Quoting from admin/settings/image:
It seemed logical enough to me to leave it out, based on the above, so that's what I did. Anyway, at least I have a fix. Thanks!
Comment #7
fax8 commentedHi Vernon,
I also experiencing this problem. I think that this is a CSS or generated XHTML issue as images sizes and div sizes
are correctly hardcoded on the generated XHTML here (from thumbnail sizes).
So .. I think this is probably something related to incorrect behavior of some css rules.
Fabio Varesano
Comment #8
mwheinz commented