CpmFetch Announcements from FistFullOfCode.com [The exact Center of the Internet] ---------------------------------------------------------------- * * * Dev release 1.9.3 is ONLINE now * * * [ Do Not Taunt CPMFetch - you have been warned ] ( get it at http://cpmfetch.fistfullofcode.com ) The only differences between 1.9.2 detailed below and 1.9.3 are: * Fixed cfig_random.php calls to cfimageget.php * Fixed cfrssget.php bugs with new system * Fixed rss_lastadded.php bugs with new system Fixed in 1.9.2 * Fixed cfimageget.php so it would actually work. Needs some touch up. Fixed in 1.9.1 * Fixed bug in thumbnail path generation during install * Changed output test to be 4 images wide instead of 6 ---------------------------- THIS IS A DEVELOPMENT VERSION - THE FIRST OF ITS GENERATION (2.0) so it may be more prone to bugs - yet also has a shorter lifespan. So support for this particular version will be done in one thread on the forum. So it can be deleted after. http://coppermine-gallery.net/forum/index.php?topic=35432.0 IMPORTANT: This is also geared toward CPG 1.4.x and better. Folks running 1.3.x will need to comment out and comment in the indicated lines in cpmfetch_dao.php Open in a text editor and look around line 36 or so. IMPORTANT: This dev version is not good for people who are bridging CPG with a forum and will bring back old errors. This IS one of my major focuses for the 2.0 release so please check the next development release. Installing and running (install.php) ------------------------------------------------------ Installation: Take the entire cpmfetch folder and copy onto your webserver into the Coppermine Photo Gallery directory. So if your gallery is located in /photos, you should now have a directory named /photos/cpmfetch Next, the webserver needs to be able to write to the file named cpmfetch_config.php - so you will need to perform a chmod on this file, either through an ftp program or through the command line. The exact rights needed will vary by webserver, and there may be other ways to do this. The easiest way would be to assign all rights to the file (chmod 777). After that, connect to the install script via a web browser http://www.yourdomainhere.com/cpgdirectoryname/cpmfetch/install.php After that you are done. Installing to a different location ------------------------------------------------------- Well, basically do the same thing as above, but put the cpmfetch folder where you really want it. When you run the install, it will fail to find the CPG config file and will prompt you for a location. The path you enter is relative to your current location. So if CPG was up one folder and called photos you would enter ../photos If it was up two levels and called photos you would enter ../../photos That should do it. Running: -------------------------------------- CpmFetch 2.0 varies from the older version in a few respects: * You no longer need to provide the path to CPG in the new statement [in fact, having a path can screw things up] * Settings are retrieved from CPG itself * Otherwise, all the calls are handled the same, so you should only have to change your include and cpmfetch constructor if you have existing pages. So if you had this before: cpm_viewRandomMedia(3,3); $objCpm->cpm_close(); ?> You would now have something like: cpm_viewRandomMedia(3,3); $objCpm->cpm_close(); ?> Not much of a difference, but the new cpm(param) is now to be used to specify an alternate cpmfetch_config.php file. More on that someday. Stick with the default for now. The config file (cpmfetch_config.php): ---------------------------------- This is where you can change the behavior of your cpmfetch installation. The things you can change and alter are in the top part of the script, the rest should be left alone. Really. What is shown is a default value and a description, all commented out. To enable an override, uncomment and change the value. If you re-run the install, your changes will be wiped out. This is the way it is for now - I plan on saving them in a future version of an install script. What's New? ------------------------------------------------------- * Massive refactoring of all code * Changed: Call to cpm( ) * Removed: cpm_init() Removed: cpm_setDebugMode( ) Replaced with cpm_debugMode($bool = "") Set it with true or false. Not setting returns current setting Removed setPhotoPrefix from cpm_dao continue to use cpm_setMediaPrefixes - although you should not need it now that settings are drawn from the database Removed setDateFormatString continue to use cpm_setDateFormat or set it in the config file Removed setFilter continute to use cpm_setFilter or use the config file entry for it Removed setPrivateLockOn continue to use cpm_unlock_private ($bool="") or use config file entry for it Removed: cpm_OverridePathToCoppermine, cpm_OverrideUrlToCoppermine, cpm_OverridePathToAlbums they should not be needed any more under the new design (I think) Fixed: Outputted HTML is spaced and hard line feeds inserted to make it more readable. Fixed: Always uses full domain name and path for images. Double slashes gone. Added: Config file option for cfUseExistingDBConnection - when set to "true" will use an existing dbconnection if it exists and will not close any connection (even if it created it) when cpmfetch exits. PHP will close any open handles anyway - this will allow for embedded work (inside a forum) to not create new db connections. DOCBOOK DOCUMENTATION CONTINUES See it here... updated daily http://www.fistfullofcode.com/projects/copperminefetch/manual/index.html -------------------------------------------------------------- Sign up for email notifications at http://cpmfetch.fistfullofcode.com This will get you: * Emails for new releases and development releases * Notifications of new tutorials and online help * Security notification (if we ever have one) * Email addresses held closely - no spam, not shared ------------------------------------------------------------- Thanks! Bill@fistfullofcode.com