This is a bit odd, but this was running just fine and then I copied the
entire application directory and renamed it (as I was switching over from
subversion to git). Now I’m getting
“No matching function [CF_LOGIN_PAGE] found”
So the original application works, the cloned application does not (under
both Railo and Lucee).
login_page.cfm is a customtag and is located in the customtag directory
that is defined in application.cfc
I’m referring to the customtag in cfscript like so:
This is a bit odd, but this was running just fine and then I copied the entire application directory and renamed it (as I was switching over from subversion to git). Now I’m getting
“No matching function [CF_LOGIN_PAGE] found”
So the original application works, the cloned application does not (under both Railo and Lucee).
login_page.cfm is a customtag and is located in the customtag directory that is defined in application.cfc
I’m referring to the customtag in cfscript like so:
It really did work, lol (and still is actually on one app).
I don’t know how I came to use that syntax, nor can I find any
documentation on it. Anyway, your suggestion worked great, so thank you!On Thursday, February 5, 2015 at 10:47:04 AM UTC-5, Gert Franz wrote:
Alex,
This really worked before? I really can’t imagine it did. What will work
instead is using the script version of cfmodule like this:
This is a bit odd, but this was running just fine and then I copied the
entire application directory and renamed it (as I was switching over from
subversion to git). Now I’m getting
“No matching function [CF_LOGIN_PAGE] found”
So the original application works, the cloned application does not (under
both Railo and Lucee).
login_page.cfm is a customtag and is located in the customtag directory
that is defined in application.cfc
I’m referring to the customtag in cfscript like so:
I apologize beforehand if this is ‘duh, I tried that’ or ‘duh, I wrote the
tag myself, so I would know’ territory, but in the interest of
troubleshooing:
You might try checking Railo admin on the site where the tag is still
working via script and see if there’s a different resource mapping defined
in one of the sections of Archives & Resources…also, I’d check the
[contextroot]/WEB-INF/railo/library/{fld,function} dirs (or within where
ever the web context files are located…even moreso if they’re not in
[contextroot]/WEB-INF). Could be something in there. Maybe someone added
a component or cfm with a custom ‘built-in’ function with a name that
mimics the cf_ naming prefix so it would work like that.
Hope this helps!
-SeanOn Thursday, February 5, 2015 at 10:35:03 AM UTC-5, Alex Kaminsky wrote:
This is a bit odd, but this was running just fine and then I copied the
entire application directory and renamed it (as I was switching over from
subversion to git). Now I’m getting
“No matching function [CF_LOGIN_PAGE] found”
So the original application works, the cloned application does not (under
both Railo and Lucee).
login_page.cfm is a customtag and is located in the customtag directory
that is defined in application.cfc
I’m referring to the customtag in cfscript like so:
