- Issue created by @Kristen Pol
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
Running the "Content provisioning" led to errors:
Configuration field.field.node.event.field_location depends on the Content Translation module that will not be installed after import.
Configuration language.entity.en depends on the Language module that will not be installed after import.
Configuration language.entity.und depends on the Language module that will not be installed after import.
Configuration language.entity.zxx depends on the Language module that will not be installed after import.
Configuration language.mappings depends on the Language module that will not be installed after import.
Configuration language.negotiation depends on the Language module that will not be installed after import.
Configuration language.types depends on the Language module that will not be installed after import.
Unable to provision theme_settings: There were errors validating the config synchronization. Configuration <em class="placeholder">field.field.node.event.field_location</em> depends on the <em class="placeholder">Content Translation</em> module that will not be installed after import. Configuration <em class="placeholder">language.entity.en</em> depends on the <em class="placeholder">Language</em> module that will not be installed after import. Configuration <em class="placeholder">language.entity.und</em> depends on the <em class="placeholder">Language</em> module that will not be installed after import. Configuration <em class="placeholder">language.entity.zxx</em> depends on the <em class="placeholder">Language</em> module that will not be installed after import. Configuration <em class="placeholder">language.mappings</em> depends on the <em class="placeholder">Language</em> module that will not be installed after import. Configuration <em class="placeholder">language.negotiation</em> depends on the <em class="placeholder">Language</em> module that will not be installed after import. Configuration <em class="placeholder">language.types</em> depends on the <em class="placeholder">Language</em> module that will not be installed after import.
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
It has success messages for:
- Successfully provisioned files.
- Successfully provisioned media.
- Successfully provisioned menu_links.
- Successfully provisioned permissions.
- Successfully provisioned site_settings.
- Successfully provisioned media_view.
- Successfully provisioned blocks.
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
After running the provisioning the
This block is broken or missing errors
are gone and the header and footer menu structure is okay.But, for the Starshot Demo, we will need to modify these to be what we want for the demo.
- Assigned to Kristen Pol
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
When switching to the subtheme it does not have any of the header/footer/menu structure which is probably what we want anyway.
- Issue was unassigned.
- Status changed to Postponed
4 months ago 8:35pm 9 August 2024 - πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
The language/translation ones are a starshot bug so put that in their queue:
#3467249: Starshot errors like: Language module that will not be installed after import β
So... everything worked here when provisioning except for the theme settings because of that bug.
Postponing this on that issue.
Once that's fixed, we can try the provision option again and, if working, add it to the documentation.
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
Keeping postponed since the underlying Starshot issue is postponed.
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
Since we don't need any of the sitebuilding stuff for Barcelona, keeping this postponed.
- Status changed to Active
3 months ago 8:13pm 9 September 2024 - πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
Might be good to get rid of the block config from optional so it isn't installed and then doesn't have these errors.
- Status changed to Fixed
3 months ago 8:37pm 9 September 2024 - πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
I've pushed the changes. Thought I was on the MR branch but was on main... whoops ;)
Anyway, changes are there so we won't get these errors anymore.
If we will continue to work on SDDS post-Barcelona then we need to figure out how we want to get these blocks to work OOTB so I'll create a separate issue for that.
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
Follow-up issue:
π [META] Determine SDDS sitebuilding approach with XB and Drupal CMS Postponed
Automatically closed - issue fixed for 2 weeks with no activity.