Bug #6035
Import of CSV file via web UI throws fatal error (2.0.x only)
| Status: | Verified | Start date: | 11/28/2013 | |
|---|---|---|---|---|
| Priority: | Critical | Due date: | ||
| Assignee: | Dan Gillean | % Done: | 0% | |
| Category: | Import/Export | |||
| Target version: | Release 2.0.1 | |||
| Google Code Legacy ID: | Tested version: | |||
| Sponsored: | No | Requires documentation: |
Description
- Checkout AtoM stable/2.0.x branch
- Login as administrator
- Click "Import > CSV"
- Click "Browse" button, and select "Kiti_works.csv" CSV file (attached)
- Leave other settings at default (Archival description import, don't disable search index)
- Click "Import"
Resulting error
Result from stable/2.0.x @ eb4a479
Error encountered PHP Fatal error: Call to a member function enable() on a non-object in /home/vagrant/atom-2/lib/search/QubitSearch.class.php on line 57 Fatal error: Call to a member function enable() on a non-object in /home/vagrant/atom-2/lib/search/QubitSearch.class.php on line 57
Expected result
A checkout of AtoM 2.x@6e72a07 returns:
Error encountered Could not find information object matching slug "church-of-panagia-angeloktistos-kiti-cyprus"
(Assuming parent record does not exist)
Kiti_works.csv 
- Sample CSV file
(1.8 KB)
pub-status.png (23.3 KB)
History
#1 Updated by David Juhasz over 8 years ago
- Description updated (diff)
Copy & paste correct error message
#2 Updated by David Juhasz over 8 years ago
Cherry picked commit:f5e6aea commit:fce9910 commit:b21cc9d from 2.x
#3 Updated by David Juhasz over 8 years ago
- Status changed from New to QA/Review
- Assignee changed from David Juhasz to Dan Gillean
#4 Updated by David Juhasz over 8 years ago
- Subject changed from Import of CVS file via web UI throws fatal error (2.0.x only) to Import of CSV file via web UI throws fatal error (2.0.x only)
Fix typo
#5 Updated by David Juhasz over 8 years ago
- File Kiti_works.csv added
Note: To test sample CSV file, create a description with "church-of-panagia-angeloktistos-kiti-cyprus" slug before import.
#6 Updated by Dan Gillean over 8 years ago
- File pub-status.png added
- Status changed from QA/Review to Verified
I tested by 1) creating the parent description, and then importing directly under the parent (i.e. with CSV import option in context menu of parent), as well as 2) creating the parent description and then using the Import option in the Main Menu. In both cases, import worked.
One note - errors were thrown for each description on the publication status. See attached screenshot. This seems to me to relate to issue #5832 and/or #5945 - the import still worked, but the pub status reverted to the application default. consequently, I am marking this as verified - we can deal with publication status roundtrip issues on one of the related tickets.