-
Notifications
You must be signed in to change notification settings - Fork 110
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
[Feature]: Allow to save Defintions with APP_DEBUG=false #531
Comments
Please take a look here, section "Configuration Storage Locations & Fallbacks" Does this solve your problem? |
Closed due to inactivity, feel free to reopen the issue if needed. |
This does not solve our problems. We want to save and edit the data-hub on the production system with APP_DEBUG=false. We need APP_DEBUG=false, because the workflow engine does not send emails if we set APP_DEBUG=true. We have some editor users, that must have the possibility to change the settings of the data-hub. |
Did you try to set
in your env file? |
Maybe you can take a look here too |
@ThomasGravel have you been able to solve your problem? |
this does not work for me in PIM 11 |
Does not work for me either on Pimcore version 11.2.6 |
@mcop1 the I have found that setting the below in config.yaml does enable the "Add configuration" button on the DataHub, but the existing data-importer configs cannot be saved
|
Hello @marko91, The reason for your problem could be that some configurations are stored as yaml configuration and some are stored in the settings store. If you set the |
Hi, I have a similar problem and despite reading the documentation I don't know how to solve it. Locally everything works fine. In the production environment I can't delete or edit (save) the configuration. What should the configuration be to be able to edit the endpoint on prod? |
Feature description
We need to save the data-hub config with APP_DEBUG=false, because the workflow engine sends emails to the user only if the APP_DEBUG=false.
We now overwrite the isWriteable function in the Configuration.php, but I think this is not the solution.
The text was updated successfully, but these errors were encountered: