Module: check_mk
Branch: master
Commit: f0c333a1ff2d0410d5b5ec13ec2026aacbb57cab
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=f0c333a1ff2d04…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Mon Mar 4 12:24:11 2013 +0100
Updated bug entries #0789
---
.bugs/789 | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/.bugs/789 b/.bugs/789
index 46d43fe..c330767 100644
--- a/.bugs/789
+++ b/.bugs/789
@@ -1,9 +1,9 @@
Title: Settings in multisite.mk without default values persist in browser cache
Component: multisite
-State: open
+Class: bug
+State: wontfix
Date: 2012-09-13 17:42:33
Targetversion: 1.2.3
-Class: bug
If you write an extension (like mkeventd) that wants to put a settings
into multisite.mk then it cannot put a default value into config.py (it
@@ -11,3 +11,6 @@ must not modify files of the main distribution). If it once sets a value
in
multisite.mk and that is later removed (factory settings) then the positive
settings survives in the browser cache. We need to find a method how extension
modules can define or declare default values for settings in multisite.mk
+
+2013-03-04 12:24:04: changed state open -> wontfix
+Wont fix this in 1.2.2.