Hi Brett,
Version 6,1,0,83762
umm, odd, that is the latest with updater?
The original problem you quote (below) is simply that the custom tag has registered itself with the double CFX_ at the front, ie CF prepended the tag's name with CFX. This was a known bug with MX before the updater and was fixed with it, I ran into it myself on an un-updated machine only last week. You have to enter the tag's name without the CFX_ prefix according to the writing on the CF Admin page but that did not work properly.
I'd say that CFXImage is probably working fine, you just aren't getting that far :^)
------------------------------------------------------------------------
Error processing CFX custom tag "CFX_CFX_IMG".
The CFX custom tag "CFX_CFX_IMG" was not found in the custom tag database. Please be sure to add custom tags to the database before using them. If you have added your tag to the database then you should check the spelling of the tag within your template to insure that it matches the database entry.
The error occurred in C:\CFusionMX\CustomTags\cfx_img\img.cfm: line 39 ------------------------------------------------------------------------
"CFX_CFX_IMG" seems a bit suspect to me but the img.cfm custom tag is encrypted so I can't do much more than that. Sorry...
What version of CF? That looks like the bug in MX < "6.1 updater" that got fixed in the updater where the name of the CFX went wrong when you registered it.
-- yours,
Kym
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
--- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
