Hey Bob,

I made a change to my own local copy of the Fusebox core so that I could
include my core files from a CF Mapping instead of a relative path from
my index.cfm. It basically looks at the first character of
fusebox_application_path and if it's a "/" it takes the fusebox path
as-is for application.fusebox.webroottocorepath, instead of trying to
calculate it. I'm not sure if this is related to your situation or not,
but making this change to the core allowed me to have my webroot on my
C: drive, with my approot on my F: drive so that I could develop my
application in either Ubuntu or Windows and use the same code base. It's
working a treat for me so far. I haven't submitted it anywhere because I
can't vouch for the quality or the robustness of the code I introduced
into the core, but if you're interested I can send it to you.

Mike
http://www.fusebuilder.net


bobsilverberg wrote:
>
> I found a bug in FuseboxApplication.cfc, in the locateCfc() function.
> Due to my lack of familiarity with the internals of the framework I'm
> not sure how to address it.
>
> The problem is occurring because I have a symbolic link in my server's
> web root which points to my code which is elsewhere. locateCfc() uses
> ExpandPath("/") to get the location of the webroot, which in my case
> is /Library/WebServer/Documents/muraCMSPlain/. The filename being
> passed into locateCfc() is the actual location of the cfc, which is
>
/Users/robertsilverberg/Documents/workspace/muraCMSPlain/plugins/meldforums_16/c\
ontroller/cApp.cfc.
>
>
> The problem is that the logic that checks to see if the application
> resides in the webroot is determining that my app *does not* live in
> the webroot because of the discrepancy in the paths. But the app
> *does* live in the webroot. Because the framework thinks it does not
> live in the webroot, it assumes that I have a mapping to the folder
> that contains the controller, but I do not have such a mapping, so
> when the parsed file is written the CreateObject call points to an
> invalid location for the component.
>
> As I said above, I'm not sure how to best get around this issue. I
> don't know if there's another way to determine the webroot that would
> yield /Users/robertsilverberg/Documents/workspace/muraCMSPlain/ rather
> than /Library/WebServer/Documents/muraCMSPlain/, or whether this means
> that there is a need for a configuration option to tell the framework
> "I don't care what you think - my app is in the webroot".
>
> Does anyone have any ideas on how to resolve this issue?
>
> Thanks,
> Bob
>
>