Hi Jennifer, This sounded familiar, and I wonder if you've taken a look at this reply by Jennifer Pringle (from Sitka) where she suggests it may be a working locations / permissions issue for the staff accounts attempting to access users.
See threaded discussion: http://markmail.org/message/ec7pucv23mhq7fuz Have you looked at the working locations for the staff users to determine if her hypothesis was correct? -- Ben On Tue, Nov 11, 2014 at 2:05 PM, Walz, Jennifer <jlw...@asbury.edu> wrote: > All - > > > > Ok. I'm new to evergreen, but I am pretty sure that all the display within > the staff client is governed by html code / files, right? I mean, if you > hit the "debug" button, you see the html code. > > > > So. We are still having problems with our patron records displaying. > In other words, we get a blank screen (almost) in the staff client window > when we go to edit a patron record. We also cannot register a patron. The > same screen displays. Like this: > > > > > > Some of the buttons are displaying, but not the rest of the form – and no > data. Data is all there in the system, but it does not display. > > > > What is wrong?? I am guessing it has to do with the html code is not > getting the right info from a js file or some part of the code is > corrupted. I investigated this by looking at our development server > files. We CAN view the patron records there with no trouble. I hit the > “debug” button there and printed off that file, and did the same in the > client that is not working. I DO notice that there are differences in the > code and some lines are missing or not in the same places. > > > > How do we fix this? Is this really the problem? Can we just > simply re-install (copy etc) the file from our development server over to > the other one? The source from debug is: > oils://remote/eg/actor/user/register Should all the files in that > directory also be swapped out? Is there a js file call that is > necessary that maybe got corrupted or deleted? > > > > Can anyone give any guidance on this? Is it possible that the files on > the server have gotten corrupted? Is there a way to make this easy? Or > do we have to do a complete reload of the files? > > > > Thanks! > > > > Jennifer > > -------------------------------------------------- > > Jennifer Walz, MLS - ILS troubleshooter > > Kinlaw Library - Asbury University > > One Macklem Drive, Wilmore, KY 40390 > > 859-858-3511 ext. 2269 > > jlw...@asbury.edu > -- Benjamin Shum Evergreen Systems Manager Bibliomation, Inc. 24 Wooster Ave. Waterbury, CT 06708 203-577-4070, ext. 113