Max Image Size (MB) - Gallery

by Jade Undone on Sun May 18, 2008 7:35 pm

I have my gallery limit set to 1mb. Yet people are still able to upload images larger than this.

One real problem is we are playing an online role playing game and they upload uncompressed image files from the game's screenshot folder. Some of these files are in excess of 15mb. As you can see this really eats up my money well spent on expanding my gallery capacity. Can we have this feature looked into and fixed asap. We're quite active and large, more than 270 members, 16000+ posts in less than 80 days, hence the urgency. Thanks. http://hammerfistclan.darkbb.com/index.htm

by **Sunny_D** on Mon May 19, 2008 5:17 am

I'll move this over to the Tech-section.

Additional Info: I have noticed this recently as well. The width / height restriction seems to work properly, but not the filesize limits.

Furthermore, if you are trying to change the filesize limit in "Modules / Gallery / Upload", the value jumps to 0.00 everytime you hit save. It jumps to 1 if the entered number was 1024 (512 returns 0.5 etc). It's displayed (only displayed!) correctly nearby the input field where you upload images, but it has no effect.

by travis_cooper on Wed May 21, 2008 10:05 am

This happens in mine as well. If the width or height is longer than what you specify the upload does shrink the picture down to your dimensions, but if the width and height are okay, but the filesize is too large, then it just uploads as is.

by dragonfir731 on Sat May 24, 2008 4:11 pm

it is happening with my test board too.

Drag~

by Jade Undone on Wed May 28, 2008 3:09 pm

So it's been an age and a day, is this resolved?

by Jade Undone on Tue Jun 03, 2008 4:50 pm

Oh brother...

Post date vs. today's date.
That's all I have to say atm.

by Jade Undone on Thu Jun 05, 2008 11:54 am

My original complaint/tech issue was filed May 18. It is now June 7th.

I've been more than reasonably patient, now I'd like some service, as I am a PAYING customer. A little feedback on the progress you've made thus far would be NICE.

by sunburnedpenguin on Fri Jun 06, 2008 9:22 am

I am having the same issue with lack of support. Seems to be a running theme. I wish you luck in getting this resolved as it seems, paying or otherwise, the issues we have are just ignored.

by Jade Undone on Tue Jun 10, 2008 10:50 am

Any word on this? It's been weeks now. Some feedback, any at all would be greatly appreciated before I go through the trouble of escalating this issue.

by Jade Undone on Mon Jun 16, 2008 2:21 am

by travis_cooper on Mon Jun 16, 2008 9:21 am

I too wish that we could receive some response to this issue. Are the techs even aware that this is a problem, are they working on it, are they just too busy right now and this is lower priority? What is the status here, a little feedback would be greatly appreciated.

by Jade Undone on Sun Jun 29, 2008 11:55 pm

Ok now I'm starting to really get upset. Wtf is going on, and why haven't we heard any response on this. SOME sort of communication would be nice here. Evil or Very Mad

Almost SIX weeks, and not a word.

by **Sunny_D** on Mon Jun 30, 2008 1:13 pm

Jade, I wonder that you are still having problems, I thought this has been solved with the new admin panel or earlier already - for me, it is working perfectly fine since then.

I can limit the filesize for uploaded images and if I upload a bigger one, I get the message "Your image is corrupted or too large". The value that you define in your admin panel doesn't reset anymore as well... As I had the same problems as you in the beginning, so I assumed the issue was gone.

Have you actually tried it recently again?

by Jade Undone on Sun Jul 13, 2008 12:27 am

After 2 months without so much as a "we're looking into it" I had all but gave up. I'll give it a test.

by katanga on Fri Jul 18, 2008 1:24 am

I'm having similar problems...

by travis_cooper on Thu Jul 24, 2008 5:20 pm

I just tested this out, I get the error message now. It says that the filesize is too large or corrupted. I'm glad that somebody came and told use they had fixed this issue.