Module: check_mk
Branch: master
Commit: 5f50dbe2775506425f3a0e565d47801b0e1741d4
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=5f50dbe2775506…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Thu Sep 13 17:46:04 2012 +0200
Updated bug entries #0789
---
.bugs/789 | 15 +++++++++++++++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/.bugs/789 b/.bugs/789
new file mode 100644
index 0000000..1576c10
--- /dev/null
+++ b/.bugs/789
@@ -0,0 +1,15 @@
+Title: Settings in multisite.mk without default values persist in browser cache
+Component: multisite
+State: open
+Date: 2012-09-13 17:42:33
+Targetversion: future
+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 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