From: Jason B. <jas...@mi...> - 2006-09-29 12:47:35
|
> you probably missed to make a new [dump4setup] on the old install. Yes, that did it. I'm sure you aren't surprised, but thank you! > When > you copied the sources to the new box, the etemplate.inc.php was touch > and reloaded to the database, overwriting your current, not yet dumped > changes. I'd like to understand this better. I figured I'd get all important information by grabbing my entire MySQL directory as well as the entire eGroupWare directory. And yet, this was somehow not the case with regards to eTemplate. Where on Earth was that information being stored, if not in either the eGroupWare folders or in the database? I mean, I get that you're saying the etemplate file was reloaded from the database, but again, where were the not-yet-dumped changes being stored?? Pardon me if I sound confused, but I'm worried that my nightly backups won't be getting things like eTemplate changes! (I rarely make changes, but still) P.S. I'm still on 1.0.0.009, as I got a few weird error messages from my eTemplate module, when I tried to move to the 1.2 series of eGroupWare. I'll try to follow up with questions about that later today, as I'd still like to complete that migration. Thanks again! --Jason Byrns |