[Archivesspace_Users_Group] Components not loading in Public UI

[Jason Loeffler]

You're correct, the path on the staff side should
include #tree::resource_21.

What's the URL for your public interface?

JL

On Thu, Feb 11, 2016 at 3:22 PM, Helen Thomas <helen.thomas at nicholls.edu>
wrote:

> Jason,
>
> Thanks for the quick reply. I am running version 1.4.2. All of my records
> are affected on the public interface.
>
> I have only tried to edit two resource records since this started
> happening. For the first one (which I edited extensively using RDE), I
> can't see anything from the staff interface. In fact, when I click View or
> Edit, my browser goes to this URL (
> http://archives.nicholls.edu/staff/resources/21/edit) where I can only
> see a blank white screen. Based on the other records that I can see on the
> staff interface, I think that this URL should be
> http://archives.nicholls.edu/staff/resources/21/edit#tree::resource_21,
> and I am being somehow redirected. When I use that URL, I am taken to this:
>
>
> The other records are displaying perfectly on the staff side, even the one
> that I just did a small edit to today (added only a series title). None of
> these are entirely new collections - I'm currently trying to edit records
> that I imported as MARC catalog records.
>
> Helen
> ​
>
> On Thu, Feb 11, 2016 at 2:01 PM, Jason Loeffler <j at minorscience.com>
> wrote:
>
>> Helen,
>>
>> Can you tell me your ArchivesSpace version number?
>>
>> Are you unable to view records from both the staff interface and the
>> public interface? Does it affect all records or just newly created records?
>>
>> Jason Loeffler
>> Technology Consultant
>> The American Academy in Rome
>> Minor Science | Application Development & Metadata Strategy
>> Brooklyn, New York
>>
>>
>> On Thu, Feb 11, 2016 at 2:41 PM, Helen Thomas <helen.thomas at nicholls.edu>
>> wrote:
>>
>>> Hello all,
>>>
>>> I'm experiencing a problem where none of the components for my resource
>>> records are loading in the public interface. Instead, I get a perpetual
>>> loading GIF that never goes away. I noticed this after I attempted to add
>>> components to a couple of records. At first I thought that just those
>>> records had crashed (one now shows a completely blank screen for the staff
>>> side of the record in either edit or view mode), but after checking I found
>>> that none of my resource components are loading. We have recently upgraded
>>> to a production server, but the tech at campus IT believes this component
>>> issue to be software related.
>>>
>>> Does anyone have an idea what may be going on or how to address this
>>> problem?
>>>
>>> Best,
>>> Helen
>>>
>>> --
>>> *Helen Thomas*
>>> Assistant Archivist
>>> Ellender Library, Nicholls State University
>>> helen.thomas at nicholls.edu | (985) 448-4644
>>>
>>> _______________________________________________
>>> Archivesspace_Users_Group mailing list
>>> Archivesspace_Users_Group at lyralists.lyrasis.org
>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>>
>>>
>>
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>>
>
>
> --
> *Helen Thomas*
> Assistant Archivist
> Ellender Library, Nicholls State University
> helen.thomas at nicholls.edu | (985) 448-4644
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160211/d6119312/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: LoadingLegendre.JPG
Type: image/jpeg
Size: 25421 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160211/d6119312/attachment.jpe>