Enabling core Field layout module fatals during installation

Since there are some issues and comments in other issues regarding the topic of compatibility issues between DS and Field layout core module with more or less good descriptions about it flying around, with some of them hijacked and half fixed, and others reporting to break the site and causing WSOD without a way out, I thought it would be important to start this meta issue and to try detangle all the issues in the mix to solve the compatibility issues between DS and Field Layout.

TL;DR Main motivation for this issue are several hijacks and reports complaining about if Display Suite and Field Layout core module are activated in a certain order causes unrevertable WSOD and there is no way out no more to disable the Field Layout before Display Suite.

List of possible related issues or issue comments in them to fix:

1. #2897810: Some fields are not shown when DS used with Field Layout core module →
2. #2878716: field_layout conflict with ds module →
3. 🌱 [plan] Add layouts to entity displays (both form and view) Active

EDIT: As stated in the comments many sites already seem to work flawless with both modules activated now but we do not know yet, if the order makes the difference. aspilicious moved this issue to core and gave some interesting insides for patching 🐛 Enabling core Field layout module fatals during installation Closed: cannot reproduce .

In case if this still hits you, it seems you can only solve this by disabling a module which is used to manage field and node view displays and which makes itself very mandatory when started to use. So this issue becomes slidely tricky in case if you have 70% finished your manage display settings with DS in your project and accidently activate the Layout Plugin module, you maybe loose all the work of a week if there is still something going on 🐛 Enabling core Field layout module fatals during installation Closed: cannot reproduce . In D8 you do not disable modules no more, you uninstall them. The chance that the settings are lost, is high. Additionally, in D8, the "way to view" content becomes more and more relevant regarding content relations and referencing (context). Without corresponding back references (not default in D8 references) many content is "lost in translation". This means, content can loose context when the display of it connected to other content is broken.

After Dries' great and encouraging keynote regarding the future of Layout API and its modules in core, many will possibly fall into this trap and we should warn them. He clearly states, that it is about D 8.5 and higher but many will think of a 50/50 chance to test the experimental modules already on early stage now below. I strongly recommend to put something in the respective project pages and docs until this issues are fixed.

Maybe useful comments from a hijacked issue fitting to the gathering point: #4 → , #5 → , #6 → , #7 →