markjcrane 88eed0c35b Browser developers disabled autocomplete in most browser. A move that makes an assumption that autocomplete is always good. In this particular case it creates a bug. There are a few legitimate reasons to disable autocomplete. In this case I'm disabling it as we are only updating the password when its provided by the user. In this case the user may be and administrator changing a user a password in this case autocomplete would offer the wrong password. Another case have two password fields that must match if both passwords are empty then the passwords are not updated allowing for other user settings to be updated.		2015-09-19 17:42:02 -06:00
..
apps	Add latest translations	2015-06-30 12:30:02 +00:00
databases	Revert "Revert "Change. Use `require "resources.functions.config"` to load co…"	2015-08-11 05:06:33 +03:00
default_settings	Fix the session rotate default setting type and value.	2015-08-21 11:25:40 -06:00
domain_settings	Remove the is_numeric on format_phone.	2015-09-15 21:53:14 -06:00
events/resources/classes	Add FusionPBX events class.	2015-01-15 16:24:53 +00:00
menu	Update app_menu.php	2015-07-02 00:17:15 -06:00
notifications	Add latest translations	2015-06-30 13:30:02 +00:00
upgrade	Improve code to update the scripts directory.	2015-07-20 15:32:52 -06:00
user_settings	Add latest translations	2015-08-02 23:42:11 +00:00
users	Browser developers disabled autocomplete in most browser. A move that makes an assumption that autocomplete is always good. In this particular case it creates a bug. There are a few legitimate reasons to disable autocomplete. In this case I'm disabling it as we are only updating the password when its provided by the user. In this case the user may be and administrator changing a user a password in this case autocomplete would offer the wrong password. Another case have two password fields that must match if both passwords are empty then the passwords are not updated allowing for other user settings to be updated.	2015-09-19 17:42:02 -06:00