Manila config.root trashed

[Lawrence Lee]

1. config.root is a local file used to save configuration settings so it
never gets updated in the root updates process.

2. If you enable the option to backup all databases nightly (this is
separate from the Manila Backups setting then it will save all the important
root files to the /Guest Databases/ops/backups folder each night (the folder
will be named using the date of the backup).

3. The error in the Admin site means that your manila.root is not updated.
Can you try updating it and then retest.

Lawrence 

-----Original Message-----
From: manila-users-bounces at userland.com
[mailto:manila-users-bounces at userland.com] On Behalf Of Jason Everett
Sent: March 20, 2008 11:13 PM
To: Manila-Users at userland.com
Subject: FW:Manila config.root trashed

Any ideas?

Thanks in advance,

Jason Everett
Educational Service Unit 10

------ Forwarded Message
From: <jingram at bbps.org>
Date: Thu, 20 Mar 2008 08:16:44 -0500
To: <jeverett at esu10.org>
Subject: Manila config.root trashed

=== UPDATE  Jim Ingram,   3/19/08 8:57 PM
One thing always leads to another. I noticed from home that I didn't have a
WYSIWYG editor in IE7 on Manila pages and determined that there had been
some updates to root files that I was unaware of. When I attempted to update
them from inside Frontier, it just kept timing out at the firewall. Don
fixed that, and it installed a bunch of updates to Frontier.root alone. I
came in later and attempted to update mainResponder.root, manila.root and
prefs.root. Somewhere in the process the config.root file got trashed. When
I tried to open any of the root files, I got an error that pointed to
'local(adrLegalMacros=@config.mainResponder.prefs.legalMacros)'. I
eventually noticed that in config.root the mainResponder branch was
completely empty. The suggested fix was to attempt to 'save a copy' to
compress the files, but it always gave the same error when I tried.

First I tried renaming config.root to config.root.old and restarting
Frontier. It generated a new config.root as it should, but it wouldn't open
the admin site and still generated error messages instead of displaying the
BBPS home page in a browser.

Then I went looking for old copies of config.root that might be closer to
what was needed. I found one that was about two years old (our sites haven't
changed much over the last two years) and plugged it in. Frontier came up
running, and web pages began displaying in the browsers. The Admin site
opens and lists the correct websites. I was eventually able to compress the
root files by 'save a copy', and dropped them in place. HOWEVER...

1. The menu across the top of the admin site is broken. In its place is the
following error message: 'Macro Error: Can't call the script because the
name 'version' hasn't been defined.'

2. If I try to update config.root from inside Frontier, I get an error
message that says, 'can't send you an update because the sysop hasn't
registered a database named 'config.root'.'

3. I've discovered that the automated backup process only backs up the
website content of the individual sites, and doesn't backup any of the
important root files. Is this correct?

So we are up and running with a visible website again, but who knows what
other issues might crop up. Jason, I need you to work your magic or talk me
through some things. Thanks.


------ End of Forwarded Message