ElkArte Community Modern, Free, Powerful
Community building forum software

Hello there Elkartians! Wasn't too sure if I should be opening a topic for every problem related issue but my guess is that it may help future users and webmasters in solving the same issue if encountered

The issue is when trying to change General account settings, first selection when hovering or clicking on the profile name.

While trying to edit account settings I am presented with a message that these options contain sensitive information and that I will be required to enter my current password, the issue is that even after entering my current password into one of the suggested password fields I guess those were for changing the account password EG: ''Choose a password'' and ''Confirm password" nothing happens, not even a new popup showing a field where the password might need to be entered ?

How would I go on about resolving this issue ? Could this be a theme related issue ?

Thanks in advance!

There should be a field at the very bottom of that form that says Current Password ... you need to fill that out as a security measure.  Those other two password fields are in the when you want to change your password (and you would still need to enter your current one in that current password field.

Its really intended for the event where you don't logout to prevent someone from pranking you.  Normally not a issue when its your computer, but if using a public access point and you forget to logout it could be a problem.

Thanks for the reply Spuds !

But could this be a theme issue ?

Check this out this is a preview of the Account Management page

Update

Tried changing the theme back to Elkarte Default and it seems to be a problem with the ''Clean'' Theme, guess I will have to test out each theme fully before enabling it forum wide 

Looks like you found your answer ...

Themes are notorious for not "keeping up" with the core, although the issue you have shown in your screen shot seems really odd.   Normally a custom  theme does not support a new feature, but in this case the current password field has been around for a decade or more!  I'll try to take a look at that and see if there is a simple fix I can provide.