-
Notifications
You must be signed in to change notification settings - Fork 36
Known Issues
mywynne edited this page Apr 10, 2019
·
13 revisions
This page collects known issues and bugs, updates on those issues, and workarounds where possible.
- Some batch import/export tools are only being exposed to drupal admins, not Mukurtu Administrators.
- Exports should only be run by drupal admins.
- No footer box.
- If needed, a new block can be added.
- Original Date field in digital heritage importer erroneously populating current date if field is present but empty.
- If field is not being used, do not include at all in the import sheets.
- Recommend including a documented false/flag date so items can be corrected post-update.
- Original Date field (mm-dd) cannot be de-selected once values are entered.
- No current workaround.
- mp4 files not rendering properly in Safari.
- No current workaround
- Occasional issues with search index after upgrade.
- Some theme settings links from Dashboard not auto-directing to current theme.
- Manually check selected theme at top of pages before making changes.
- Language Steward cannot edit existing dictionary words.
- No current workaround without granting drupal admin role.
- GUID/NID fields not handling leading whitespaces in importers.
- Avoid leading whitespaces.
- Some native OG fields showing in community/protocol forms.
- No current workaround.
- Demo.zip file has incorrect path separators.
- Ensure that correct '/' separator is used in filepaths.
- Erroneous AJAX errors occurring.
- If the updates/imports/changes are successful, these can be safely ignored.
- Uploading Media Assets: When clicking the media asset icons on the SCALD library sidebar, nothing happens and media assets cannot be imported. This issue only affects certain Chrome browser configurations on PC.
- This bug was introduced in 2.0.8 and will be patched in 2.0.9.
- Media assets can still be imported through the "Add Media" link on the dashboard.
- This bug does not affect browsers other than Chrome on PC.
- This bug does not appear to affect any browsers on macOS.
- Roundtrip/Batch Import: The "Import Images/Audio/Video/Files" tools on the dashboard are not intended to be used for updating media metadata. The best way to edit media metadata is through the web interface, or by exporting content, then importing an updated spreadsheet.
- This is present in 2.0.8 and below. These links may be removed or modified in a future release.
- Collections: When viewing a digital heritage collection page, no digital heritage items are displayed.
- This bug was introduced in 2.0.7, and will be patched in 2.0.8 (May/June 2017 release).
- Digital heritage items can still be viewed grouped in their collections by filtering by collection on the digital heritage browse page.
- Book Pages and Multiple Media Assets: When adding a book page to a digital heritage, if a user attempts to add more than one media asset, a new digital heritage item will be created instead of a book page.
- This bug is present in 2.0.7, and will be patched in 2.0.8 (May/June 2017 release).
- A book page can be created with one media asset (or none), and once created can be edited and multiple media assets can be added.
- Book Pages and Anonymous Users: If a digital heritage item has no Author identified, book pages cannot be created for that item (the most likely cause is leaving the Username field blank when batch importing digital heritage metadata).
- You can edit the item, enter your username in the "Authoring information" field at the end of the page, and then create book pages as expected.
- Dewplayer media player: in some locations (eg: dictionary entries), the previous media player (dewplayer) is still showing instead of the newer HTML5 player.
- This bug is present in 2.0.7, and will be patched in 2.0.8 (May/June 2017 release).
- Roundtrip/Batch Import: The "Import Images/Audio/Video/Files" tools on the dashboard are not intended to be used for updating media metadata. The best way to edit media metadata is through the web interface, or by exporting content, then importing an updated spreadsheet.
- This is present in 2.0.7 and below. These links will likely be removed in a future release.