Mirador Block (deprecated)¶
The blockmirador module is deprecated. Its Mirador Block Viewer block is part of wisski_mirador now.
Installation¶
Enable it only on a site that still has the old block. It depends on wisski_mirador. Follow Update before uninstalling it.
Configuration¶
The block settings (IIIF Field Number, Viewer Height) stay on the placed block. New external manifests are configured on the WissKI Mirador block.
Update¶
blockmirador now depends on wisski_mirador. That module needs the contrib modules imagemagick, image_effects and colorbox (through wisski_iip_image), which WissKI only suggests. Require them before updating WissKI, if your site does not have them yet:
composer require drupal/imagemagick drupal/image_effects drupal/colorbox
Then run drush updb. The update
- installs
wisski_miradortogether with the modules it needs and that are not enabled yet:wisski_iip_image,wisski_salz,views,datetime,text,imagemagick,image_effectsandcolorbox, - saves every placed Mirador block with
wisski_miradoras provider. The block ID, its region, IIIF Field Number and Viewer Height stay as they are.
Until drush updb has run, placed Mirador blocks show as broken. If wisski_mirador cannot be installed, the update says so and the blocks stay broken but keep their settings. Installing wisski_mirador later, for example with drush en wisski_mirador, moves them then.
Nothing else changes for the blocks: the markup (.mirador_block, data-blockmirador-viewer), the drupalSettings.blockmirador key and the library name blockmirador/viewer stay. A Mirador build in /libraries/mirador keeps being used while the WissKI Mirador Integration library is not installed, so no new library download is needed.
Uninstall¶
After drush updb you can uninstall blockmirador. The blocks no longer depend on it and are kept:
drush pm:uninstall blockmirador
Code that extends Drupal\blockmirador\Plugin\Block\BlockMirador must extend Drupal\wisski_mirador\Plugin\Block\MiradorBlock instead before.