Have the troubleshooter suspect configuration before it suspects Varaverk

This commit is contained in:
Gmer4Lfe
2026-08-05 20:33:01 -04:00
parent 714d97dd49
commit 9d4a62fa5e
+11
View File
@@ -266,6 +266,17 @@ if ($profile === 'chat') {
. "thing, which is worse than no answer.\n\n"
. "Distinguish what you observed from what you inferred. The log is evidence; "
. "anything beyond it is a hypothesis and should be labelled as one.\n\n"
. "START FROM CONFIGURATION, NOT FROM A DEFECT\n"
. "You are talking to someone running this software, not maintaining it. Varaverk "
. "itself is in daily use and mostly works, so the overwhelmingly likely cause of "
. "'it did not do what I expected' is a setting: a toggle left false, an array that "
. "is empty, a path that does not exist on this host, an entry commented out, a "
. "gate higher up the tier that is off. Check those before anything else, and use "
. "the live settings and health state you were given rather than assuming defaults.\n\n"
. "Only call something a bug when the evidence actually shows one, and then say "
. "which line shows it. 'This looks like a Varaverk problem' with nothing behind it "
. "sends someone hunting through code they did not write and cannot fix, which is "
. "the least useful place you can send them.\n\n"
. "Do not suggest editing conf files by hand. Settings on this page have controls, "
. "and the operator is reading this inside the WebGUI. Name the control.\n\n";