Ticket #90 (closed defect: wontfix)

Opened 20 years ago

Last modified 16 years ago

bug slips by CF, breaks on BD

Reported by: charlie@… Owned by: somebody
Priority: low Milestone: 2.0.x-next-patch
Version: 2.0.304 Severity: minor
Keywords: bluedragon Cc:

Description

Folks, line 16 of the modelglue.cfm file has this:

<cfparam name="ModelGlue?_LOCAL_COLDSPRING_PATH" type="string" default="#expandPath(".") & "/config/ColdSpring.xml"#" />

which works fine on CFMX but breaks on BD. Notice the separation of the # from the end of the expandpath function. It would seem it should be there, rather than the end of the line.

And indeed, this works on BD:

<cfparam name="ModelGlue?_LOCAL_COLDSPRING_PATH" type="string" default="#expandPath(".")# & "/config/ColdSpring.xml"" />

but it fails on CFMX. The solution that works on both is this:

<cfparam name="ModelGlue?_LOCAL_COLDSPRING_PATH" type="string" default='#expandPath(".")# & "/config/ColdSpring.xml"' />

I've assigned this as lower priority and minor severity only because, after fixing that, it breaks on another line. I won't for now be able to go through figuring it all out.

Change History

Changed 20 years ago by anonymous

  • milestone set to Release Public Beta 1

Changed 20 years ago by charlie@…

Just noticed on searching the issue tracker for Bluedragon that Sean had found the same error (with a slightly different explanation). His and mine are the only BD comments so far, it seems.

Changed 20 years ago by anonymous

is there a reason why you couldn't just use:

<cfparam name="ModelGlue?_LOCAL_COLDSPRING_PATH" type="string" default="#expandPath(".")#/config/ColdSpring?.xml" />

Why do you need to try to do some fancy concatenation of the strings.

Changed 20 years ago by joe.rinehart

  • milestone changed from Release Public Beta 1 to Feature Requests

I'm shifting to Feature Requests, which is what BlueDragon? and Railo support is sort of becoming. Not saying it won't make it in, but it's not on the front burner.

Changed 16 years ago by cfgrok

  • milestone changed from Feature Requests to 2.0.x-next-patch

Changed 16 years ago by DanWilson

  • status changed from new to closed
  • resolution set to wontfix

I'm not sure this is still valid, since it is 4 years old. I'm not likely to have a test environment for BD.

If there is still an issue, someone will re-raise this, but I suspect this bug was fixed in a more recent version of BD.

Note: See TracTickets for help on using tickets.