Closed cromulus closed 9 years ago
Thanks for catching/reporting the issue. The above commit should just about do it and also fix another bug where saving the general settings would reset the cron, even if the value hadn't been changed.
And if you're not feeling adventurous to try the develop branch (on mission-critical/production sites), you can download a hotfix version of master w/ above patch here: https://github.com/ExpandedFronts/Revisr/archive/issue-70.zip
Hope that helps!
Thanks! ᐧ
On Mon, Jul 6, 2015 at 1:04 PM, Matt Shaw notifications@github.com wrote:
And if you're not feeling adventurous to try the develop branch (on mission-critical/production sites), you can download a hotfix version of master w/ above patch here: https://github.com/ExpandedFronts/Revisr/archive/issue-70.zip
Hope that helps!
— Reply to this email directly or view it on GitHub https://github.com/ExpandedFronts/Revisr/issues/70#issuecomment-118926145 .
This fix has been merged in with the 2.0 release.
Which causes merge conflicts regularly. Perhaps that setting should live in the git config and not stored in the DB?