Hi Alex, Aaron,
I'm working on a site for my wedding, planning on using Feed API to pull Flickr content to one page. I'm setting up the Flickr emfield right now and suddenly something has happened where I can't change set the height field to 0.
When choosing a width and height for the field dispaly, the note says I can set to zero to maintain the aspect ratio. But when I set it, it defaults back to the past value that I had changed it from. The help text says:
"These settings control how this image is displayed in its full size, which defaults to 500x800. Note that if one of the dimensions is 0, then the image will be resized to be no larger than the other dimension."
There is no error message text. When I the value to zero, it doesn't stick on submit. And I swear it was working right just a second ago.
Comments
Comment #1
davidhk commentedHere's a patch that solves a slightly different issue, but may work for you too: http://drupal.org/node/383274
With that patch if you set width & height, eg 640 x 640, then the image will be scaled to fit that box while preserving it's aspect ratio. So if you have a mix of portrait and landscape format pictures, they will all have the same area when displayed. (With the 'set one dimension to 0' approach, portrait & landscape images are displayed at very different sizes, which looks odd to me).
Comment #2
stattler commentedI am having the exact same problem. That is, the settings get saved but whenever I revisit the settings page, I would need to re-input all the values. Otherwise it goes back to the default values. This happens for the "height" field only, though.
Comment #3
seaneffel commentedIs this happening for all the values you set for the height? Its been happening for me but only when setting the height to zero.
Comment #4
stattler commentedI didn't try other values, but its happening for me when I set the height = zero.
Comment #5
jcmarco commentedFix for that issue:
#416790: Fixed bug in widget form that break aspect ratio configuration
Comment #6
seaneffel commentedjc, that patch solved the problem for me. I'm going to mark this as a dupe and followup on that other issue:
http://drupal.org/node/416790