wrong input field

[tajriba]

when using chrome/firefox the api key is stored in a password field type input. this is not good, because when editing the module configuration the key is always gone... because it's not a saved password:

solution: No password field

[venditdevs]

You are incorrect.
Yes it's empty when you open the configuration screen again but it's still saved in the database. and when you save the configuration again the data in the database doesn't get overwritten by the empty one if you look at the code of the module.

if (!empty(Tools::getValue('PAYNL_API_TOKEN'))) { Configuration::updateValue('PAYNL_API_TOKEN', Tools::getValue('PAYNL_API_TOKEN')); }

[tajriba]

In the real world it's working not good in Firefox for example.
The field is empty and after saving the configuration failed and empty field is saved.

[annevelden]

Thank you for your comment @tajriba however @venditdevs is correct that we have made modifications so an empty field doesn't get saved to the database.
We would still like to see if we can help you in more detail. If you send an email to [email protected] with these details, our integration manager can possibly help resolve this.

[woutse]

Thanks again for your message. Though it should work properly, also in Firefox, we can see how a password field might not the best solution for not showing the API Token. Next release will contain an update for this.