|
Friday 04 April 2008 8:02:12 am
The empty SiteAccess limitations are the result of a fix in the 3.6 series. The siteaccess names are actually stored as checksums and there was an issue with checksum calculation on 64-bit systems. The side-effect of the fix is that checksums are recalculated so your siteaccesses end up being different than those you picked. There is a related ini setting in site.ini. I believe it's 64bitCompatibilityMode under [SiteSettings]. Setting it to disabled might help as long as you don't migrate to a 64-bit system, but it may already be too late. We did an upgrade from 3.6.12 to 4.0 on Monday without any problems. But that upgrade path does require careful planning, testing and enough time and documentation. I tested the complete upgrade path 3 times before doing it on the live site and it really paid off. Brian, It's far from impossible to go from 3.9.2 to 4.0, it's pretty easy in fact. I've done it this morning :-) I skipped 3.10 and moved to 4.0 right away. The nice URL update script in 4.0 is better anyway and the only script I needed from 3.10 was an update for the ISBN datatype (which runs flawlessly on 4.0). The other scripts did not apply to that particular site, but I'm quite sure they run on 4.0 too. You do need the 3.9.0-to-3.10.0 database update before doing the 3.10.0-4.0.0 update.
Hans
http://blog.hansmelis.be
|
