max_pic_size not working / prev&next image buttons look weird

I have the following code for my gallery:



but when I click on the image I get the original uploaded size.
Also when I’m actually viewing the image, the prev and next image buttons look messed up: they use up the entire image height and about half of the image width.

Help!

You have &max_pic_size=`0` in that snippet call (it’s actually used twice on the call). That makes maxigallery to store the original size images. When you change the parameters that affect pictures, you have to re-upload the pics.

The messiness of prev/next links is probably because of a css collision between your site css and slimbox css.

Quote from: doze at Jun 01, 2009, 02:30 PM

You have &max_pic_size=`0` in that snippet call (it’s actually used twice on the call). That makes maxigallery to store the original size images. When you change the parameters that affect pictures, you have to re-upload the pics.

The messiness of prev/next links is probably because of a css collision between your site css and slimbox css.

Thanks, good catch with the parameter appearing twice. Kind of silly. I fixed it and now when I upload a relatively small image it seems to be scaled down, but when I upload a large image (a 2000x2000 photo) I just get a blank page. The same photo upload worked before I corrected the max size. Is it running out of memory when resizing or something like that?

Any suggestions about debugging css collision? I looked at it with web develoepr plugin in Firefox and don’t see anything.

Actually I just looked at slimbox.css and see this:



so it is explicitly set to 50%?

Quote from: meshko at Jun 01, 2009, 10:26 PM

but when I upload a large image (a 2000x2000 photo) I just get a blank page. The same photo upload worked before I corrected the max size. Is it running out of memory when resizing or something like that?

Yes, that would be my guess. Check the maxigallery wiki page for information on server settings that you could try to change.
Quote from: meshko at Jun 01, 2009, 10:26 PM

Any suggestions about debugging css collision? I looked at it with web develoepr plugin in Firefox and don’t see anything.

Not really... Don’t have time to check the specific issue.. But what you can do is simply comment out everything from your site css and bring it back one block at a time to see where it breaks. Then try doing a more specific css setting to your site css.

OK, I traced the problem to this style in our main css file:

A:hover {
BACKGROUND-COLOR: beige; COLOR: #006699; TEXT-DECORATION: underline
}

in particular the background-color property. I can’t make it more specific in our CSS, really. What does slimbox want the background color to be?

I don’t know.. Look at slimbox css file. I’m not really giving help for the 3rd party components that MaxiGallery uses.. there are help forums for slimbox itself. But I guess you could modify slimbox to have some id’s for the link elements, if it doesn’t have them yet, then add css to slimbox css file to override that your "global" setting.