Hi, I’m updating Omeka S from 3.01 to the latest version (4.1.1).
I followed the instructions here Installing - Omeka S User Manual but I had incompatibility problems with all the modules, because they apparently asked for version 3.
Do I have to update moduls before the core?
Thank you very much for the help,
If you have an update of the core that raises the base version number (from 3 to 4 in this case), you will then have to go and update all of the modules to the most recent version that is compatible with the version of the core you are using. Those updates can happen after you update the core.
Hi @marco.orlandi ,
One approach would be to deactivate the modules before upgrading Omeka. This would allow you to upgrade and reactivate each module one-by-one. (You can also toggle module activation in the database if you’re site breaks after an upgrade.)
Also, I just wanted to share a video demonstrating how you can manage sites on the RefBytes Hosting Platform
In the video I show how you can easily copy an Omeka site, in this case to perform an upgrade and test before attempting to upgrade your production site. Alternatively, on the platform you can do a one-click upgrade with a database backup. If you run into issues, it’s a one-click restoration to revert your site back.
Dear Sharon, thanks for the reply, I tried exactly this way: I updated the core version, updated the database (Omeka was asking for it) and when I logged in and saw the plugin situation, I started updating them. Unfortunately, however, they kept telling me that they were asking for Omeka version 3. This happened to me for instance with Advanved Search, but also with Wikidata and others. Should I perhaps follow an order when updating plugins?
Thanks for the help!
Marco
Thanks! I’ll also try this way, maybe it will help to point out where the issue is!
Thank you also for the video, it’s a very useful option!
Those modules that are asking for version 3 of the core have not yet been updated by their creators to be compatible with version 4.
Yes, I understand that, the odd is that even modules like Wikidata, which is supposed to work fine also withe Omeka 4 (version 1.4 says “minimum omeka version 3”) still have issues after the update process.
And if I need a module which doesn’t have an Omeka 4 version, the only way is to stay with Omeka 3 until a new version of the module is released, right?
Thanks for the support,
M.
@marco.orlandi , when you look at the version constraint ^3.0.0, it means that it will work with any version of 3 up to 4, but not including 4. It doesn’t mean anything greater than 3.
Ahhhhh!!! I didn’t realise!!!
This is a quick module list I have installed. Some of them cannot be updated at Omeka 4, while others require Omeka 4. Can I ask for some advice on how to handle it?
Thanks for the help!
Advanced Search Plus version 3.3.5.3
Any Cloud version 1.1.5
Error: Any Cloud requires Omeka S ^1.3.0 || ^2.0.0
Bulk Edit version 3.3.12.4
CSV Import version 2.2.1
Custom Vocab version 1.3.1
Data Type RDF version 3.4.12
Error: Data Type RDF requires Omeka S ^4.0.0
DataScribe version 1.0.0-beta
Easy Install version 3.2.5by
Error: Easy Install requires Omeka S ^1.2.0 || ^2.0.0
Export version 1.5.0by
Extract Text version 1.2.1
Fields as Tags version 1.0.1
IIIF Server version 3.6.3.1
Bottom of Form
Image Server version 3.6.3.3
Item Sets Tree version 0.4.0
ItemCopy version 1.0.1
Mapping version 1.4.0
Metadata Browse version 1.4.0
Omeka 2 Importer version 1.4.0
PDF Embed version 1.2.0
RDF Datatype (archived) version 3.0.4.1
Error: RDF Datatype (archived) requires Omeka S ^1.1.0 || ^2.0.0
Reference version 3.4.27.3
Search version 0.8.0
Universal Viewer version 3.6.4.4
URI Dereferencer version 1.1.0
Value Suggest version 1.6.0
Wikidata version 1.3.0
Zotero Import version 1.2.0
@marco.orlandi , it sounds like you already know which modules can be upgraded and which can’t. I personally would start with the ones that can’t and decide whether or not you can live without them. Sometimes, modules are no longer maintained because the functionality has been included in Omeka, while other times, the developer has just abandoned the module. You’ll have to decide if you can live without that functionality or if you want to fork the module and maintain it yourself (assuming you’ve reached out to the developer and they are not interested in updating it).
After you go through that process, you will know whether or not you should upgrade Omeka or stay on the outdated version. If you decide to upgrade, then you could go through and upgrade each of the modules that can be upgraded.