Where I'm having a problem, and I guess I shouldn't be... is how to set up the variables for the plug-ins, similar to the "globals".
For instance, rather than abstracts, in the picture-post-gallery mod, the script needs to have a whole bunch of variables available to it, including the $CFG variables, $USER variables, and then it's own $UPLOAD_CFG set of variables (which include paths, options, etc).
Within my script, what should those configuration options be called? Is there a passed object that holds all that?
Right now, I'd have a my_plugin.pm which would be equivalent to the Links.pm in version 1.1x. That would be loaded on script start up, to hold the variables. But, I want that to be administered via the Admin/plugin options, so I don't have to re-invent the wheel and come up with an admin screen.
I'm getting too close to this, and probably need to take a break, since I've gotten further in the past 2 days than I ever thought possible. Right now, I have to integrate the filescan/process with the image upload, and the actual program will be working. The other features -- such as adding in existing collections, and re-creating databases or indexes, etc will follow, but I'm very close to a working picture-post-gallery-postcards program all in one.
What I've found is that the thumbnailer I'm using is using backtic function to run parts of the netpbm package to do the image conversions.
That should still function in CGI calls by the server, right? I'd just have to give full paths to the netpbm utilities, since the server user has no defaults set. This is something that is new to me, and I need to figure out how to prevent people from uploading files that would be security holes or problems. Maybe there are none, but when something is dropped to the system like that, the potential exists.
PUGDOGŪ PUGDOGŪ Enterprises, Inc.
FAQ: http://pugdog.com/FAQ