You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+196-2
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,201 @@
6
6
7
7
## Future Development
8
8
9
-
Islandora Defaults is no longer under active development. Its core purpose is being superceded by a project to create an example Starter Site. You can read the announcement [here](https://groups.google.com/u/1/g/islandora/c/uGzhTnW4TUI).
9
+
Islandora Defaults is no longer under active development, and is being deprecated. Its core purpose is being (and has been) superseded by a project to create an example Starter Site, which [exists in the `islandora-starter-site` repository](https://github.com/Islandora/islandora-starter-site). You can read the announcement [here](https://groups.google.com/u/1/g/islandora/c/uGzhTnW4TUI).
10
+
11
+
### Deprecation/Removal Preparation
12
+
13
+
To ease the removal of this module from existing installations, we have implemented a post-update hook which should remove any references to this module from configuration entities that it installed. To make use of it, it should be sufficient to update to the `islandora/islandora_defaults` package in your Drupal project such that it includes the new hook, and to run it. On the CLI, this might be effected as something like:
14
+
15
+
```bash
16
+
# Navigate to the root of your Composer project; for example:
17
+
cd /var/www/html/drupal
18
+
19
+
# Update islandora/islandora_defaults such that it has the post-update hooks
20
+
# available. Presently anticipating a "3.0.1" release to which it should update.
# A caveat exists in that, if `islandora/islandora_defaults` is required by any
23
+
# other Composer package, then those packages may have to be updated first; for
24
+
# example, it is known that there exist Drupal installation profiles that
25
+
# specify a dependency on `islandora/islandora_defaults` (such as https://github.com/Islandora-Devops/islandora_install_profile_demo/blob/181a53bb230d7ced6e70e7746f0da567216ebbf7/composer.json#L157),
26
+
# which would likely have to receive a treatment to strip out any references
27
+
# from their configurations which explicitly bind to `islandora_defaults`
28
+
# similar to our update hook, and to include updated requirements accordingly
29
+
# in the root Composer project.
30
+
31
+
# Clear cache (paranoia; to ensure the update hooks are appropriately
32
+
# discovered).
33
+
drush cr
34
+
35
+
# Run the update hook.
36
+
drush updb
37
+
38
+
# Now that our config entities should stay behind, the module itself should be
39
+
# fine to be uninstalled. Note that this should/may also result in the
40
+
# uninstallation of the islandora_oaipmh and islandora_search modules; though,
41
+
# the configurations they included should remain in the system.
42
+
drush pm-uninstall islandora_defaults
43
+
44
+
# Perform a dry-run removal to list out all that would be removed, when
45
+
# islandora/islandora_defaults is removed, as some modules may only be included
0 commit comments