(2.0.0 is identical I think to 1.9.12 so if you are running 1.9.12, no need to upgrade at this time - but use - the online doc's they are newer.)
Here are the release notes:
CpmFetch Announcements from FistFullOfCode.com
[The exact Center of the Internet]
----------------------------------------------------------------
* * * Stable release 2.0.0 is ONLINE now * * *
[ We're off to the witch. We may never never never come home ]
( get it at
http://cpmfetch.fistfullofcode.com )
There is a whole new web site now. And the doc's have been completely redone (and may almost even be up to date). They are at least, if not better than the old ones.
The doc's also contain a nice walkthough and an UPGRADE GUIDE (Important read).
As of now, if you have problems with the older versions (anything before 2.0.0) my first response will be to upgrade. You are welcome to post for help with older versions, but that support will have to come from the community at large - I will remain focused on the latest versions and fixing problems that occur in there.
------------------------------------------
Enhancements since the last stable release
------------------------------------------
* Bug fixes - many. Since these are of little interest to people I am not going to list them here. Suffice to say there has been several fixes to bugs, fixes to the fixes of bugs, performance enhancements, etc. We had a very large gallery database donated to us (20,000 entries) which really did a lot to show where CpmFetch was lacking in a large environment.
* Installer - CpmFetch now has an installer program that helps you get started. See the documenation for how to install and use it.
* New parameters to the $source parameter - lets you specify by keyword what to select.
keyword=a,b,c,d
text=a,b,c,d
* Many functions were modified at the SQL level to provide more information, and to work faster.
getMediaCount converted to left join, sql call altered a bit
getMediaCountFrom converted to left join
getMediaCountForAlbum converted to left join
getMediaCountAddedSince converted to left join
getViewcount converted to left join
getMediaByPid converted to left join
* Added $objCpm->sqlPostSelect to support inserting a no-cache SQL directive. Should only be used for benchmarking.
* cfrssget should not autoset your cpg's char set
* Made website URL a variable in install script for future change
* Added BMP to list of types that may have a thumbnail to display (list is now: jpg, jpeg, gif, png, bmp)
* Fixed a nasty SQL inefficency in default bridged code (thx Jerx)
* cpm_getConfigEntry($_keyName) added - allows for checking CPG and CpmFetch config info
* Added in cpm_getAlbumListFrom ($source, $rows, $columns, $options="")
* DAO Added in getAlbumListFrom ($source)
* Added in cpm_getCategoryList ($options="")
* DAO Added in getCategoryListFrom($source="")
* Mmmm... cpm_viewLastUpdatedAlbumsFrom($source, $rows, $columns, $options="")
which may or may not work, depending... test before use.
* Changed a number of calls so $source is the first parameter so it linguistically flows. For any, insert "" instead of a source.
- cpm_viewRandomMediaFrom($source,$rows, $columns, $options="")
- cpm_viewLastAddedMediaFrom($source, $rows, $columns, $options="")
- cpm_getAlbumListFrom ($source, $rows, $columns, $options="")
* CFRSSGET
- Recoded to use cpmfetch.php instead of cpmfetch_dao.php
* Fixed error generated when no results were found
* Remapped parameters for H,I,L,O from CPG 1.3 database fields to the userProfile1,2,3,4
* cpm_listMediaAddedOverLastDays : Changed linking to use cpg url from config file
* cpm_showCategoriesUpdatedOverLastDays : Changed linking to use cpg url from config file
* cpm_showAlbumsUpdatedOverLastDays : Changed linking to use cpg url from config file
* Reduced functionality for bridged versions (replacement SQL code)
* Added in %1, %2, %3, %4 to represent the photos custom fields in each photo (last additions to depreciated % option array method)
* Added a.visibility as aVisibility, a.pos as aPos, a.category as aCategory, a.thumb as aThumb, a.keyword as aKeyword to be returned with picture data. (CPG 1.4.x +)
* Added c.name as cName, c.description as cDescription, c.pos as cPos, c.parent as cParent, c.thumb as cThumb to data returning pictures in the data rows (CPG 1.4.x +)
* When returning data, three new fields are added to the rows (This is to save people the trouble of calling getImageToUse...):
fullPathToThumb
fullPathToNormal
fullPathToFull
* The subtitle and alttag will also be passed back as part of the dataset as:
cpmSubtitle
cpmAlttag
* Due to the lack of one character abbreviations for subtitles, anything that generates based on a template is now moving to a format involving {{tag}} and fully descriptive tags. The older % based tags are depreciated and will go away in the future. This is a sample list for what is returned with pictures:
pFilepath
pFilename
pAid
pFilesize
pTitle
pCaption
pOwner_name
pOwnerId
pCtime
pHits
pPid
pPic_Rating
pVotes
pWidth
pHeight
pUser1
pUser2
pUser3
pUser4
cName
cDescription
cPos
cParent
cThumb
uUser_lastvisit
uUser_regdate
uUser_email
uUser_profile1
uUser_profile2
uUser_profile3
uUser_profile4
uUser_profile5
uUser_profile6
aAid
aTitle
aDescription
aVisibility
aPos
aCategory
aThumb
aKeyword
fullPathToThumb
fullPathToNormal
fullPathToFull
cpmSubtitle
D,S,V,w from the old format can still be called in the new method as:
D : {{pCtimeAgo}} : Formatted Picture time - as in how old
S : {{pFilesizeKB}} : Filesize in Kilobytes
V : {{pPic_RatingStars}} : Number of stars given to picture
w : {{pCtimeFormatted}} : Formatted picture creation date
* "linktemplate" added to the options array. This allows you to set up exactly what the link will be formatted like. This allows for you to link to other than the CPG gallery. This is new, and allows you to screw the links up all on your own.
"linktemplate" => "t_blackbearcar.php?carid={{pAid}}"
or using the old way (bad):
"linktemplate" => "t_blackbearcar.php?carid=%a"
* Moved templated SQL code into the config file (preparing to support bridge)
* Changed output test to be 4 images wide instead of 6
* cpm_debugMode($bool = "") Set it with true or false. No 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)
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.
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, now it is a
path to the cpmfetch_config.php file.
* 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:
<?php
include "./cpmfetch/cpmfetch.php";
$objCpm = new cpm("/gallery");
$objCpm->cpm_viewRandomMedia(3,3);
$objCpm->cpm_close();
?>
You would now have something like:
<?php
include "./gallery/cpmfetch/cpmfetch.php";
$objCpm = new cpm("./gallery/cpmfetch/cpmfetch_config.php");
$objCpm->cpm_viewRandomMedia(3,3);
$objCpm->cpm_close();
?>
Note that the new cpm parameter is the relative, or full path to the config file.
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.
--------------------------------------------------------------
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
Author
Topic: CpmFetch 2.0.0 is the new STABLE release (Read 5088 times)