setup a new install of 3.2.3 and when trying to add new admins I get the error below. The system adds the new person but will not send a password notification; therefore new Admin’s cannot login (no password)… Any help would be appreciated
And you can send emails (campaigns, test email via campaign?) without problems?
Have you got the new admin’s email entered in their subscriber profile?
Yes, i have been able to send campaigns from the start… No problems… Using the default admin account!
The only problem I have is adding new Admins. It takes all of the information but will not allow a password because no token can be sent to set one up. It saves all of their info but you cannot login with their account because there is no password
Just looked at one of my installs and added a new administrator.
YOU cannot set a password for the new admin, an email is sent to their email address and they then click on a link in that email to set their own password. Just make sure you set the password (hidden) Update it to yes.
No it does not… I am aware of what you said. I set up several new admins with an email I own and have the program send to me. Unfortunately the program is no longer sending the password token. As I said before I can send you privately the admin password and site info and allow you to look at the install to view what happens when you try to add a new admin. I am at a lose as to the problem.
I have reset 323 with a new clean database and cannot even send a test message, preferences, or any thing else. The same thing is true of trying to setup new admins (cannot set them up). I don’t want to upgrade from 321 before I get this corrected.
My config.file is working in 321 and things are good on the production site.
After installing 321 on the test site. I used the config file from the production site (with website specific changes) and nothing worked. It was just like the 323 setup;
The Admin password token would not sent, could not send a test message, could not send a campaign.
After talking to my web service personnel they checked and the smtp info used on both the production site and the test site was incorrect even though it was working on the production site. (Duncan, if you remember me talking to you about a slowdown while entering info on campaigns, that was a symptom of the problem). There were two lines of php code that were not on the test site in the php ini file…
After changing the smtp info on both the production and the test site all is working well. Actually the slow down on the production site while entering campaign info is now gone.