Fusebox?

That was on the default site so it’s ok. All good on the install of CF but
I would like to get this site onto Lucee. For some reason it adds a “:” to
the URL. Other fusebox sites run fine on Lucee except this one.On Thu, Apr 16, 2015 at 9:43 AM, Sean Coyne <@Sean_Coyne> wrote:

The CF or Lucee installers are not going to modify YOUR code. Clearly
your code has a reference to server.lucee.version somewhere, which will not
exist if you’re running on ACF.

On Wednesday, April 15, 2015 at 1:05:18 PM UTC-4, Bill Foresman wrote:

uninstalled and thought I had removed all dir’s. Where would that be and
why wouldn’t CF overwrite it?

On Wed, Apr 15, 2015 at 1:00 PM, Sean Corfield se...@corfield.org wrote:

Looks like you left the Lucee index.cfm page in place?

Sean

On Apr 15, 2015, at 9:49 AM, Bill Foresman bi...@foresman.com wrote:

I had already move back to CF and now I have Lucee interfering in it.
I’ve uninstalled Lucee and get this after installing CF:

Welcome to your Lucee Installation!

You are now successfully running Lucee

The web site you are accessing has experienced an unexpected error.
Please contact the website administrator.

The following information is meant for the website developer for
debugging purposes.Error Occurred While Processing RequestElement
LUCEE.VERSION is undefined in SERVER. Resources:

  • Enable Robust Exception Information to provide greater detail
    about the source of errors. In the Administrator, click Debugging & Logging

Debug Output Settings, and select the Robust Exception Information option.

Browser Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/41.0.2272.118 Safari/537.36Remote Address
73.28.53.29Referrer Date/Time 15-Apr-15 12:44 PM

On Wed, Apr 15, 2015 at 12:46 PM, Sean Corfield se...@corfield.org wrote:

On Apr 15, 2015, at 9:43 AM, Bill Foresman bi...@foresman.com wrote:

How do I update to 5.5 and what is ACF?

Google turned up this article (I’ve no idea how accurate it is);

http://fuseboxipedia.com/index.cfm/do/cWiki.
viewWikiPage&webpath=upgrade-fusebox-4-to-5

There may also be useful information on the Fusebox web site itself.

ACF = Adobe ColdFusion.


You received this message because you are subscribed to a topic in the
Google Groups “Lucee” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/lucee/4_LL03OC5T0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/lucee/BEC0F5E3-79F7-42E5-AFC6-5788BB7B1F7C%40corfield.org
https://groups.google.com/d/msgid/lucee/BEC0F5E3-79F7-42E5-AFC6-5788BB7B1F7C%40corfield.org?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


Bill Foresman
(239) 404-2814


You received this message because you are subscribed to a topic in the
Google Groups “Lucee” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/lucee/4_LL03OC5T0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/85d1f8c1-2834-45ab-adec-24339f8d6a39%40googlegroups.com
https://groups.google.com/d/msgid/lucee/85d1f8c1-2834-45ab-adec-24339f8d6a39%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


Bill Foresman
(239) 404-2814

The CF or Lucee installers are not going to modify YOUR code. Clearly your
code has a reference to server.lucee.version somewhere, which will not
exist if you’re running on ACF.On Wednesday, April 15, 2015 at 1:05:18 PM UTC-4, Bill Foresman wrote:

uninstalled and thought I had removed all dir’s. Where would that be and
why wouldn’t CF overwrite it?

On Wed, Apr 15, 2015 at 1:00 PM, Sean Corfield <se...@corfield.org <javascript:>> wrote:

Looks like you left the Lucee index.cfm page in place?

Sean

On Apr 15, 2015, at 9:49 AM, Bill Foresman <bi...@foresman.com <javascript:>> wrote:

I had already move back to CF and now I have Lucee interfering in it.
I’ve uninstalled Lucee and get this after installing CF:

Welcome to your Lucee Installation!

You are now successfully running Lucee

The web site you are accessing has experienced an unexpected error.
Please contact the website administrator.

The following information is meant for the website developer for
debugging purposes.Error Occurred While Processing RequestElement
LUCEE.VERSION is undefined in SERVER. Resources:

  • Enable Robust Exception Information to provide greater detail about
    the source of errors. In the Administrator, click Debugging & Logging >
    Debug Output Settings, and select the Robust Exception Information option.
  • Check the ColdFusion documentation
    http://www.adobe.com/go/prod_doc to verify that you are using the
    correct syntax.
  • Search the Knowledge Base http://www.adobe.com/go/prod_support/ to
    find a solution to your problem.

Browser Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/41.0.2272.118 Safari/537.36Remote Address 73.28.53.29
Referrer Date/Time 15-Apr-15 12:44 PM

On Wed, Apr 15, 2015 at 12:46 PM, Sean Corfield <se...@corfield.org <javascript:>> wrote:

On Apr 15, 2015, at 9:43 AM, Bill Foresman <bi...@foresman.com <javascript:>> wrote:

How do I update to 5.5 and what is ACF?

Google turned up this article (I’ve no idea how accurate it is);

http://fuseboxipedia.com/index.cfm/do/cWiki.viewWikiPage&webpath=upgrade-fusebox-4-to-5

There may also be useful information on the Fusebox web site itself.

ACF = Adobe ColdFusion.


You received this message because you are subscribed to a topic in the
Google Groups “Lucee” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/lucee/4_LL03OC5T0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
lucee+un...@googlegroups.com <javascript:>.
To post to this group, send email to lu...@googlegroups.com <javascript:>
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/BEC0F5E3-79F7-42E5-AFC6-5788BB7B1F7C%40corfield.org
https://groups.google.com/d/msgid/lucee/BEC0F5E3-79F7-42E5-AFC6-5788BB7B1F7C%40corfield.org?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


Bill Foresman
(239) 404-2814

That was on the default site so it’s ok. All good on the install of CF but
I would like to get this site onto Lucee. For some reason it adds a “:” to
the URL. Other fusebox sites run fine on Lucee except this one.

You need to do some troubleshooting of your own, Bill. It’s not “for some
reason”, it’ll be doing it for a very precise reason. Fortunately you have
all the logic as to how this is coming to pass sitting in front of you! You
need to look @ the code and how it’s building that path and then identify
where it’s going wrong. Then when you’ve isolated the preicse bit of code
which behaves differently on CF than it is on Railo/Lucee, come back and
ask about that.

This isn’t the right forum to be asking for help with a Fusebox install.
However it is the forum to ask for help in difference between
ColdFusion’s and Lucee’s CFML implementations.

You really also ought to read these:

And these (which are also discussed in the articles above):
http://www.catb.org/esr/faqs/smart-questions.html
http://sscce.org/On 16 April 2015 at 14:45, Bill Foresman <@Bill_Foresman> wrote:


Adam

I mentioned this in a blog post yesterday:

http://cfsimplicity.com/90/the-simplicity-of-lucee

and have raised a ticket:

Julian.On 17 April 2015 at 13:59, Chris Schmitz <@Chris_Schmitz> wrote:

Railo/Lucee on the other hand do have a built in function getCanonicalPath()
which does NOT replace the back slashes.

Hi Bill,

That was on the default site so it’s ok. All good on the install of CF
but I would like to get this site onto Lucee. For some reason it adds a “:”
to the URL. Other fusebox sites run fine on Lucee except this one.

first of all, you are already running Fusebox 5. The file that throws the
error (fuseboxApplication.cfc) didn’t exist in FB4.

That being said, I did a quick test and ported a legacy FB app to Lucee and
ran into the same error. Some quick debugging showed that the approotpath
was using \ instead of the / as a delimiter.

Iin FB5 the approotpath is calculated using the function
getCanonicalPath(). ACF does not know this function, but FB5 does have a
UDF for this which replaces all occurrences of \ with / (which works on all
OSs).

Railo/Lucee on the other hand do have a built in function
getCanonicalPath() which does NOT replace the back slashes.

As a quick fix, do a search and replace on the complete fusebox5 directory.
Replace all occurrences of “getCanonicalPath” with “getCanonicalPath_UDF”
(or whatever name you would like, just make sure you are not using a built
in function name). That makes sure that the UDF is called no matter what
app server.

This raises another issue though. ACF does not allow the declaration of
UDFs with the name of a built in function. Lucee on the other hand does.
Shouldn’t Lucee throw an error here? Or is there a setting that I missed
which allows for this?

Cheers

Chris

I have the same problem with no resolution eitherOn Tue, Jun 9, 2015, 12:18 PM Phillip Vector <@Phillip_Vector1> wrote:

I’ve been looking hard at this issue and it still doesn’t run even though
I ran the path through a variety of filters like these.

<cfset relative = replace(relative,"//","/","all") />
<cfset relative = replace(relative,"\/","/","all") />
<cfset relative = replace(relative,"\","/","all") />

I’m still getting…

…/…/…/…/:/Lucee/tomcat/webapps/ROOT/Ubersite/

It seems to me that the /:confused: is messing things up, but all my efforts to
find out where the path is first being set up are coming up fruitless. Any
ideas?

On Friday, April 17, 2015 at 5:59:47 AM UTC-7, Chris Schmitz wrote:

Hi Bill,

That was on the default site so it’s ok. All good on the install of CF
but I would like to get this site onto Lucee. For some reason it adds a “:”
to the URL. Other fusebox sites run fine on Lucee except this one.

first of all, you are already running Fusebox 5. The file that throws the
error (fuseboxApplication.cfc) didn’t exist in FB4.

That being said, I did a quick test and ported a legacy FB app to Lucee
and ran into the same error. Some quick debugging showed that the
approotpath was using \ instead of the / as a delimiter.

Iin FB5 the approotpath is calculated using the function
getCanonicalPath(). ACF does not know this function, but FB5 does have a
UDF for this which replaces all occurrences of \ with / (which works on all
OSs).

Railo/Lucee on the other hand do have a built in function
getCanonicalPath() which does NOT replace the back slashes.

As a quick fix, do a search and replace on the complete fusebox5
directory. Replace all occurrences of “getCanonicalPath” with
“getCanonicalPath_UDF” (or whatever name you would like, just make sure you
are not using a built in function name). That makes sure that the UDF is
called no matter what app server.

This raises another issue though. ACF does not allow the declaration of
UDFs with the name of a built in function. Lucee on the other hand does.
Shouldn’t Lucee throw an error here? Or is there a setting that I missed
which allows for this?

Cheers

Chris


You received this message because you are subscribed to a topic in the
Google Groups “Lucee” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/lucee/4_LL03OC5T0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/23528d2c-f47f-4ba4-883c-54e15b4f94c5%40googlegroups.com
https://groups.google.com/d/msgid/lucee/23528d2c-f47f-4ba4-883c-54e15b4f94c5%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

I’ve been looking hard at this issue and it still doesn’t run even though I
ran the path through a variety of filters like these.

<cfset relative = replace(relative,"//","/","all") />
<cfset relative = replace(relative,"\/","/","all") />
<cfset relative = replace(relative,"\","/","all") />

I’m still getting…

…/…/…/…/:/Lucee/tomcat/webapps/ROOT/Ubersite/

It seems to me that the /:confused: is messing things up, but all my efforts to
find out where the path is first being set up are coming up fruitless. Any
ideas?On Friday, April 17, 2015 at 5:59:47 AM UTC-7, Chris Schmitz wrote:

Hi Bill,

That was on the default site so it’s ok. All good on the install of CF
but I would like to get this site onto Lucee. For some reason it adds a “:”
to the URL. Other fusebox sites run fine on Lucee except this one.

first of all, you are already running Fusebox 5. The file that throws the
error (fuseboxApplication.cfc) didn’t exist in FB4.

That being said, I did a quick test and ported a legacy FB app to Lucee
and ran into the same error. Some quick debugging showed that the
approotpath was using \ instead of the / as a delimiter.

Iin FB5 the approotpath is calculated using the function
getCanonicalPath(). ACF does not know this function, but FB5 does have a
UDF for this which replaces all occurrences of \ with / (which works on all
OSs).

Railo/Lucee on the other hand do have a built in function
getCanonicalPath() which does NOT replace the back slashes.

As a quick fix, do a search and replace on the complete fusebox5
directory. Replace all occurrences of “getCanonicalPath” with
“getCanonicalPath_UDF” (or whatever name you would like, just make sure you
are not using a built in function name). That makes sure that the UDF is
called no matter what app server.

This raises another issue though. ACF does not allow the declaration of
UDFs with the name of a built in function. Lucee on the other hand does.
Shouldn’t Lucee throw an error here? Or is there a setting that I missed
which allows for this?

Cheers

Chris

I have several fb4 and fb5 sites running fine on both Railo and Lucee.

Here’s something to note though: Railo/Lucee and Fusebox each have their
own getCanonicalPath() function, but they each return very different
results. So to get FB sites to run on Railo/Lucee, you need to rename FB’s
getCanonicalPath() function to soemthing esle - I used getFbCanonicalPath()

  • and then search and update all references to that function.

Then, stop Railo/Lucee, delete your parsed and web-inf directories, restart
Railo/Lucee and start your sites.

Hope that helps.

-RROn Friday, April 10, 2015 at 9:16:28 AM UTC-4, Bill Foresman wrote:

With railo there was an app that we needed to install so is there one for
Lucee?

I know this was from months ago, but I wanted say thanks for this find. I
just migrated our server to Lucee and we have one rogue app still on
fusebox5. I am currently rewriting it, but I still needed to run for
another month or two while I complete the project. My fix for this was just
to find the non-qualified calls to getCanonicalPath (the calls on the same
components as the UDF definition), and replace them with
“this.getCanonicalPath”. Anyway, thanks this was a huge time saver for me!On Friday, April 17, 2015 at 7:59:47 AM UTC-5, Chris Schmitz wrote:

Hi Bill,

That was on the default site so it’s ok. All good on the install of CF
but I would like to get this site onto Lucee. For some reason it adds a “:”
to the URL. Other fusebox sites run fine on Lucee except this one.

first of all, you are already running Fusebox 5. The file that throws the
error (fuseboxApplication.cfc) didn’t exist in FB4.

That being said, I did a quick test and ported a legacy FB app to Lucee
and ran into the same error. Some quick debugging showed that the
approotpath was using \ instead of the / as a delimiter.

Iin FB5 the approotpath is calculated using the function
getCanonicalPath(). ACF does not know this function, but FB5 does have a
UDF for this which replaces all occurrences of \ with / (which works on all
OSs).

Railo/Lucee on the other hand do have a built in function
getCanonicalPath() which does NOT replace the back slashes.

As a quick fix, do a search and replace on the complete fusebox5
directory. Replace all occurrences of “getCanonicalPath” with
“getCanonicalPath_UDF” (or whatever name you would like, just make sure you
are not using a built in function name). That makes sure that the UDF is
called no matter what app server.

This raises another issue though. ACF does not allow the declaration of
UDFs with the name of a built in function. Lucee on the other hand does.
Shouldn’t Lucee throw an error here? Or is there a setting that I missed
which allows for this?

Cheers

Chris