Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: making an add-on that only uses info stored in the cpg database  (Read 1234 times)

0 Members and 1 Guest are viewing this topic.

jhfotoman

  • Coppermine newbie
  • Offline Offline
  • Posts: 9
making an add-on that only uses info stored in the cpg database
« on: November 20, 2008, 01:21:29 am »

I hope this is the correct location for this; it seems the only logical place that is not locked down.

I am considering bypassing the Coppermine "theme" approach altogether and writing my own front-end code to access the data stored in the cpg database. This will allow considerable freedom from the somewhat restrictive and clumsy theme framework.

I'm not asking for support; just curious what people think...I can't see that it violates any license or even ethic...though I can easily imagine certain Devs being upset by this idea.

Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47844
  • aka "GauGau"
    • gaugau.de
Re: making an add-on that only uses info stored in the cpg database
« Reply #1 on: November 20, 2008, 08:38:27 am »

Coppermine is licensed under GNU GPL, so you're free to come up with modifications. Why should we be upset? The theme engine's core in use is 5 years old, so yes: there might be better alternatives. Branding it as being "clumsy" is a matter of taste though.
Back to your initial suggestion: only using the data stored in coppermine's database and not using the "wrapping" code is not a new idea in itself: that's what cpmFetch and a load of other mods is doing. Please go ahead. We'd love to see what you can come up with.
Logged
Pages: [1]   Go Up
 

Page created in 0.013 seconds with 19 queries.