Friday, June 09, 2006

Click on photo to enlarge question

Soon after I started my blog, I switched from a PC to a new Mac running OS 10.4.6 When I uploaded photos from my PC, you could click on them and enlarge them. With the uploads from iphoto, when you click on the photo, the size remains the same. I looked at the code for both and it is somewhat different, but changing the new code to match the old didn't fix the problem. It seems that iphoto is defining the size of the photo because when I click on the photo it brings up an image name and the size 360x270 pixels on my Safari tab.

I don't know if this is an iphoto issue or a blogger/iphoto/safari issue. I'd like people to be able to click and enlarge on the photos if possible, so if anyone could enlighten me on this, it would be much appreciated.

Thanks in advance,
Catherine


This Post was written by Catherine from Albion Cooks

7 comments:

Sam said...

Hey catherine - can you explain how you upload the photos to blogger (I only ask because there are a few different ways you can do it, but i guess you are no longer using picasa or hello?

Cindy said...

I'm also using a mac since a couple of weeks now. before I used to upload photo via the blogger thing, but now since on a mac I use flickr (which I kept on using for my logos). I paste the html code of the medium size and put a link (clicking on the image and then on the link thing) to the url of the bigger photo. Therefore when people click on the image, they see a bigger photo.

Catherine said...

Hi Sam,

I'm using the blogger upload image button.

Cindy - thanks for that - I have a flickr account but have only used it when I couldn't get the picture to upload oriented the right way. If I can't figure out something easier, I may go that route.

Sam said...

Ok - so I normally use Hello or Picasa so I just went and tried a test using the upload image button as you would do. I selected "image size large" and it gave me the following piece of code:

<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://photos1.blogger.com/blogger/267/407/1600/IMG_7941.jpg"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://photos1.blogger.com/blogger/267/407/400/IMG_7941.jpg" border="0" alt="" /></a>

You will see there are two references to an url that starts with photos1.blogger.com = exactly the same as you. Then there are a couple of numbers which are your unique id. the last number in this case is 400 or 1600 [320 or 1600 if you had loaded at medium res]. I believe this number referes to the x resolustion (number of pixels running horizontally) in your image.

The code is basically telling blogger to put the 400 width image in the blog, but to show the 1600 width image when the picture is clicked on (so you see a larger image when click on the picture). This is what you want.

Now when I do this from my PC this works just fine. So I don't think the problem is with blogger.

For some reason when you do this from your mac it seems it loads the 1600 width picture with the correct name, but with actually a smaller image and i am afraid i don't know why that is happening for you because it works fine for me.

I couldn't find anything about it in the blogger know issues section of their site. Maybe you need to write and ask them? They do recommend Mozilla Firefox for Mac users, not sure if that might make a difference for you?

blogger known issues web page

Sam said...

Maybe you have some kind of image limit size setting on your apple somewhere? Since I dont have a mac to test it, I am only guessing?

Catherine said...

Hi Sam,

I appreciate your help on this. I will bug the Apple guys and see if they know what's happening here.

Thanks again,
Catherine

Catherine said...

I've finally solved this. I was uploading photos directly from my iPhoto library . If I export the images from iPhoto to another folder on my Mac and then upload them from that folder, it opens a full size version when the posted photo is double-clicked. Weird, but at least there's a work around.