Two thirds of the conf was unreachable from the UI, and an empty Config block said nothing about why
This commit is contained in:
@@ -4358,6 +4358,15 @@ function vvShowScriptInfoMode(name, hdr, id) {
|
||||
vvConfId = id;
|
||||
document.getElementById('vv-cancel-edit-btn').style.display = '';
|
||||
document.getElementById('vv-save-conf-btn').style.display = '';
|
||||
} else {
|
||||
// Say so rather than showing nothing. An absent Config block is ambiguous — it reads the
|
||||
// same whether the script genuinely has no settings or nobody ever mapped it, and that
|
||||
// ambiguity hid 15 scripts' settings until the conf was audited against the map.
|
||||
html += '<div class="vv-sinfo-block">'
|
||||
+ '<div class="vv-sinfo-lbl">Config</div>'
|
||||
+ '<p class="vv-cf-none">No user adjustable settings — this script is driven by its '
|
||||
+ 'own logic and the values it inherits.</p>'
|
||||
+ '</div>';
|
||||
}
|
||||
|
||||
si.innerHTML = html || '<p class="vv-cf-empty">No additional information found.</p>';
|
||||
|
||||
Reference in New Issue
Block a user