Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Omeka 3.1.2 incompatible? #28

Open
StevensBrian opened this issue Mar 1, 2024 · 10 comments
Open

Omeka 3.1.2 incompatible? #28

StevensBrian opened this issue Mar 1, 2024 · 10 comments

Comments

@StevensBrian
Copy link

When we first installed the IIIF plugin, we got a 500 error, but when refreshing the plugin showed up among the installed Omeka plugins. When using the plugin, there were many errors thrown, and the embed wasn't displaying, so I decided to just uninstall it from the server end and reinstall it. It won't uninstall and throws the 500 error, and when activated, items/collections won't open on the public side. The Omeka folks sent me here. Note that we successfully installed the IIIF tookit and toolkit embed on our test server that runs a previous version of Omeka classic (3.0.3). Our problems came when we tried to implement it on our production server running 3.1.2.

@dicksonlaw583
Copy link
Collaborator

I am sorry to hear that the plugin is not running properly. To start, what is the PHP version on your instance?

@StevensBrian
Copy link
Author

StevensBrian commented Mar 4, 2024 via email

@dicksonlaw583
Copy link
Collaborator

I am not able to see the information in the email or on GitHub. Please try posting it in plain text form.

@StevensBrian
Copy link
Author

Omeka | 3.1.2
PHP | 8.0.29 (apache2handler)
OS | Linux 5.15.0-88-generic x86_64
MySQL Server | 8.0.36
MySQL Client | mysqlnd 8.0.29
Apache | Apache/2.4.52 (Ubuntu)

Regular | apache2handler, calendar, Core, ctype, date, dom, exif, FFI, fileinfo, filter, ftp, gettext, hash, iconv, json, libxml, mysqli, mysqlnd, openssl, pcre, PDO, pdo_mysql, Phar, posix, readline, Reflection, session, shmop, SimpleXML, sockets, sodium, SPL, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlreader, xmlwriter, xsl, Zend OPcache, zlib
Zend | Zend OPcache

ArchiveRepertory | 2.15.8
AtomOutput | 1.0.1
AvantCommon | 2.1.0 (inactive)
AvantSearch | 2.1.0 (inactive)
BulkMetadataEditor | 2.9
CSSEditor | 1.2
CatalogSearch | 1.0.3
Coins | 2.1.1
CollectionTree | 2.1
CsvImport | 2.0.7
CsvImportPlus | 2.3.2
DerivativeImages | 2.0
DocsViewer | 2.2 (inactive)
Dropbox | 0.7.2
DublinCoreExtended | 2.3
EmbedCodes | 1.0
ExhibitBuilder | 3.6.1
Geolocation | 3.2.3
GettySuggest | 1.3 (inactive)
HideElements | 1.4
Html5Media | 2.7 (inactive)
ItemOrder | 2.1
ItemRelations | 2.2.1
LcSuggest | 2.0.4
MlaCitations | 1.0
Neatline | 2.6.1 (inactive)
NeatlineFeatures | 2.0.5 (inactive)
NeatlineSimile | 2.0.4 (inactive)
NeatlineTime | 2.1.0 (inactive)
NeatlineWaypoints | 2.0.2 (inactive)
OaiPmhRepository | 2.2
OaipmhHarvester | 2.0.4
OmekaApiImport | 1.1.2
OpenLayersZoom | 2.6 (inactive)
PdfText | 1.3.1 (inactive)
RecordRelations | 2.0.1
Reference | 2.4.1 (inactive)
Reports | 2.0.2 (inactive)
SearchByMetadata | 1.2.1
ShortcodeCarousel | 1.0.1
SimpleContactForm | 1.1.1
SimplePages | 3.2.1
UserProfiles | 1.1

avantgarde | 1
berlin | 2.7.5
centerrow | 1.5.3
centerrow_noNav | 1.5.3
default | 2.7.1
emiglio | 2.4.2
hvd-dh-omeka-theme-master | 2.3
hvd-dh-omeka-theme-wcsu | 2.3 (current)
minimalist | 2.5.2
neatscape | 1.0-rc.2
rhythm | 2.4.2
santa-fe | 2.5.2
santa-fe-fci | 2.5.2
seasons | 2.7

@dicksonlaw583
Copy link
Collaborator

I tried replicating your Omeka (3.1.2), PHP (8.0.29), and MySQL (8.0.36) on a local Docker Compose setup, but I could not produce any errors from installing or uninstalling IIIF Toolkit 1.1.0. Your plugin listing is also missing IiifItems, which should be there if IIIF Toolkit is present (unless you explicitly deleted it at the file level). Do you have any logged error messages from when you first encountered the HTTP 500 errors?

Here is the Docker Compose setup that I used: iiifitems-github28.zip

You can set it up with ./setup.sh, then run it with docker compose up -d.

@StevensBrian
Copy link
Author

StevensBrian commented Mar 5, 2024 via email

@dicksonlaw583
Copy link
Collaborator

The first issue should be resolved by this upcoming commit: 2f2c37e

I will look into the uninstall routines of the plugin to make it more defensive in case of an installation error.

Among other changes, I will aim for a versioned update as soon as I can.

@dicksonlaw583
Copy link
Collaborator

@StevensBrian

The defensive uninstall routines are in: c43a532

If you don't mind testing it out on your setup, please download the current master branch, and let me know if the issues that you described persist.

@StevensBrian
Copy link
Author

StevensBrian commented Mar 7, 2024 via email

@dicksonlaw583
Copy link
Collaborator

I am glad to hear that the patched setup works for you. My colleagues at work would like to test this on some existing setups before moving forward with the 1.2.0 patch release. Please feel free to post on the Omeka forums about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants