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

[Bug]: unable to delete graphql configuration #16849

Closed
Abdelrhman02 opened this issue Mar 26, 2024 · 3 comments
Closed

[Bug]: unable to delete graphql configuration #16849

Abdelrhman02 opened this issue Mar 26, 2024 · 3 comments

Comments

@Abdelrhman02
Copy link

Pimcore version

11

Steps to reproduce

I don't know how can reproduce it

Actual Behavior

should able to delete data-hub configuration
image

I deleted it from var/config/data_hub folder but it still here

I can't save or delete or clone the configuration.
image

Expected Behavior

should be able to delete configuration from pimcore UI or by deleting the config file from var/config/data_hub

@podarcis
Copy link
Contributor

Seems that you're in an environment that uses config write-target symfony-config for your Data-Hub configs and your environment is cached (probably prod). This is the expected behavior, see https://pimcore.com/docs/platform/next/Pimcore/Deployment/Configuration_Environments/#production-environment-with-symfony-config

You can either clear the Symfony caches (ideally integrated in deployment) or change the write-target to settings-store and have your configs in the DB and thus editable in prod, however not under version control.

Copy link

Thanks a lot for reporting the issue. We did not consider the issue as "Pimcore:Priority", "Pimcore:ToDo" or "Pimcore:Backlog", so we're not going to work on that anytime soon. Please create a pull request to fix the issue if this is a bug report. We'll then review it as quickly as possible. If you're interested in contributing a feature, please contact us first here before creating a pull request. We'll then decide whether we'd accept it or not. Thanks for your understanding.

@fashxp
Copy link
Member

fashxp commented Apr 15, 2024

I'll close this, as the reason is explained by @podarcis. Thx very much!

@fashxp fashxp closed this as completed Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants