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
Today a site enabled Islandora Context, which promptly disabled a pile of other modules. No alert was given. I believe this may have happened to another site a year or two ago. Have you encountered this problem?
The text was updated successfully, but these errors were encountered:
Did they enable it via the Drupal GUI or the command line (I assume GUI)?
What modules were disabled by enabling Islandora Context?
Did they enable the core Context already or allow it to be enabled automatically as a dependency when they enabled Islandora Context?
To try to replicate the problem, on a clean Vagrant, I enabled Islandora Context via the Drupal UI (saying yes to Drupal enabling the dependency Context) and could not replicate the problem. Before I enabled it, I queried Drupal's system table to see how many modules/themes were enalbled:
mysql> select count(*) from system where status = 1;
+----------+
| count(*) |
+----------+
| 127 |
+----------+
1 row in set (0.00 sec)
and then after I enabled it, I reran my query, which shows two more modules, which would account for islandora_context and its dependency context (which Drupal enabled automatically):
mysql> select count(*) from system where status = 1;
+----------+
| count(*) |
+----------+
| 129 |
+----------+
1 row in set (0.00 sec)
I'll need more information in order to troubleshoot this further.
Today a site enabled Islandora Context, which promptly disabled a pile of other modules. No alert was given. I believe this may have happened to another site a year or two ago. Have you encountered this problem?
The text was updated successfully, but these errors were encountered: