CMD_LOGIN_KEYS to Reseller/User Packages (SKINS) ** Manditory Skin Changes **

Version 1.41


Option CMD_LOGIN_KEYS in the skins. During the DA update, the will automatically run: echo "action=addoptions" >> /usr/local/directadmin/data/task.queue This task will go through all user.conf, reseller.conf and package files. If the directadmin.conf has login_keys=1, then all of the above files will receive: login_keys=ON else, if login_keys=0 is in the directadmin.conf, then all files will receive: login_keys=OFF Note that the internal default in DA is: login_keys=1 even if no value for login_keys is present in the directadmin.conf ---------------------- Failure to use update skins will result in login_keys being turned off in a package or user.conf/reseller.conf file. This would disable login_keys for that User. SKINS: admin/create_customized_reseller.html admin/show_reseller_package.html admin/modify_reseller.html reseller/create_custom_user.html reseller/show_user_package.html reseller/modify_user.html user/show_domain.html All files essentially have this 1 line addition after System Info: <tr><td class=list>Login Keys</td><td class=list align=center><input type=checkbox name=login_keys value="ON" |LOGINKEYSCHECKED|></td><td class=list></td></tr> user/show_domain.html will have something like: |*if LOGIN_KEYS_ENABLED="0"| |?USERLOGINKEYS=OFF| |*endif| |*if USERLOGINKEYS="ON"| <a href="/CMD_LOGIN_KEYS">Login Keys</a> |*endif|

Interested to try DirectAdmin? Get a 30-day Free Trial!