This is a tough one, but if anyone can point me in the right direction for troubleshooting, that would be greatly appreciated. In trying to use the Omeka Classic Importer module on a new Omeka S installation, all I get when entering the url of the Omeka Classic site api is: “Omeka S encountered an error” with a link to instructions for setting up logs. However, the logs are not capturing the error, and nothing shows up in the Jobs. Logging is enabled in local.config.php, but is there another log location that captures module errors?
I’ve confirmed that the api of the old site is enabled by entering the url and clicking on the link that shows available api resources. The module doesn’t even get that far though, so I’ve ruled out any issue with the old site api. I have gotten similar, unspecified errors with certain modules, but have not investigated, as those modules are not that important.
One thought I had was that the php path needs to be set manually in local.config.php, but the php path shows up just fine when I click on the system information. We have another installation of the newer, alpha version of Omeka S on another subdomain, which is why I thought maybe the php path needs to be set. But that’s really a shot in the dark. Not sure what could be causing the error. We have uninstalled and reinstalled the module, with no luck.