Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Fix broken core-only config strategy #1358

Merged
merged 1 commit into from
Apr 11, 2017
Merged

Conversation

bkosborne
Copy link
Contributor

@bkosborne bkosborne commented Apr 11, 2017

The directory path for checking if the core.extension.yml file exists needs to be rooted to ${docroot}. I think there was a similar fix that I saw for config-split strategy, but it was missed for core-only.

The directory path for checking if the core.extension.yml file exists needs to be rooted to `${docroot}`. I think there was a similar fix that I saw for config-split strategy, but it was missed for core-only.
@grasmash grasmash added the Bug Something isn't working label Apr 11, 2017
@grasmash grasmash merged commit 6f5b38c into acquia:8.x Apr 11, 2017
grasmash pushed a commit that referenced this pull request Apr 12, 2017
The directory path for checking if the core.extension.yml file exists needs to be rooted to `${docroot}`. I think there was a similar fix that I saw for config-split strategy, but it was missed for core-only.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants