limit photo size per role

The combination of limiting the number of photos and the ‘resize on upload’ feature ( Table I-A2 and I-A3 ) enables you to limit diskspace. Not to the kb exact, but a downsized picture to, say 640×480, will most likely never exceed 200k. The max number is better acceptable for a user than diskspace, which might encourage them to upload photos of bad resulution and/or jpg compression.

Thanks for the quick reply as usual.
Sorry for my late reply, but I didn’t have any spare time to continue with it.

Limiting the number of photos is an option as well, but in that case I would like to implement two limits per role.
In table VII-B3 I can either limit the number of photos per day or the number of photos “for ever”.

Would it be possible to have two limits for one role?
1. limit the number of photos to 3 per day
2. limit the total number of photos a user can have to (let’s say) 50

Kind regards,
Dirk Claesen

I do not see why a user should not be allowed to upload them all ( 50 ) the day, ( and replace some later if he likes ).

I would like to limit the number of photos one user can upload per day to avoid this user fills the entire front page of my website (the most recently posted photos). By allowing one user to only post maximum 3 photos, I give the opportunity to the other users to also post some photos that can be seen immediately on the first page.

As I don’t have unlimited disk capacity, I want to limit the total number of pictures one user can keep. If he exceeds the 50 photos limit, he will first have to remove some of his older photos before he can post any new one.

Depending on the role of a user I could allow the lowest role to be able to post maximum 50 photos and the next role in level could then have for instance a maximum limit of 100 photos.

Kind regards,

Dirk Claesen

to avoid this user fills the entire front page of my website (the most recently posted photos).

That makes sense…

If the users upload in their own album only, you can set the grand total as a limit on the album, and the limit per day on the user role in Table VII-B.
Note that they have to upload at frontend in this case and have no upload rights in Table VII-A.

Hmmm, that might be an option but I’m using public albums (one album per category) into which all users can post their pictures.

The upload is done via the WPPA+ upload widget and in table VII-A I assigned the upload rights.

I’m creating a wildlife photo blog website and my idea was to have one public album per category (mammals, birds, insects, …). All users can post their pictures in any of these albums.
Or is this the wrong approach and should I create one album per user? But can I then force the pictures to belong to one of the categories I defined?

Your approach is good to my opinion, but you must understand that creating a third limit for user upload quantities makes things even more complex than it is already, so i will only do that if there is no other way to approximate your aims.

To be continued…

Thanks for your feedback and your open-mindedness.

It’s true I don’t know what is all happening behind the scenes in order to make this plugin the great plugin that is fun to use. If it is too complex to be implemented, I’ll have to find another way in order to impose the limits.

Instead of having to define x number of rules, would it be a valid option to remove the fixed number of rules that are currently in place and allow any number of rules to be created by the admin. (In database terms this would result in an extra table to be created which would store all defined rules.)
The administrator could then add new rules, modify existing rules or delete existing rules. The columns to be filled in would be the role, the number and the frequency (per day, per week, for ever).
I know this is easily said and that it will require some time to do these changes, but would it be an option?

Kind regards,

Dirk Claesen