Apparently, this has already been identified as FC-590.

The fix is: Edit your jrun-web.xml (in <CFInstallDirectory>/wwwroot/WEB-INF)
and duplicate the Cold Fusion mapping in the XML file. Restart Cold Fusion
and you're all set.

BTW, this is only a problem for Cold Fusion 6.1 running on Windows.



rkolosky wrote:

As an update to my own post, I got the upgrade to work using the 301 zip
file from farcrycms.org.

It appears the problem with 302 that I had was in types.cfc.

In types.cfc, part of getDisplay() says:

<cfif NOT structIsEmpty(stObj)> <cfif NOT
fileExists("#ExpandPath(displayTemplatePath(typename=stObj.typename,
template=arguments.template))#")>
  <cfthrow type="Application" detail="Error: Template not found
[#ExpandPath(displayTemplatePath(typename=stObj.typename,
template=arguments.template))#]." />
  </cfif>
<cfinclude template="#displayTemplatePath(typename=stObj.typename,
template=arguments.template)#">
</cfif>

And displayTemplatePath() is:

<cffunction name="displayTemplatePath" returntype="string"
access="private" output="no">
  <cfargument name="typename" type="string" required="yes" />
  <cfargument name="template" type="string" required="yes" />
  <cfreturn
"/farcry/#application.applicationname#/#application.path.handler#/#arguments.typename#/#arguments.template#.cfm"
/>
</cffunction>

And in 301, the same part of getDisplay() says:
<cfif NOT structIsEmpty(stObj)> <cftry>
    <cfinclude
template="/farcry/#application.applicationname#/#application.path.handler#/#stObj.typename#/#arguments.template#.cfm">
  <cfcatch>
    <!--- check to see if the displayMethod template exists --->
    <cfif NOT
fileExists("#application.path.webskin#/#stObj.typename#/#arguments.template#.cfm")>
      <cfthrow type="Application" detail="Error: Template not found
[#application.path.webskin#/#stObj.typename#/#arguments.template#.cfm]." >
    <!--- <cfabort showerror="Error: Template not found
[#application.path.webskin#/#stObj.typename#/#arguments.template#.cfm]."> --->
     <cfelse>
<cfrethrow /> <!--- <cfif isdefined("url.debug")><cfset request.cfdumpinited =
false><cfoutput>#cfcatch.message#<br />#cfcatch.detail#</cfoutput><cfdump
var="#cfcatch#"></cfif> --->
     </cfif>
    </cfcatch>
    </cftry>
</cfif>

It should have returned
/farcry/farcry_production/webskin/dmHTML/displayLHSFNAHomepage.cfm but in
302 it was returning
/farcry/farcry_core/admin/farcry_production/webskin/dmHTML/displayLHSFNAHomepage.cfm.

I checked #application.applicationname# (which was farcry_production) and
#application.path.handler# (which was webskin). When I called the
functions from display.cfm, the paths were correct. But, when I called
them from the instantiated object farcry.farcry_core.packages.dmHTML, they
had the extra farcry_core/admin in the path.

Anyway, thanks to Jeff and Jake for helping me out!

rkolosky wrote:

Hi all --

I have an ancient Farcry (Farcry 211) that I wanted to update to 3.0.2.

I downloaded the release candidate, dropped the new core and fourq
folders on the existing one, and went to the updates page. I ran the
updates for b220 through 301, stopped and started Cold Fusion, and went
to go view the front page.

Cold Fusion complained it couldn't find the template.

It was trying to find the template in
/farcry/farcry_core/admin/farcry_production/webskin/dmHTML/displaypageLHSFNAHomepage.cfm

But, the template is in /farcry/farcry_production/...

Obviously I missed a setting somewhere, but I don't know where.

This is running Cold Fusion 6.1 on Win2003 with SQL Server.

Thanks!




--
View this message in context: 
http://www.nabble.com/Upgrade-to-3.0.2-tf2886229s621.html#a8079643
Sent from the FarCry - Dev mailing list archive at Nabble.com.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to