Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grav - Gantry's Extras Menu Prod/Dev Toggle creates deprecated custom environment path instead of using user/config/plugins/ #3169

Open
blizam opened this issue Aug 10, 2023 · 1 comment

Comments

@blizam
Copy link

blizam commented Aug 10, 2023

If I toggle Gantry from Production to Development under the Extras menu when it goes to write the gantry5.yaml file it creates a old-style custom environment path directly under /user/ like

/user/www.domain.com/config/plugins/gantry5.yaml

the ONLY thing that will be in the file is the "production" attribute and true|false value... no settings that are in the main user/config/plugins/gantry5.yaml are retained/copied.

This does NOT happen if I go to Extras > Platform Settings and change the "Production Mode" (or any other setting) there... this only happens with the Toggle in the Extras submenu.

This then creates further issues when other Grav plugins (or Grav itself) see this old-style (not that it should be happening at all, but it should now be /user/env/www.domainname.com/) custom Environment folder and start to write their YAML files there as well.

@blizam
Copy link
Author

blizam commented Aug 10, 2023

Note my issue here as well #2605 (comment)

.... with gantry.siteUrl() not evaluating properly on this same server... unsure if related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant