Something goes wrong setting options / saving to database about intervention HOT 7 CLOSED

@jmerilainen ah thanks! fixed.

from intervention.

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!

from intervention.

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.

from intervention.

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.

from intervention.

@huubl ,

Interesting, I was finally able to replicate. The problem is that Intervention is setting fields in application as disabled on the option pages, and so when you save settings from WP, the disabled field values aren't pulling through on save and instead clearing the DB entries. Not ideal. I think changing from disabled to readonly will solve the issue, but still testing.

from intervention.

Really appreciate you picking this up, got a hotfix up which should solve it. Let me know if it does it for you. cf57d4a

from intervention.

Related to the fix: the Sober\Intervention\UserInterface\Tools\Import class is missing from the repo.

from intervention.