Desperate for help!

[paulket]

The following has been copied and pasted from vBulletin.com where customer support is the worst that I have ever experienced. I have gone from being annoyed and frustrated to being angry. I cannot wait 24 hours between asking questions to get help with this problem:

My uploaded images keep being re-sized smaller for no apparent reason... for instance if I upload a picture from my computer to an album or post that is 800px wide, it was some times getting uploaded at 800px, some times at 750px and recently at 620px or 518px. I tried globally turning off plugins and it made no difference. If I upload pictures to a folder on my server and then use image tags in a post they are shown at the correct size. This is extremely frustrating and annoying! I'm using a fresh install of vBulletin version 4.1.8 and this happens with a custom style or the default. Any help with getting this issue solved will be appreciated greatly. Link to my site http://panaworldonline.com/forum.php

------------------------------------------------------------

My site is dedicated to travel and photography, I need to get this taken care of as soon as possible. I can't ask people to join if they will be unsure of what size their uploaded pictures will be and I can't start new threads that will have pictures in them with different sizes... which is almost all of them.

All of the pictures in this album were the same size BEFORE being uploaded and now none of them are the same size http://panaworldonline.com/members/paul-albums-sinaia-romania.html

[kh99]

I don't really know anything about how images are handled, but (from your vbulletin.com post):

The image sizes set in the config.php are much larger than what the uploaded images are on my site.

and according to the comment in config.php

// Images that exceed either dimension below will not be resized by vBulletin. If you need to resize larger images, alter these settings.


so maybe you should *reduce* those dimensions in your config.php. (Or maybe the comment is wrong...)

ETA: which version do you have installed? It looks like maybe the values in config.php aren't used in version 4.1.8

Would you be willing to attach a zip of the original images in the album you linked to, so I can try uploading them?

[paulket]

Thank you for the reply, kh99. I'm using version 4.1.8. The dimensions in the config.php shouldn't be resizing images randomly that are much smaller than what is stated in the file, should they? For instance, the dimensions say:
$config['Misc']['maxwidth'] = 2592;
$config['Misc']['maxheight'] = 1944;

Why would an image that is 800px wide be re-sized to 518px wide in one upload or maybe 750px in another upload?

[kh99]

I really don't know why it's resizing at all to be honest. But it doesn't make sense to me to *not* resize images that are *larger* than the given dimensions, but that's what the comment seems to say. But as I added in my post above, in 4.1.8 it doesn't look like those values are used anywhere (the line has been commented out).

Are you able to provide those original images for testing? If not I can probably find my own somewhere.

ETA: Don't worry about it, I'll just resize some images to 800x533.

--------------- Added 1323027606 at 1323027606 ---------------

In your attachment manager, what do you have for maximum file size, width, height for each file type? To answer your above question, I think you could end up with "randomly" resized images if you have the max file file set to something small, because it looks like the code first resizes the image if necessary to be within the max dimensions, then resizes again if the file size is > the max.

BTW, when I did a test with 5 .jpg images that were all 800x533, they all ended up the same size but larger than the originals (I haven't quite figured out why yet).

[paulket]

But as I added in my post above, in 4.1.8 it doesn't look like those values are used anywhere (the line has been commented out).

I just downloaded 4.1.8 again from the vBulletin.com customer area and at the bottom of the config.php(.new) file it says:

Images that exceed either dimension below will not be resized by vBulletin. If you need to resize larger images, alter these settings.
$config['Misc']['maxwidth'] = 2592;
$config['Misc']['maxheight'] = 1944;

But the problem is not having images that are too big re-sized, it is having images that should be uploaded at their original upload size kept from being resized. Maybe my frustration with the issue is keeping me from understanding what you are saying.

[kh99]

IBut the problem is not having images that are too big re-sized, it is having images that should be uploaded at their original upload size kept from being resized. Maybe my frustration with the issue is keeping me from understanding what you are saying.

I'm saying that the comment sounds like it *won't* resize images that are larger than the dimensions shown there, so if you didn't want images to be resized, you would want to reduce those values. However, like I said above the values don't seem to be used, and it could well be that the comment is wrong or I'm misunderstanding it.

What do you have in your attachment manager for max dimensions and file sizes? Maybe post a screen grab of it if you can. If I can reproduce the problem you're having then I might be able to tell you why it's happening.

[paulket]

Here is a screen shot from my attachment manager. Your assistance is appreciated a lot, kh99.

[kh99]

Well, I set mine up like yours and I can't really reproduce your problem. But what I do see is that 4 images were rsized from 800x533 to 820x553, and one is smaller (the Train image) because it is larger than the 100K limit. So the only thing I can think is that maybe your original images (which I'm assuming were all of type .jpeg) were much larger than mine and so got resized to reduce the file size. Maybe try increasing the max file sizes and see what happens.

[paulket]

All of the image file size maximums have been increased to 1000000, the system cache was cleared and the problem still persists. This has only been a problem recently, when I first installed vBulletin the images were uploading at the correct size.

[kh99]

When you say the problem still persists, you mean when you upload new files they get resized, right? Because of course it won't fix files that were already uploaded.

I'll look at the code again and see if I can see anything else.

[paulket]

When you say the problem still persists, you mean when you upload new files they get resized, right?

Yes, each time I upload a new test image, it is a new file that has not been used before.

It took me a while but I finally caught on to the random size being related to the image file size. I've looked everywhere I can think of and have not been able to find anything limiting the size so low.

[kh99]

OK, try this: in the adminCP go to Attachments > Attachment Permissions, and check to see if any custom permissions have been set for a user group (should show up in red).

[paulket]

OK, try this: in the adminCP go to Attachments > Attachment Permissions, and check to see if any custom permissions have been set for a user group (should show up in red).

Nothing is in red. Test pictures are being uploaded at completely random sizes regardless of their file size. I just uploaded one at the correct pixel size that has a file size of 94kb and right after that I uploaded an image that 95kb it is shown in much smaller dimensions. 1kb shouldn't make the image 50 pixels smaller. This is ridiculous and I'm ready to demand a refund from vBulletin.

--------------- Added 1323049924 at 1323049924 ---------------

EDIT:

It seems the issue has been solved by someone who sent a PM and may wish to remain nameless. In the admin control panel I turned off image the resizing option and then increased the allowable file size well past 1000000 in the attachment manager.

A very big thank you goes to this anonymous person who sent the PM and to kh99 for their help.

[kh99]

Oh right - I should have thought of turning off image resizing. Good work, whoever that was.

Anyway, glad you solved it.