(repost)
I’m not sure if I’m doing anything wrong, but when I upgrade our installation of Omeka 2.1-rc to Omeka 2.1 (through Github) and I upgrade the database, the whole omeka_items table gets ruined. All Item_type_id’s are set to NULL so no single Item has Item type specific data anymore.
Also, the API tab does not appear in my settings.
Any suggestions or ideas?
The issue with the item_type_ids should be fixed in Github.
The API tab, I'm not aware of something that would make it not appear. Are you still using a "super" user?
Thanks for the fix. Updating now seems to give no problems.
Yes I am super user. Also, in the settings table "api_enable" is set to 1.
What is the slug of the API tab? (so I can see if I'm allowed to navigate there)
Edit: I can't navigate to "admin/api"
slug should be admin/settings/edit-api
I found the problem. We are running an adjusted version of the admin theme because plugin hooks weren't doing the trick. I guess we'll have to keep up with the changes manually.
Which plugin hooks are misbehaving? We might be able to add them to 2.1.1
It's not a matter of misbehaving. For instance, we wanted to add colors and extra tabs to the to the search result pages. Also we completely changed the search forms. And there is more to come.
I'm sure there could be nice hooks for that, but I think it might become a huge forest of plugin hooks everywhere.
(modified admin theme: https://github.com/iwemuiser/admintheme-verhalenbank/commits/master )
The migration issue is fixed in Omeka 2.1.1
Hi, we just upgraded from v. 2.0.4 to 2.1, and experienced the problems described above (item_type_id set to NULL for the majority of our records). We were lucky in that we only had one item type for all records, so it was easy to fix with an SQL statement.
We still have a couple Omeka instances to upgrade, and in those cases we have multiple item types. Should we just migrate straight from 2.0.4 to 2.1.1? I'm just worried about that data getting lost if upgrading to 2.1.
Thanks,
Jeremy
I'd say make sure you have a backup of the database, then jump right to 2.1.1.
Correction -- we released 2.1.2 last week, so jump right to that.