On Oct 7, 10:50 am, Kay Smoljak <[EMAIL PROTECTED]> wrote: > > upgrade to 4.0.11 it should be fixed. I noticed that issue > > previously, and I haven't seen it in a while so it was fixed in 10 or > > 11. > > Thanks Sean - I'll have to see if my host will upgrade.
Just a quick note on upgrades. If its a point release like 4.0.10 to 4.0.11 all you should have to do is deploy the code over the top of the existing farcry library and possibly restart the applications. For hosts, this might easily done by upgrading and restarting CF -- ie. forcing all applications on the server to restart. If its a 5.0.0 to 5.1.0 style release, this is typically associated with some sort of schema change and may require slightly more effort. For example, you may need to run an updater to upgrade an existing project. Again we try and make this very straightforward, but for hosts running lots of sites it may be a bit more difficult. Essentially people should be updating the minor point releases as soon as they are available. -- geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
