I've installed Farcry in my in-house dev environment, and now I'm getting my head around what does what.
If I was to have several different farcry sites, operating independently, I assume I don't need to have multiple farcry installations, only multiple installations of the parts that relate to the specific sites. Is this correct? I can share some parts of the code? If so, which parts can be shared, and which parts would need to be created for each site? For the record, I installed Farcryv2 straight off. I followed the instructions laid out by Neil Robertson-Ravo on this list on 1 October, and as discussed earlier today with Gary Menzel. The project's got its own SQL Database, as you'd expect, but the files for the site are not going into c:\inetpub\wwwroot\oursite_farcry\... as I'd expect, but instead they're going into C:\Inetpub\wwwroot\applications\farcry_oursite\ I guess I didn't pay enough attention to the instructions because in my shared environment that would not work. The control panel on the hosting server creates the client's site under wwwroot but never mind, I'm most impressed that in 10 minutes I had Farcry installed, and in a couple of hours, I had the basis of a completed site - structure, bare-bones of each section of the site, and a start on customising the look and feel of the site. This was a lot slower than it could have been, because I was stopping to look at the Bathurst race all the time, and also I was looking in to the nuts and bolts, trying to find out what did what. I hope eventually to locate what actually changes the look and feel of the site, so I can make a site that looks a little different to all the other FarCry sites. Has anyone written a simple user manual for non-technical people? I'm using a CMS because I'll have a lot of non-technical people working on this site, and to tell the truth, I can't give them stuff like this: [quote] Nav Aliases - is a simple name that creates a variable in the application (application.navid.navalias) that can be referenced programmatically. These aliases can be used with 'Included' pages. You can set up Navigation nodes with aliases and then refer to that alias in the included page instead of the complete path and objectID. [/quote] Cheers, Michael Kear Windsor, NSW, Australia AFP Webworks. --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
