I'm experimenting with <cfmimage> for the first time on a photogallery 
site that's nearly finished (thanks for the help in the early stages OBD 
list & Matthew!)


here's the code:
<cfset full_path = "/stetsonimages/"&#img_lg#>
<cfimage action="grayscale" 
destfile="/stetsonimages/images/gallery/work/kitty" 
srcfile="#full_path#" type="jpeg" text="&copy; J.B. Mentzer 2009.">

Here's a dump of the CFIMAGE struct:

Sucess: NO
Error: Error loading image. File could not be found, or is an invalid 
format : /stetsonimages/images/gallery/lg/0612-177/wmsr734_0612-177_01.JPG

If I paste that path into the address bar, the image opens without 
issue. Did I run afoul of a illegal character issue, or is the path too 
long?

And the debug code:
DEBUG:<br />
<cfoutput>
    Sucess: #CFIMAGE.Success#<br />
    Error: #CFIMAGE.Errortext#<br />
    Path: #CFIMAGE.PATH#<br /><!--- --->
    <!--- Name: #CFIMAGE.name#<br /> --->
    Filesize: #CFIMAGE.filesize#<br />
    Dims: #CFIMAGE.Height# x #CFIMAGE.width#<br />
</cfoutput>


Is this page accurate?
http://wiki.openbluedragon.org/wiki/index.php/CFIMAGE

It says 'path' and 'name' are within the CFIMAGE struct, but when I 
tried to print 'em, OB done blowed up ... or displayed a Runtime Error.


Next Q:
The forthcoming photogallery site will require images (jpg's) to be 
FTP'd to the server. I then store the image paths (for sm and lg 
versions) in a table. Will the forthcoming Image functions preclude 
this? How would I use the image/CFIMAGE to read jpgs on a local drive 
and deposit then on the server (my ISP restricts CFFILE for accounts of 
my type).

Also, if the combination of sm and lg images are about 500k, would 
storing them as BLOBs put that 500k in the database (times 500+images?).

Thank you!

* JB *

JB Mentzer


--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
 http://groups.google.com/group/openbd?hl=en
 official site @ http://www.openbluedragon.org/

!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to