I've been working on a pretty convoluted project. In a couple instances,
I'm using Spectra via publishing rules to retrieve one or more
objectIDs. An ID are then passed into a Flash movie, and via Flash's
ability to "include" additional Flash movies, the ID is passed through a
couple movies, and then Flash calls back to Spectra.
Somewhere along the way - and I'm 99% certain this is a bug/feature of
Flash - the ID was lower-cased. When Flash passed it back to Spectra, I
was attempting a contentObjectGet, manipulating the object, and then saving
it via contentObjectData. The contentObjectGet worked with my lower-cased
ID, but the contentObjectData did not.
While I realize that this is not really a shortcoming in Spectra, wouldn't
it be nice if Spectra coded defensively against this in *all* tags, not
just some? Or, on the other hand, if I pass in a lower-case, and therefore
invalid ID, should I not expect results?
In an earlier thread I noted a problem with case-sensitivity in the default
"search" publishing rule, and Charles mentioned that for a later release,
either the rule or the contentObjectData tag would be fixed (or both). I
guess I'm putting in my vote here to "fix" the COAPI tags to be coded for
case-insensitivity.
BTW, I've updated my own contentObjectData tag - it's a simple fix. Just
add one statement at line 86:
cfset attributes.objectID = UCase(attributes.objectID)
That's all!
-- David
-------------------------------------------------
David An: [EMAIL PROTECTED]
-- life through a browser --
MINDSEYE Technology, Inc. http://www.mindseye.com/
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
