-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Something goes wrong setting options / saving to database #89
Comments
Hey @huubl, I’m on my phone now, but the new versions use pre_option which is faster than updating the db, so it wouldn’t reflect in the db itself. I am working on providing a sync option to update the db, should be releasing that soon. |
Hey @huubl, Just tested with a new copy from dev-master here and no problems with the above config. EDIT: just re-read your comment, and that behaviour sounds correct. Intervention does not update the DB by using application (it did in previous versions). There will be an option for this soon. Without application being set, or intervention being active, it will revert to the previous db settings. #64 for reference. |
@huubl , Interesting, I was finally able to replicate. The problem is that Intervention is setting fields in |
Really appreciate you picking this up, got a hotfix up which should solve it. Let me know if it does it for you. cf57d4a |
Related to the fix: the |
@jmerilainen ah thanks! fixed. |
Hi @darrenjacoby, I missed #64 Intervention using the pre_option now. I tried the current master branch with hotfix and it solves the problem. Thanks for looking in to this! |
Hi,
Something goes wrong when using this settings:
When I check the database values, they are not changing or (when I click save on the admin general settings page ) wrong. For example the media options get:
When saving the (partly) locked setting on the admin general settings page (by the save button ) and then comment out the application -> general settings I get this:
Am I doing something wrong?
The text was updated successfully, but these errors were encountered: