Matt, both of these issues seem very wrong! The RC1 should definitely
be exactly the same as the current BER, and the two issue you are
seeing would be coming from code that hasn't been in ColdSpring since
the alpha 1 or 2. Can you confirm that you actually deployed the
correct version, cleared your template cache, etc...?
Thanks, Chris
Chris Scott
[EMAIL PROTECTED]
http://cdscott.blogspot.com/
http://www.coldspringframework.org/

On Jun 4, 2006, at 9:57 AM, Matt Williams wrote:
I could have missed a change, or simply had something wrong to
begin with, but I just tried ColdSpring 1.0 RC1 with my Mach-II
app. It wanted to see my MachII_Config_Path variable in the
application scope. I added the following line in my index.cfm and
all worked okay.
<cfset application.MACHII_CONFIG_PATH = MACHII_CONFIG_PATH />
The other addition I had to make was in an AOP Advice cfc. I didn't
have a getXxxAspect function in the Advice cfc, but had never
received an error. Perhaps the Release Candidate requires this
where the older BER I was using did not.
Just my experience: Your Mileage May Vary.
--
Matt Williams
"It's the question that drive us, Neo."