Print

[scotch196]

In a previous post, a member asked: "I have a client who wishes to restrict downloads for their web visitors, basically they want to limit downloads to  1 or 2 images per day. Is this possible just using Coppermine?"

GauGau replied: "Not out of the box - you'll have to code this extra feature in."

Following from the above, I'd like to use Coppermine with membership software (probably aMember) as a means of distributing images to members. However, I also want to limit downloads so that members (who will be registered for Coppermine) can only download 100 images per month (or, as an alternative, a total of 2MB per month).

Can anyone give me an indication how difficult it would be to code this extra function into Coppermine? (I'm assuming this question falls under "permissions")

Many thanks,

Scotch

[Joachim Müller]

Telling you how difficult this would be depends entirely on your skill levels. I can't give an estimate here. You'll need good PHP skills and readiness to look into the code in detail. Unless you're an experienced PHP coder I strongly suggest to review the idea. You'd have to come up with code that records what images a user has seen (because this equals "downloading") inside the database. You'd then have to come up with code that keeps him from seing more once he has reached the limit.
I guess a skilled coder could come up with a solution in two or three days.

You might want to search for the various discussions about "amember" as well, since you'd have to code a bridge for this app as well.

[scotch196]

Thank you for your quick and comprehensive reply.

I would definitely not try this myself, but would have to get a programmer to do it. Reason I'm hoping this is possible is to prevent monthly members from simply downloading all or most the images and then cancelling. Commercial stock photo software like Photostore does offer a download limiter, but as far as I know Photostore can't easily be integrated with membership or CMS software.

I like all the features of Coppermine, and aMember Pro does offer bridging with Coppermine, so maybe I'll need to look at alternatives like only offering 6 or 12 month memberships.

Thank you again for your help.

Scotch

[Joachim Müller]

OK, good to hear that you were able to benefit from my reply. I'd like to remind you of something that many tend to forget: applying a hack as the one you're up to will make many core code changes necessary. You have to understand that each time we release a maintenance release you'll have to re-apply all those code changes. That's one of the main drawbacks of heavy customization. Applying the customization and then never ever touching the app even though there are maintenance releases is not an option either: we release new versions to fix bugs and security issues in existing versions. If you don't upgrade on a regular basis, chances are high that you'll be hacked in the future.
I strongly suggest to thoroughly consider this.
To steer clear of the updating dilema, you (or the coder you hire) could try to implement the hack as a pplugin nthat uses coppermine's plugin interface. ZThe main drawback: when upgrading the core application, the plugins don't get touched. Subsequently, you don't have to worry about upgrades ruining your custom hack (making it necesary to re-apply it). I'm not sure though wether the feature you're looking for can be accomplished using the plugin architecture of coppermine, but it's worth considering it for a while.

[scotch196]

Thanks GauGau, particularly for explaining the serious drawbacks of heavy customisation and how this impacts on new releases.

From what you have described, I now don't believe it's worth trying to make such major customisation to Coppermine. I will work instead on using Coppermine as it is, with a membership structure that allows members to download what they want, but will limit access to albums or categories based on the length of membership.

Your assistance on this is much appreciated.

Scotch