Timeline for How can I export only one paragraph type, the fields, the form settings and the display settings?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 15, 2020 at 7:11 | comment | added | Lance | Let us continue this discussion in chat. | |
| Oct 14, 2020 at 15:50 | comment | added | leymannx | Activate it on both sites. So that also on the source site Features is able to track changes to the paragraph type (new field, new display settings, whatever). | |
| Oct 14, 2020 at 15:10 | vote | accept | Lance | ||
| Oct 14, 2020 at 14:58 | comment | added | Lance | I have now both modules available on both sites (sounds logic in a multisite environment). I have only enabled the module on the site where I did not have the new content type. On the source sites I do not have to activate it right? | |
| Oct 14, 2020 at 12:18 | comment | added | leymannx | @Lance – Exactly. Because features are just modules in the end. Of course Features also comes with a set of Drush commands to export and import changes. When exporting an updated feature the module will then be rewritten and you can then go to your other multi-site where Features will tell you, hey there are changes in the feature module which ain't active on that site here, do you want me to import them? They then can be imported into the active config of this instance's database. From where you export the instance-specific config as usual, because every instance still has its own config. | |
| Oct 14, 2020 at 12:13 | history | edited | leymannx | CC BY-SA 4.0 |
Details
|
| Oct 14, 2020 at 12:13 | comment | added | Lance | So if I create a paragraph type on the main site (or other) then with Features you can manage to only export that specific paragraph type with all settings and import it into the other site? Without using drush cmd? I did not yet install the module, so it is a guess. | |
| Oct 14, 2020 at 12:10 | history | edited | leymannx | CC BY-SA 4.0 |
Details
|
| Oct 14, 2020 at 12:05 | comment | added | leymannx | @Lance – Yep, that's exactly why you manage each site from their own config (as usual). The Features module only is a helper to sync partial config into the database. From where it must be exported as site-dependant (normal) config. On live/prod then you leave the features untouched, you just import config (which then also contains the paragraph type on both sites). | |
| Oct 14, 2020 at 12:02 | comment | added | Lance | "then export config as usual" please explain in more detail. Keep in mind that config in this case) is not equal on all the different sites within the multisite approach. | |
| Oct 14, 2020 at 10:03 | history | answered | leymannx | CC BY-SA 4.0 |