Answered Unable to Create or Change User Details

Hi, I'm on 1.0.14 but can't create a new user (admin, publisher or editor), the system just sits and does nothing, no error message. I can't even reset or unblock a current user. What could be wrong please?

it is possible that your site has been hacked?
in some hacked 1.0.14 websites I noticed changes to the core files of user management

you could backup and upgrade to 1.0.15 and look if it still happens.
and check if your site is hacked

It doesn't 'look' hacked but I'll upgrade and see what happens, cheers for the suggestions

Upgraded, no change :-(

Its a behaviour I have never had before. Doubt it will work but you could repair tables with phpmyadmin.
I have no other clues

Cheers. I'm thinking it may be a database corruption. I deleted the site and installed from scratch. I was then able to create a new user. When I imported the data it all turned to custard again. I couldn't reset the password or make changes but I could delete the user. I think I'm going to have to rebuild it manually.

So I exported the site content from the database then installed a new site then created the new user then imported the site content. The site works but I still can't edit any user details (after the import).

This may or may not be relevant.

Have you checked the permissions for the Admin user account ?

In Evo you can't modify the account settings for the main Admin / super user account. But it can be modified via phpMyAdmin.

A suggestion:

Using phpMyAdmin look at the DB table "?_user_roles" where "?" is your table prefix.

You will see all of the user accounts and you should have something like "edit / copy / delete" and a load of table headers.

For the main admin account, all of the elements should have a "1" in them - if that's not the case and there is a "0", click edit, find the culprit and change it from "0" to "1" - save and log back into the manager, clear Evo cache and try modifying the user again.

If it works great, if not, go back to the DB and check again - if the settings have been changed again to "0" the site probably has hacked code somewhere.

Background:

One of my sites was hacked some time back and after upgrading, deleting all suspicious code and removing all modified files, the site was hacked again within 12 hours.

The hacker had injected code in the DB and modified the Admin user account - each time I modified the user the malicious code changed the settings again.

I couldn't find the code that kept doing the changes so my end-solution was a complete re-build which ensured that no dodgy code or files were still there. [ed. note: iusemodx last edited this post 11 years, 7 months ago.]

Quote from: iusemodx at Feb 17, 2015, 07:17 AM

This may or may not be relevant.

Have you checked the permissions for the Admin user account ?

In Evo you can't modify the account settings for the main Admin / super user account. But it can be modified via phpMyAdmin.

A suggestion:

Using phpMyAdmin look at the DB table "?_user_roles" where "?" is your table prefix.

You will see all of the user accounts and you should have something like "edit / copy / delete" and a load of table headers.

For the main admin account, all of the elements should have a "1" in them - if that's not the case and there is a "0", click edit, find the culprit and change it from "0" to "1" - save and log back into the manager, clear Evo cache and try modifying the user again.

If it works great, if not, go back to the DB and check again - if the settings have been changed again to "0" the site probably has hacked code somewhere.

Background:

One of my sites was hacked some time back and after upgrading, deleting all suspicious code and removing all modified files, the site was hacked again within 12 hours.

The hacker had injected code in the DB and modified the Admin user account - each time I modified the user the malicious code changed the settings again.

I couldn't find the code that kept doing the changes so my end-solution was a complete re-build which ensured that no dodgy code or files were still there.

That sounds horribly familiar :-(

I'll check it tonight, cheers