Album Picture Limits

[Piru]

Code: [Select]

Maximum File Size per Picture   97.7 KB
Maximum Picture Dimensions 600 by 600 Pixels
That sucks IMHO.

Could the limits be made more sensible?

[Karlos]

That is a bit weak. I wonder how much storage the old gallery images require between them?

[RRunner]

Code: [Select]

Maximum File Size per Picture   97.7 KB
Maximum Picture Dimensions 600 by 600 Pixels
That sucks IMHO.

Could the limits be made more sensible?

Yea, it is a little limiting. I uploaded a screen capture of the old site and had to size it down to 600 x 600 which makes it very hard to see.

[GadgetMaster]

That is a bit weak. I wonder how much storage the old gallery images require between them?

Maybe it is a default setting and  needs to be tweaked yet.

If it is server space issues I wonder if the gallery can be hosted externally like on FliKR or something and linked to like people do with youtube vids.

[EDIT]

Her's one way to do it:

http://www.internaldrive.com/2009/04/30/integrating-flickr-with-vbulletin/

[Wayne]

Code: [Select]

Maximum File Size per Picture      97.7 KB
Maximum Picture Dimensions         600 by 600 PixelsThat sucks IMHO.

Could the limits be made more sensible?

Ok,

I just figured out that part of my problem with my recent "grumpyness" is stress.  The other part is that I don't respond well to passive aggressive, which the original post in this thread is.

That being said, I've changed the defaults to 1280 x 1024 / 300000 bytes.

With each person being able to upload 100 images, let's put that into perspective:

300,000 bytes x 100 = 30 megabytes of storage for each person's private album.

With over 900 active users, 900 x 30 megabytes is 27 Gigabytes.

I suck at math, but I believe that's right.  Anyway....

Should this become a problem for the site, we have three solutions:

1) Make private albums only available to VIP / Donors to the site (you know, the people who actually pay for the bandwidth)

2) Disable private albums altogether.

3) Increase the monthly donation needs to cover a dedicated server with sufficient hard drives not to care any more.

(Since #3 still requires donors, providing freebie amounts of space to people who don't donate doesn't make a lot of sense to me).

I had hoped we could use them as a great way to keep our members happy, but we'll need to just wait and see how things go.

Wayne

[RRunner]

I'm just thinking out loud here...

One solution may be to create an "Image Gallery" forum. Each "topic" would be for an image post. Instead of hosting the pictures here, the pictures could be linked to an outside photo source. There are LOTS of free and reliable image hosting sites such as the previously mentioned Flickr. If Flickr is utilized, an "Amiga.org" photo pool could be set up that users could add images to. A widget could be created on the home page that randomly shows images from this pool. Not sure how difficult that would be though.

Pros:
- Easy to implement, just add a forum called "Image Gallery"
- Image storage is external so no extra space needed

Cons:
- Users need external accounts to image hosting sites
- Posting an image to the "gallery" is a multi-step process (upload to hosting site then post here)
- Lack of control over the external images... if the external site goes down or its structure changes, the image links may break completely

[Piru]

I tried to upload a picture somewhere else but it complained it wasn't in my user gallery, so it would not add it. That's a bit weird IMO. Personally I don't need any galleries for myself, I just wanted to add the picture elsewhere. It could well be that I don't quite know how to use the new board yet. Ah, this was it:

You may add pictures to this group from your albums. Paste the URL of each picture you want to add on a separate line. Alternatively, you can add pictures to this group by first viewing them in your albums and then selecting "Add Pictures to Group".

Why the pictures need to be put to some private user album before they can be posted in groups is beyond me. This doesn't quite make sense IMO.

As for the passive aggressive. I'm sorry if it came out that way, it wasn't intended as such. It was meant to be plain observation of facts.

Now, I must add that you guys have done excellent job moving a.org to the new CMS. Such work is never easy, and it for sure generates tons of stress. However, this forum is called "Suggestions and Feedback", and this is what I used it for.

[freqmax]

One solution for storage space is to remove those images that is viewed fewest times. Or send them to shrink hell

[cv643d]

Hi,

I get the following error when uploading a picture (75kb 800x600 JPG).

Warning: move_uploaded_file(/home/amiga84/public_html/gallery/images/1091/1_wb41_pegasos2.jpg) [function.move-uploaded-file]: failed to open stream: Permission denied in /home/amiga84/public_html/gallery/upload.php on line 171

Warning: move_uploaded_file() [function.move-uploaded-file]: Unable to move '/tmp/phpOsET9y' to '/home/amiga84/public_html/gallery/images/1091/1_wb41_pegasos2.jpg' in /home/amiga84/public_html/gallery/upload.php on line 171

Is it the same problem?

[Karlos]

That must have only just happened then. It's a simple directory permissions error. The directory is not currently writeable by apache.

-edit-

Bug report filed.

[Wayne]

That must have only just happened then. It's a simple directory permissions error. The directory is not currently writeable by apache.

-edit-

Bug report filed.

"Replacing permissions on 17,407 files, please wait...."

Really, it's expectable.  The backup utilities gzip up the files, but have little to do with the CHMOD permissions on each file/directory as they're replaced, so I expect to find a few of these type problems, easily fixed, though annoying as hell.The best we can say is that "at least the swapover is done"

[Karlos]

"Replacing permissions on 17,407 files, please wait...."

That actually wouldn't take long on the commandline. +1 to bash

[Wayne]

That actually wouldn't take long on the commandline. +1 to bash

Nope but as a security precaution, there is no shell or telnet access.  Keeps all the kiddies out.

Wayne

[Wayne]

There may be an image or two missing from before I figured out what was happening, but the gallery should now be back to where it was.

1) When the swapover happened, apparently some of the 16000+ files didn't get transferred, which is normal if the tech helping was using FTP without the verify option enabled.

2) The uploaded images were given the wrong CHOWN ownership, and the wrong CHMOD permissions by the system which I could not correct until the ownership issue was corrected by the techs.

I have manually re-uploaded all the images again, skipping the ones already in place.  While this took several hours, it should have replaced all the missing images, and they should now have the right permissions/ownership attached.

Leech away..

[buzz]

Nope but as a security precaution, there is no shell or telnet access.  Keeps all the kiddies out.

That is what passwords are for I'd take a commandline chmod (few seconds), over some ftp/cpanel approach anyday!