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

project.yaml support - no way to add/change text in production or staging environments #12

Closed
toddpadwick opened this issue Aug 29, 2019 · 4 comments

Comments

@toddpadwick
Copy link

Using project.yaml requires adminstration access to be revoked on production and staging. This means that there is no way to currently add/edit the cookie text in anything other than dev/local and copy the database over.
Will there be support for this anytime soon?

@mark-adigital
Copy link
Contributor

Hi @toddpadwick - I'll look to add a separate settings page as these can still be accessed and edited with allowAdminChanges set to false. In the shorter term, as I don't believe there's any technical requirement that admin changes are disabled when using project config you could temporarily enable admin changes in your live environment to configure the plugin - provided this doesn't clash horribly with your workflow!

@toddpadwick
Copy link
Author

toddpadwick commented Aug 30, 2019 via email

@mark-adigital
Copy link
Contributor

Hi @toddpadwick - apologies for the long delay, but I just today released an update with various new configuration options, including migration of plugin settings via project.yaml by using UIDs for settings rather than IDs. Hopefully that helps with the issue you raised when allowAdminChanges is set to false.

@toddpadwick
Copy link
Author

Hi @mark-adigital this is great news! Appreciate the update, this will really help us out :)

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

2 participants