Bug #7498

EAD import and Export broken in 2.2.x branch

Added by Dan Gillean over 7 years ago. Updated about 7 years ago.

Status:VerifiedStart date:11/10/2014
Priority:CriticalDue date:
Assignee:Misty De Meo% Done:

70%

Category:EAD
Target version:Release 2.2.0
Google Code Legacy ID: Tested version:2.2
Sponsored:No Requires documentation:No

Description

To reproduce
1) Navigate to a description with children
2) Click export EAD

Resulting error: 500 internal server error - see attached stack trace

3) Try to import an EAD description created in an earlier 2.x version of AtoM - see attached EAD as an example. (This file was tested first on the stable/2.1.x branch to ensure the EAD would import)

Resulting error: 502 Bad Gateway

There have been several changes in the EAD for 2.2 - Misty has made significant changes in #5094, and Mike G has made EAD fixes based on other client projects recently. Any of these might be affecting the import/export, and should be considered when trying to diagnose the issue.

500-error-export-stackTrace-cooke-fonds;ead.xml Magnifier (5.6 KB) Dan Gillean, 11/10/2014 10:52 AM

artefactual-test-fonds;ead.xml Magnifier (22.1 KB) Dan Gillean, 11/10/2014 10:53 AM


Related issues

Blocks Access to Memory (AtoM) - Bug #5094: RAD EAD Dates improperly encoded when not Dates of creation Verified 05/16/2013

History

#1 Updated by Dan Gillean over 7 years ago

In case it is of use, I recently tried to do a bulk CLI import on my local install of qa/2.2.x - the attempt failed immediately, with the following error message:

PHP Fatal error: Call to a member function getActor() on a non-object in .../lib/QubitXmlImport.class.php on line 895

#2 Updated by Mike Gale over 7 years ago

This bug was introduced with Misty's fixes for events... see: https://github.com/artefactual/atom/commit/c4dd3a16ea2682534b06b974761f6c8a2607eec4#diff-388a807e866482e6526be428c356959eR877

I don't think it will be a hard fix. I'll probably have time this week to fix it.

#3 Updated by Dan Gillean over 7 years ago

Mike that would be great. It's actually blocking me on testing I'd like to do for a client migration, to see if Misty's 2.2 fixes will resolve issues I'm seeing during test import. And you happen to be the dev on that migration :D

#4 Updated by Misty De Meo over 7 years ago

Oh no! The monster at the end of the commit... was me!

#5 Updated by Misty De Meo over 7 years ago

  • Status changed from New to Code Review
  • Assignee changed from Mike Gale to Misty De Meo

#6 Updated by Mike Gale over 7 years ago

It looks good to me Misty, go ahead and merge. Thanks!

#7 Updated by Misty De Meo over 7 years ago

  • Status changed from Code Review to QA/Review
  • % Done changed from 0 to 70

Merged into qa/2.2.x; ready for QA.

#8 Updated by Dan Gillean about 7 years ago

  • Status changed from QA/Review to Verified

Also available in: Atom PDF