Bug #5274
closed
services_dyndns_edit.php existing password is not loaded/saved when editing
100%
Description
Try to edit an existing Dynamic DNS entry.
In 2.2.* you can edit, change the description or other inconsequential filed and save. The current password is known and kept (without being displayed, of course).
In 2.3-ALPHA the password field comes up blank in the editor. If you change some other field (e.g. description) and press Save then you get a validation message to say password is required.
That is annoying - you have to find the password from somewhere and enter it. It is much easier if it is loaded in the background somewhere and re-saved... like in 2.2.*
Updated by Anonymous over 8 years ago
- Status changed from New to Feedback
- Assignee set to Phillip Davis
Element names corrected for password and description.
Page now displays those values on load.
Updated by Anonymous over 8 years ago
- % Done changed from 0 to 100
Applied in changeset pfsense:b19ff0d2dfc39f32ecb6b7d5f4836cd22a3c4ea0.
Updated by 
Updated by
Updated by Steve Russell 3 months ago
Not sure if this should be a separate bug now, or when this came back, but this issue is present in 2.60 and 2.72.
Updated by Jim Pingle 3 months ago
Steve Russell wrote in #note-5:
Not sure if this should be a separate bug now, or when this came back, but this issue is present in 2.60 and 2.72.
I can't replicate any problem like that on a current version, it's probably something local or in your browser. This site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum .
See Reporting Issues with pfSense Software for more information.
Updated by Steve Russell 3 months ago
Ugh, yes, you are correct Jim, thanks! Password manager was autofilling the password field with who knows what.
Sorry for the noise.
Updated by Jim Pingle 3 months ago
Steve Russell wrote in #note-7:
Ugh, yes, you are correct Jim, thanks! Password manager was autofilling the password field with who knows what.
Sorry for the noise.
No worries, there is a reason we cheekily refer to them as Password Manglers.