Makes the nag message not activate if comms are not enabled

This nag message should only come up when something has gone horribly
wrong.
This commit is contained in:
VistaPOWA
2014-04-13 19:18:16 +02:00
parent 19d46a7084
commit 2459f5c17f
+1 -1
View File
@@ -130,7 +130,7 @@ var/next_external_rsc = 0
if(holder)
add_admin_verbs()
admin_memo_show()
if(config.comms_key == "default_pwd" || length(config.comms_key) <= 6) //It's the default value or less than 6 characters long, warn badmins
if(config.comms_key == "default_pwd" || length(config.comms_key) <= 6 && !config.comms_enabled) //It's the default value or less than 6 characters long, but it somehow didn't disable comms.
src << "<span class='danger'>The server's API key is either too short or is the default value! Consider changing it immediately!</span>"
log_client_to_db()