[Encore] Upgrading from 3.3.4 to 5.0

[kevijeps at telusplanet.net]

Hi Joe
Thanks for the info.
The multi language aspect of V5 is one of it's big pluses IMHO.
One thing I would highly recommend is to setup a default V5 MOO AND a default 
V4.01 and test out the user interface and MOO applet functionality.
Depending on your user/builder base they may have some strong opinions about 
some of the "feature" changes between those versions :-)

WRT your old DB, do you know if there were any custom objects with MOO code 
that was not default enCore?

These are the objects most likely to break in doing the conversions.  That goes 
for v3 to v4 as well as v4 to v5. My MOO for example would be a royal pain to 
convert to V5 as I have had to custom code many objects to work in the WEB 
integration part of enCore.

There is a document at the Barn:
http://www.encore-consortium.org/Barn/files/docs/Moo%20Patching.txt 
That talks about the process for doing large version changes with enCore I 
recommend you check it out.

For that matter if you haven't checked out the Barn lately I encourage you to 
do so (A shameless plug, that!).
http://www.encore-consortium.org/Barn/news.html

Ciao
KJ


Quoting Joe Lizzi <jlizzi at rutgers.edu>:

> kevijeps at telusplanet.net wrote:
> > Joe
> > As far as I know I'm afraid you will have to do the full upgrade routine in
> 
> > order to do it safely.
> > The only other way is to rebuild the spaces in a blank V5 Database and then
> 
> > cut 'n paste the details.
> > Hopefully others will have better suggestions.
> >
> >   
> 
> That's what I was afraid of. *sigh* Oh well.
> 
> > Out of curiosity why are you going to use V5?
> > What parts of V5 do you need that V4 doesn't have?
> >
> > Ciao
> > KJ
> >
> >   
> 
> Well, for starters, since this is being used by the language labs, 
> having the "language packs" (and the other language changes) is very 
> useful. It also looks like it handles firewalls and the like better. On 
> top of that, at least from what I can tell, documentation on installing 
> and running v5 is much easier to come by then v4 (I'm probably missing 
> something, though). It also looks like v5, despite being beta, is fairly 
> stable, given that it hasn't been updated since Nov 2006.
> 
> Having said all of that, however, I'm not married to using v5. If that 
> should wait a bit, and I instead use v4 right now, the world isn't going 
> to end. ;)
> 
> -- 
> Joe Lizzi
> System Administrator, Rutgers University
> Office of Instructional Research and Technology
> 732-445-6305
> 
>