OmekaS - Package Updates
-
[1.1.1]
- Update Omeka S to 4.0.1
- Full changelog
-
[1.1.4]
- Update Omeka S to 4.0.3
- Full changelog
- Malformed/malicious non-image files could improperly be allowed as uploaded assets
- Installation title was not properly escaped when displayed in several views
- The accept attribute for the upload input for assets was not updated to match the new default allowed asset types
- Uploaded assets are now checked for both type and extension
- Alongside the configurable list of allowed asset types introduced in 4.0.2, there is now a configurable list of allowed asset file extensions
-
[1.1.5]
- Update Omeka S to 4.0.4
- Full changelog
- Page titles were not properly escaped on the admin pages list for a site if viewed by lower-privilege users without permission to edit
- Lower-privilege users could view the info on other users' user edit pages
- Updated translations for Brazilian Portuguese, Dutch, French and Mongolian
-
[1.2.0]
- Update Omeka S to 4.1.0
- Full changelog
- Page authoring improvements
- Performance improvement for performing many "OR"-joined property/value searches at once
- Site navigation allows user to configure a custom link to open in a new tab/window
- New settings for controlling appearance of subnavigation on public site pages
- New batch edit option for setting resource ownership
- OEmbed media can now be updated
- Site setting for pre-expanding value annotations
-
[1.2.1]
- Update Omeka S to 4.1.1
- Full changelog
- Custom thumbnails set on a primary media will also be used when getting a thumbnail for the parent item
- The "no sites" message never disappeared when adding the first site on the add/edit item page in 4.0.0
- Item sets were not sortable in the site resources section in 4.0.0
- Themes did not show new version notifications in 4.0.0
-
[1.3.0]
- Update base image to 5.0.0
-
[1.3.1]
- Add checklist
-
[1.4.0]
- Update omeka-s to 4.2.0
- Full Changelog
- New version notifications were not being shown correctly for the core
- The confirmation message warning users that they made changes which would be lost if not saved could trigger improperly on the site navigation admin page when no changes were actually made
- An error that could arise when viewing the system information page with no subfolders yet under the "files" folder (#2196, fix contributed by Andreas Warnaar)
- Custom thumbnails for primary media were not used when getting the thumbnail for a parent resource
- The media show page could show an Edit button even if the current user did not have permission to edit the media
- An error happened preventing the proper response when performing a REST DELETE operation when
@reversewas enabled in the API - Event listening did not work properly for some forms
- Public "front page" cross-site advanced searches were broken