Double check that you have cookies enabled and that they are not being emptied on each page load. Usually, when your cookies get deleted you get signed out of WordPress as it heavily relies on cookies to read user permissions etc.
Thanks for your reply.
The problem is solved now. It turnes out there was a conflict between the WP_SITEURL and WP_HOME in wp-config.php and my settings in Dashboard -> Settings.
I’m a little late to the party I realise, but can you explain how you repaired the conflict between wp-config.php and your WP settings please?
This problem has just occurred for me, but it’s now impossible to do any work on the site because each time I try to make a change, including in WP settings, I’m immediately logged out.
Thanks…
In the wp-config.php file it says somewhere:
define(‘WP_HOME’,’http://example.com’);
define(‘WP_SITEURL’,’http://example.com’);
When you go to Dashboard –> Settings there’s also a field for the “WordPress address (URL)” and “Site address (URL)”.
If I remember correctly the problem was that the settings at WP-admin didn’t match the URL in the wp-config.php file or something like that. Maybe I forgot the “www” somewhere or added a “/” at the end, I don’t know anymore..
Hope this helps!
Thanks Enna. I’ve actually fixed the problem, but still not sure how or why.
I think there must have been some corruption of phpmyadmin, because some weeks ago I’d changed my WP username from the ubiquitous “admin” to something more unique. For some reason, all of a sudden, this new username started playing up by allowing me to login, but then log me out each time I tried to change pages or do an update. As a last report, I tried the old “admin” username, and it worked!
I’ll check out your suggestion though,
Cheers
i would make sure that there isn’t a outdated plugin or theme that maybe causing a issue?
most things that are outdated can actually leave back doors open.
No, I’m very diligent in keeping everything up-to-date. With the update to WP V4.0, there may have been some unexpected activity in phpmyadmin, which is where the username change was implemented.
Anyway, all good. The ‘catch-all’ admin username is working perfectly, for the time being at least.
