Henri Kaukola <[EMAIL PROTECTED]> wrote: > >>Since someone started with the MultiLang I'm > >>going to continue. There has been a thing > >>that has really bothered me in the MultiLang - > >>replication. After the DB conversion it's > >>virtually impossible to upgrade packages. > > > > > > What do You mean with "upgrade packages" ? > > > > > I mean the conversion from nonML to ML.
"Import" option in datagard will do it automagically. It will produce additional *_i18n_po.xml file ready to use with ML databases. > > Nope. But I was wondering about create something to make > > new midgard-data package be usefull for nonML <-> ML. > > Whatever it will look like , it will be looong time running. > > > > Alright, we're going to need one for this case. > Sooo... I think Rambo will be the man to create > somekind of Perl script to sort it out. He's on > vacation until 1. July though... Perl or whatever. The most important thing is to keep things clear. We do not need to keep thousands of different scripts and make tons of documentation for how , when , why. All such scripts should be ready to use with midgard-data. > > Obviously this is a very large site (over 2000 pages) 2000 midgard's pages? > > BTW , I noticed slow performance with midgard 1.6 but compiled > > without Multilang , when one host uses another's one database. > > Both hosts are in the same network and use stunnel to secure > > connections. > > You mean you have DB on separate server? Yeah. MidgardDatabase host:DB user pass. > We've had good results with two server setup. > Although that was mgd-1.5.0 installation... 1.6 doesn't change anything for this case. Piotras --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
