The old flash of red in lieu of an error message trick! I hate when that happens.
I can't think of what about adding a 3rd level child ou could upset the system but that is not saying much! Generally the flash of red has told me that a low level database error of some kind has occured. When this has happened with me, I set my log level high in /openils/conf/opensrf_core.xml, I get my staff client set to just before the moment of activity that throws the error, I then clear /openils/var/log/osrfsys.log and force the error. If you make a quick copy of /openils/var/log/osrfsys.log right after the error it's easier to read the log snippet. usually the log will reveal the underlying database error. So far it has always pointed me at a config step I either skipped or missed that my red flash step relied on. ________________________________________ From: [email protected] [[email protected]] On Behalf Of Joe Atzberger [[email protected]] Sent: Thursday, September 30, 2010 6:47 PM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Adding OU's in the client I used to see this error consistently before whatever caused it was eventually fixed. --joe On Thu, Sep 30, 2010 at 4:57 PM, Metcalf, Steve <[email protected]<mailto:[email protected]>> wrote: This is in the 1.6.0.6 client. When I click on New Child in a level-2 record, I get a flash of red background and the new level-3 record doesn’t appear until after I reload the Server Administration/Organizational Units page. Is there a way see and open the new unit for editing without the need to go back to the Admin menu? Steve Metcalf THE EVERGREEN STATE COLLEGE
