That link to 3.0.1 is the one available in farcrycms.org's site. I have done that and followed the instructions from the PDF, and also from the video in Jeff Coughlin's site (thanks, Jeff). I've done that three times in different machines. That will work fine with postgres (the whole installation process) until you start running the two updates.
The b300 issues a "datetime" type error. The code in fu.cfm and b300.cfm assumes that when you use an ODBC socket, you are not using postgresql. In my case, the "application.dbtype" variable has a value of ODBC in fu.cfm and postgresql in b300.cfm (oh, this b300.cfm is from bugs.farcry.org, it has better postgresql support). That I cannot figure out how it does that, fu.cfm is an include file, ergo "application.dbtype" should still have the value of 'postgresql' and not 'ODBC'. Regardless, FU.CFM assumes that when you are using ODBC, you are not using Postgresql. A dangerous assumption as PostgreSQL has ODBC support for Windows. For my installation I am using an ODBC socket, and that's where the problem starts. Because the switch-case control detects that I am using an ODBC socket, it executes a create table command with a "datetime" datatype for a certain field, while datetime does not exist in PostgreSQL. Postgres uses timestamp. I managed to fix this by removing the switchcase control and sticking with the timestamp and the update went smoothly. After doing this, Farcry works quite well. By reason that since most CFMX installs in Linux uses JDBC rather than ODBC for PostgreSQL, b300 will work without the tweaking. But still, this needs to be looked at by the bug-fixing team so that it can work well with postgresql-windows-MX6.1-FC301 installs. I've posted this in bugs.farcry.org. Then there's b301 where I am stumped. I encountered a WDDX error. I do not know WDDX, so I can't fix it. The error says that the code found no "root" or something. Beth Bowden said that she has a fix for this for Oracle, though I don't know where to find it and whether it will work for Postgres. Both the updaters worked well in the 3.0.2. install, though, without any tweaking. Maybe that's what I need to do: grab the updaters from 3.0.2 and run them on my 3.0.1. Stephen Moretti wrote: > On 04/09/06, windspinnah <[EMAIL PROTECTED]> wrote: > > > > The 300, yes. The 301, no. My version is 3.0.0, and there is no b301 > > update in the list in version 3.0.0. SO I fixed it manually and now it > > works. > > > Here is the direct download link for 3.0.1 > http://atlas.daemon.com.au/pub/farcry/farcry-milestone_3-0-1.zip > This is the latest stable milestone of farcry. > > Delete everything you've done so far, including the database and start again. > > Thoroughly and carefully read the installation instructions (which you > can download from here : > http://www.farcrycms.org/download.cfm?DownloadFile=C01D17AC-EA69-0EC7-F729E01643D2B36C). > > Once you've done the initial installation make sure you install the > updates by going to http://yoursite/farcry/updates/index.cfm, tick the > boxes for the 3.0.0 and 3.0.1 updates. > > Don't use the 3.0.2 installer. As it says on the download page "If you > are fresh to FarCry you'll definitely want the 3.0.1 release above. " > > Most of all make sure you install the updates and DO NOT mess with the > database tables or entries! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
