Jump to content

new super user password not saved

Recommended Posts


On a 2.5 install I try to add a second super user. After adding and saving it with password assigned, It gets displayed with a strike through in the user list. When I then edit and save it again, I get this error:

Missing required value

Required password was not specified.

But the password was entered already when I added the user.

This is happening only on a clone of an install on my dev server. When I add the same user on my local environment, everything is working as expected. The install on the dev server is the same where I get the persistent httpHost error described in my other thread.

Also the httpHost error message gets displayed twice, above the user list and on the very top:


I have other PW installs on that server which are all running smoothly.

Any pointers to a solution would be great. Thank you.

Share this post

Link to post
Share on other sites

If you have moved to a different server, have you ensured that all your path statements reflect the move (different physical location of files) on this install?

  • Like 1

Share this post

Link to post
Share on other sites

Thanks for the hint. But again, which path statements? Never had issues before when moving sites.

Share this post

Link to post
Share on other sites

If you are talking about include paths in my templates, they are all correct.

Share this post

Link to post
Share on other sites

Whatever the domain name of that cloned PW install is, that is what the config.php is looking for (the error that is displaying).  Or to put it another way,  If you clone an install, you need to supply a different domain name in the config.php file.

Share this post

Link to post
Share on other sites

After moving the site to the new host I have specified the new domain in the config file. But it is not recognized by PW. What ever I assign to $config->http hosts array, I always get that error.

Share this post

Link to post
Share on other sites

The problem happened to be related to old session files that I transferred when moving to the new server.

Once I deleted all session files in assets/sessions on the new server, PW picks up the $config->httpHosts array. The error message in the backend disappears and I can create users and save their passwords without problems.

  • Like 2

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Lewis Newson
      Hi All,
      Im working on streamlining my email sending setup for SMTP. I have a page where the user of the website can input the SMTP host, port, connection type email and password etc but the password field has an additional box underneath it for 'Confirming' it as if it were a new password. The placeholder text also says 'New Password' but I want to be able to change that. I just need an input field where they can enter their SMTP password without it being plain text.
      Thanks for your help!
    • By Tyssen
      I have a client who is reporting that in the last couple of days they can no longer login to their site with their normal browser (Chrome). Using another browser or an incognito window works.
      I've tried logging into the site using the same login details in my usual browser (Firefox) and have had no problems.
      The site is a membership site and today other members are reporting the same problem.
      The site is running 3.0.148 and has the session handler DB and login throttle modules installed. It was recently upgraded to 3.x from 2.x. But no changes have been made to the site between the time when they were able to login OK and when the problem started happening.
    • By anttila
      We are developing an App that sends data over the Internet to ProcessWire (POST/JSON). We want password to be protected somehow when sending it, but I should be able to compare it to PW's passwords. We were thinking of using md5 encryption, but PW uses different encryption.
      How can I be sure that user has active account when they use the App?
    • By Robin S
      Password Generator
      Adds a password generator to InputfieldPassword.

      Install the Password Generator module.
      Now any InputfieldPassword has a password generation feature. The settings for the generator are taken automatically from the settings* of the password field.
      *Settings not supported by the generator:
      Complexify: but generated passwords should still satisfy complexify settings in the recommended range. Banned words: but the generated passwords are random strings so actual words are unlikely to occur.  
    • By AndZyk
      can somebody tell me, if it is possible to get the clear password of an InputfieldPassword inside a module, before it is encrypted?
      I have made a custom module which sets the password of an Auth0User after the hook publishReady with a random generated password. When I try to get a clear password from a InputfieldPassword in this hook, it is of course already encrypted (which is of course good). But is there a hook before the encryption, so I could get it one time to send it to Auth0?
      If there is not such thing, could be another possibility to add a jQuery script to get the value directly from the DOM and save it somewhere temporarily?
      I know this might be an unusual question, but I would appreciate any feedback. 
      Regards, Andreas
  • Create New...