Thanks for the extra information @mc2
I can now see that clicking OK to save a change to the form field configuration using the latest KPRPC version causes a problem.
I don’t have any idea why it happens or how to fix it yet but in the mean time, please can you try following the instructions below on an affected entry to confirm that this then causes Kee to behave as expected?
To repair any affected entries, you can edit the “KPRPC JSON” advanced string - replace the “FFTradio” “type” with “FFTusername”, for the JSON object containing the “value” of “{USERNAME}”.
Make sure this is the only thing you change while the Entry Edit window is opened, since this will simplify rolling back to an earlier version of the entry if anything goes wrong.
For example, if your JSON is like this:
{"version":1,"hTTPRealm":"","formFieldList":[{"name":"password","displayName":"KeePass password","value":"{PASSWORD}","type":"FFTpassword","id":"password","page":-1,"placeholderHandling":"Default"},{"name":"username","displayName":"KeePass username","value":"{USERNAME}","type":"FFTradio","id":"username","page":-1,"placeholderHandling":"Default"}],"alwaysAutoFill":false,"neverAutoFill":false,"alwaysAutoSubmit":false,"neverAutoSubmit":false,"priority":0,"altURLs":[],"hide":false,"blockHostnameOnlyMatch":false,"blockDomainOnlyMatch":false}
Change it to this:
{"version":1,"hTTPRealm":"","formFieldList":[{"name":"password","displayName":"KeePass password","value":"{PASSWORD}","type":"FFTpassword","id":"password","page":-1,"placeholderHandling":"Default"},{"name":"username","displayName":"KeePass username","value":"{USERNAME}","type":"FFTusername","id":"username","page":-1,"placeholderHandling":"Default"}],"alwaysAutoFill":false,"neverAutoFill":false,"alwaysAutoSubmit":false,"neverAutoSubmit":false,"priority":0,"altURLs":[],"hide":false,"blockHostnameOnlyMatch":false,"blockDomainOnlyMatch":false}
@RRRainick I think you can apply a similar fix after modifying the placeholder setting for an entry.
As well as understanding how to prevent the “type” being changed unexpectedly, we will probably also need an additional fix to handle any entries that have become corrupted in this fashion (especially useful for anyone that doesn’t know they have hit this bug). That might be do-able as a one-off data migration task or perhaps have to be rolled into the larger project of our review of form field configuration in this issue: New Entry configuration format · Issue #101 · kee-org/keepassrpc · GitHub
