Admin hangs on login but subscriber has no issues…

Have you tried:

– deactivating all plugins to see if this resolves the problem? If this works, re-activate the plugins one by one until you find the problematic plugin(s).

– switching to the default theme to rule out any theme-specific problems?

– resetting the plugins folder by FTP or phpMyAdmin? Sometimes, an apparently inactive plugin can still cause problems.

– re-uploading the wp-admin and wp-includes folders from a fresh download of WordPress?

– increasing the available memory?

I did consider renaming the plugins folder (thus automatically deactivating all plugins) almost instantly but was worried that I’d have to re-set all the options for them which could set me back even longer (I’m only able to get online a couple hours a day – long story! – so hoped to find a quicker solution from someone who’s experienced this issue before. Also all other issues I’ve had with this particular project, if I’ve been unable to resolve them myself, have normally resolved themselves by the next day, but since this issue is still hanging around I’m just about to try the plugins one. The theme and wp-admin options for the same reason, but will do if the plugins idea fails. I’ve already had the server-side memory increased to allow use of another web app so that’s not the issue…

Thanks for the input though esmi, I appreciate you taking the time to reply.

Unfortunately this hasn’t helped. I was finally able to login but only because I’d tried to load the homepage in another tab while the first one was attempting to login. With the plugins folder renamed (regardless of there being an empty one in its place) I’m unable to access any of the back-end pages, and with the plugins folder restored attempting to access them brings back the painfully slow progress bar until it eventually times out. Also tried the SQL database hack but constantly receive a 404 error when trying to reach the back-end pages…

It’s sounding more and more like a plugin conflict but all active ones have been in use for days or even weeks with no issues (I normally track down a replacement for any plugin that experience issues with). I’m fast being reminded of why I’d avoided using wordpress for so many years, it’s by far the most unstable development platform I’ve ever encountered! Unfortunately tho I’ve invested too much into this to just give up so I’ll keep trying and if anyone has any more ideas please fire them this way…

With the plugins folder renamed (regardless of there being an empty one in its place) I’m unable to access any of the back-end pages

Wait, so when you remove the plugins folder (rename) the problem still exists?

What plugins?

Too many to name in the couple mins I have left online (working in 20 mins). But yeah, I even tried moving the plugins to a backup folder, but this also causes me to be unable to access the back-end. Uncertain if it’s the exact same issue that I had originally, but it’s definitely an issue in itself…

Also, it would seem the active plugins stay active once the plugins folder is restored (normally wp keeps them deactivated until they’re manually reactivated…)…

That only happens if you visit the back end and they’re automagically disabled but … Yeah, something’s really hinky there.

– re-uploading the wp-admin and wp-includes folders from a fresh download of WordPress?

Def try that.

Hey. Im pretty confident I can help you resolve this issue.

IMO it’s a header issue. I had the same problem months ago.

Firstly, check your functions.php for spaces at the begining and the end of the file. Any white noise could be causing this error. IF you find any, delete it.

But if this dosn’t work, try inserting;

ob_start();

into the top of the functions.php file.

Hope that works.

The only one of esmi’s suggestions I didn’t try was the memory upgrade, and that’s because it was one of the first things I asked my host to do when I first bought my domain…

Thanks razor.harrison, but it doesn’t seem to be the same issue, or at least it requires a different solution as there was only a single blank line at the end of the file and removing it didn’t make any difference. Also the ob_start(); line seemed to cause a bunch of errors when added to the top (assuming you meant above the “<php?”) and made no difference when entered anywhere else…

I managed to find a trick to log in, after the login process starts open the homepage in a new tab (but in the same browser) and it will eventually load with my front-end version of the admin menu, unfortunately trying to access any of the back-end pages is still impossible as it’s the same scenario as logging in.

I’ve resigned to having to start the whole thing from scratch, and in future I’ll be keeping a safe distance from wordpress (no offence to others but this is the second time I’ve relied on it and it’s let me down in a big, and expensive, way!)…

Thanks again though to those who tried to help, if I do find a solution I’ll post it for others’ reference…

This really sounds like a bad plugin combination, which without knowing what you’re running, makes it guesswork.

Sorry you’re having such a bad time of it.

@ The Living Legend,

One of the points is that if you are to put – ob_start(); AFTER the <?php = so it would be the second line, then you SHOULD get a heap of errors. Once you have identified what those errors are, you should be able to fix the problem. Or at least post them here and we can have a look at it.

As for wordpress letting you down, I find you comment interesting. I’ve worked with heaps of different solutions and honestly I doubt you’d find a better, more powerful solution in the OS community. And I’ve worked with HEAPS.