[Archivesspace_Users_Group] white screen lock-out

[Elizabeth Dunham]

Hi all,

I've had the same issue as Annie and Lydia - I get the white screen lockout when using RDE with Chrome.  I've found it doesn't happen with Internet Explorer and it generally lasts for a few days.  I reported it and it's logged as AR-1372, but the following notes indicate that it couldn't be replicated.

I also checked the URL for my ArchivesSpace instance, and we aren't using a proxy (or at least I don't have :8080 in the URL).

Best,
Elizabeth Dunham

------------------------
Assistant Archivist
Arizona State University Libraries
Archives and Special Collections
Tempe, AZ 85287-1006
Elizabeth.Dunham at asu.edu

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick
Sent: Wednesday, March 30, 2016 10:23 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] white screen lock-out



Hm. 

And Annie you get the same white screen when it locks out? 

Yeah, 10 rows shouldn't be too many ( I was thinking like 50 or more ). And if you're getting the same white screen with different browsers, then we can rule that out. Do the Resources have a lot of child archival objects? Like a child with hundreds of direct siblings?

Also..weird technical question but do you know if you're using a proxy? Like is your archivesspace have the :8080 port numbers in the URL or not? 

b,chris. 

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048 http://archivesspace.org/

________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Annie Benefiel <benefiea at gvsu.edu>
Sent: Wednesday, March 30, 2016 6:53 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] white screen lock-out

I have experienced a similar problem using RDE (also in Chrome browser). I have found that when it happens the resource gets "locked out" for about a day, and is accessible when I come back to it the next day. Even attempting to access the resource in another browser fails (tried IE and Firefox). Not so great when you've got a lot of data to enter! In my experimentation I have found that validating the rows before saving them seems to help prevent the "lock out" problem. But I haven't exactly been scientific about it. For longer finding aids I'm using a MS Excel>EAD>ASpace workflow to prevent data loss and lock outs.

Annie Benefiel
Assistant Archivist
Grand Valley State University
Special Collections & University Archives
(616) 331-8727
www.gvsu.edu/library/specialcollections