313 - Display Suite instability

[treasuretron]

In GitLab by @thomasmurphy on Jan 28, 2019, 17:25

This bug is affecting #312 and #301 and would prevent future layout changes if these branches were merged. This is very unusual instability for display suite and may be a result of how customised the site is. Symptoms so far

1. Download database and codebase from dev
2. boot up locally and attempt to change the layout of a content type - OK
3. Install paragraphs
4. Attempt to change a content type layout - No
5. Uninstall paragraphs - no change.

[treasuretron]

In GitLab by @thomasmurphy on Jan 28, 2019, 17:26

changed title from Display Suite instability to {+313 - +}Display Suite instability

[treasuretron]

In GitLab by @thomasmurphy on Jan 28, 2019, 17:37

Second attempt

1. Reset to origin
2. reimported clean/old database dump
3. ran update.php
4. display suite is already dead

[treasuretron]

In GitLab by @thomasmurphy on Jan 28, 2019, 17:50

1. Reset to origin
2. reimported clean/old database dump
3. display suite is alive
4. run update.php (1 update - node module cache clear)
5. display suite is dead

[treasuretron]

In GitLab by @thomasmurphy on Jan 28, 2019, 19:01

upgrading to display suite from 3.1 to 3.2 solved this issue, although there is no related bug in the DS issue queue related to that release. It may have just cleared a module caching as part of the upgrade.

[treasuretron]

In GitLab by @thomasmurphy on Jan 28, 2019, 19:14

This is now stable on #301 and #312 but remember to run lando composer install, update.php and lando drush entity-updates on download a copy of the dev database.

[treasuretron]

In GitLab by @thomasmurphy on Jan 29, 2019, 00:07

closed

[treasuretron]

In GitLab by @thomasmurphy on Jan 29, 2019, 00:07

changed the description

[treasuretron]

In GitLab by @thomasmurphy on Jan 31, 2019, 17:22

hfixed here https://www.drupal.org/project/ds/issues/3028237