Theme keeps breaking

It looks like you might need to review the steps in the Extended Upgrade Procedure to make sure you didn’t skip any of the steps.

For example, did you run the WordPress upgrade program after doing the initial upload of files in order to upgrade the database? I’m not sure if it would be done if you reinstall. That might be it.

linux4me2, perhaps that is it.

I clicked through the link you posted and reinstalled following those instructions religiously.

At the moment, I’m waiting to see if the problem occurs again; I’ll be sure to post if it does. Thanks.

It just happened again. And when I login to the dashboard, I again see:
“ERROR: The themes directory is either empty or doesn’t exist. Please check your installation.”

Did you make a backup at each upgrade step? Did you check the site thoroughly after each upgrade step?

I made backups at the beginning, and I asked the server owner to back up the databases.

What should I have checked after each step? The site started displaying a php error when I started deleting files, and stopped when I was finished uploading all the new files. I checked to make sure the upload/download/delete occurred correctly if that’s what you mean. I’m not being sarcastic; I don’t know what you mean.

This should not be marked as resolved. That was a mistake. Can a mod “un-resolve” this thread?

“ERROR: The themes directory is either empty or doesn’t exist. Please check your installation.”

This message, along with the theme resetting itself to default from time to time, leads me to suspect that your problem is somewhat deeper than WordPress.

If a drive is failing or if the drive is on the network and the network temporarily becomes inaccessible, then this can lead to directories “disappearing” for a short time on a unix-based machine.

If you happen to access WordPress at that time, and the wp-content directory or themes directory or theme directory is not there, then WordPress will switch to default. It has no choice, really, the theme it’s trying to find isn’t there.

So I’d ask your host to look closely at the drives in that machine, or check the network connections, or something else. This is indicative of a failing filesystem.

And make *darned* sure you get a total and complete backup of that site, immediately. If the drive fails and there’s no backups… yikes.

Samuel Wood, I’ve forwarded your post to the server owner and asked him to verify normal function on his end.

Also, I’m pinging the host every second from now until after it resets again, then I’ll check the results for anything unusual.

If a drive is failing or if the drive is on the network and the network temporarily becomes inaccessible, then this can lead to directories “disappearing” for a short time on a unix-based machine.

How long would the drive have to be offline for? I pinged the host every second and then every half a second and waited for the error to occur again – no packets were lost and the longest one took < 400ms to come back. Then again, I don’t know if pinging is useful here. From what I understand, all these files would be on the same drive/machine, right? So for the themes folder to become inaccessible for a short while because the drive is blinking out, it should become inaccessible to me for a short period, right? Or am I an idiot?

How long would the drive have to be offline for?

At a guess, less than 1 second.

From what I understand, all these files would be on the same drive/machine, right?

That would be my understanding, yes.

Or am I an idiot?

Well, it all sounds quite logical and correct to me. Are you running this server locally?

Are you running this server locally?

No, the hosting is provided by a member of the club – the site existed for years before I came along. I don’t know if he owns his own server, whether it’s real or virtual, or if he just has a paid hosting plan somewhere. I still haven’t received a response from him.

Well, it all sounds quite logical and correct to me.

Ok, but I pinged the server every half second until after the site broke again. None of the pings failed to come back, and none of them took longer than 400 ms. Should I try pinging more quickly if it may only be blinking out for less than a second?

I think you need to speak to whoever is hosting the site – either your club member or (even better) the actual hosting company. It’s really not up to you to diagnose server issues and you don’t really have access to the right tools to do it properly.

In terms of evidence for a server problem, check your site’s error logs (assuming you have access to them). They may provide the evidence that you need to create a ticket with the hosts.

check your site’s error logs (assuming you have access to them)

I have FTP access to the subdomain. Would I be able to find them that way? I don’t know much about this kind of stuff.

Pinging the site won’t help, so you might as well stop doing it.

Bottom line is that you don’t have the kind of access to the server that you need to diagnose the issue. You need root access, to examine the logs. You need physical access, to examine the drives.

You need to tell the host, basically. And if they don’t fix it, then you need to switch to a new host.