search

omeka-s-modules / Osii

Import items from other Omeka S installations
GNU General Public License v3.0
2 stars 0 forks source link

Error importing with Omeka S version 4.1.1 #15

Open akprtll opened 2 months ago

akprtll commented 2 months ago

As a test, I tried to import 2 items from an installation on a different server into a freshly set-up version of Omeka S 4.1.1 and received the following error message:

Doctrine\ORM\ORMInvalidArgumentException A new entity was found through the relationship 'Osii\Entity\OsiiImport#snapshotJob' that was not configured to cascade persist operations for entity: Omeka\Entity\Job@1401. To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or configure cascade persist this association in the mapping for example @ManyToOne(..,cascade={"persist"}). If you cannot find out which entity causes the problem implement 'Omeka\Entity\Job#__toString()' to get a clue.

Full error message is attached, with "~URL HERE~" substituted for the path on my server. OSII Error.txt

jimsafley commented 2 months ago

I can't reproduce the error. "A new entity was found" errors are difficult to troubleshoot, but they're sometimes transient. Try running the snapshot several times. If the problem continues I'll need the "Root endpoint" you're using so I can match your setup.

akprtll commented 2 months ago

I've tried a couple of different things and it's still not working. I am trying to import items from a 3.1.1 installation into 4.1.1 -- would that have any bearing on the issue?

jimsafley commented 2 months ago

I don't think the version of the remote installation could cause this. Perhaps it's a bad interaction with some module? Deactivate all modules but Omeka S Item Importer and try the import again. I still would like the "Root endpoint" you're using, if it's accessible.

akprtll commented 2 months ago

The API I'm importing from is www.migrantconnections.org/api. I've just tried deactivating the modules on the site I'm importing into and right now the jobs are running (rather than an immediate error message, which is what I got the last time around).

jimsafley commented 2 months ago

There's a bad interaction with a module. You could deduce which module is responsible by activating one module at a time and attempting an import.