OmekaS - Package Updates

[girish]

[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

[Package Updates]

[1.3.0]

• Update base image to 5.0.0

[Package Updates]

[1.3.1]

• Add checklist

[Package Updates]

[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 @reverse was enabled in the API
• Event listening did not work properly for some forms
• Public "front page" cross-site advanced searches were broken

[Package Updates]

[1.4.1]

• Update omeka-s-module-Ldap to 0.6.0
• Full Changelog
• Log all error message when authentication fails
• Handle authentication when user is inactive
• Add update hook

[Package Updates]

[1.5.0]

• Update omeka-s-module-Ldap to 0.7.0
• Full Changelog
• Add update hook on existing ldap user
• Improve attributes retrieval by asking all ldap attributes and using it
• potentially in another module

[Package Updates]

[1.5.1]

• Update omeka-s to 4.2.1
• Full Changelog
• Block titles for the IIIF page blocks were not properly escaped
• The IIIF presentation page block did not respect the site's configured IIIF viewer setting for the Mirador theme
• Some fields were not aligned properly on the admin advanced search
• Themes could not use the Ckeditor form elements to allow HTML input for theme settings
• Unnecessary spacing when listing data types in resource template browse
• Modules using older code for database queries could encounter errors related to core events like those used for processing fulltext search
• The Asset add form only allowed a fixed list of file types regardless of what types were specified in config
• The confirm password check did not properly run when the confirm box was left blank