Go Daddy

We ran some tests with your database, imported it into a fresh WordPress and didn’t have any issues with the Dashboard. This leads us to believe there may be issues with the files.

Potentially, you could re-install WordPress and import your content and database, but we do have some other ideas for you to try that we don’t want to discuss in a public forum. If you’d like, we can give you a call to chat about this. If you’d like to do that, please let me know when a good time to call during business hours would be. We’re on Arizona time if that helps.

^Cj

haynerfide,

Have you duplicated the issue in multiple browsers? Also, have you tried to update your WordPress to the most recent version? If it were a change on our servers, I’m fairly certain we’d be hearing about multiple users experiencing the same issue. I’d be happy to see what we can do to troubleshoot it for you though.

I see you’ve disabled all plug-ins and tried reverting to the Twenty Eleven theme without success.

I’d be interested to know if it does occur across multiple browsers as it could possibly be a browser-specific or add-on/extension issue. Also, if you’re not running the most recent version of WordPress, upgrading may be an idea.

^Cj

Seacost, I apologize if this sounds argumentative, but it’s important for others reading this to know that what I stated previously *is* correct.

Windows servers respect data hierarchy differently than Linux.

For linux, the htaccess file closest to the data takes precedence. So, if there’s data and htaccess files in one folder and in a child of that folder, and parts of the htaccess file conflict with one another, the conflicting portions of the htaccess file in the subfolder overrules the one in the parent folder (in the above user’s example, the parent folder is the root).

However, with the same arrangement in Windows, the one in the parent folder overrules the one the child folder. This breaks the WordPress site in the child folder because the web.config file in the root is controlling its permalinks.

There are certainly other ways to resolve this issue, like manual modification of the web.config file, but that method isn’t for beginners, and such a modification could be destroyed by an update to the permalinks settings.

Leah,

I know exactly what’s going on here. Without spending a long time explaining the details of why, I’ll simply state that if you’re on a Windows server and using permalinks, you don’t want to put one site in the root and another in a subfolder.

This is because Windows servers handle web.config files differently than Linux servers handle .htaccess files. On Linux, having a site in the root and a different one in a subfolder would not cause this problem.

The easiest and best solution for you is to switch to a Linux hosting plan. It’s easy to do AND you’ll experience much better performance overall. If you absolutely need to have a Windows server (this is only if you’re running .NET or ASP code), you could get a second hosting plan and move the sites to it.

Here’s how you would make the switch to Linux. It just takes a few clicks and a day of patience as the migration takes place – http://x.co/mFN4

Just for the record, you COULD keep things on Windows, but you’d have to relocate the site in the root to a subfolder. First, you’d set the primary domain name on the hosting account to placeholder domain which doesn’t need to be a domain you really control (like Leah4sci-placeholder.com), and setup the site in the root as a secondary site just like you did with the other site. As long as the sites are in different subfolders that don’t fall in each other’s file hierarchy, you won’t experience this trouble.

My first troubleshooting suggestion is to switch to the default Twenty Eleven theme. You can do this quickly by accessing the /wp-content/themes/ folder and renaming each folder that isn’t the “twentyeleven” folder. You can just add an ‘x’ or the word ‘old’ after the current folder name… anything, as long as it’s different than what it is now – when WordPress can’t find the theme it’s looking for, it will revert to the default. Reload your site, and hopefully, it will run properly. If it does, you should check with your theme provider to see if there’s a new version since the recent WordPress update.

If this doesn’t fix the problem, I’d also rename the /plugins/ folder in order to disable all plugins.

Once you have your site working again, you can re-introduce the plugins one by one by making a properly named /plugins/ folder and moving each plugin into that folder until you find the one that causes a problem.

Hope this helps. Let us know if you’re able to fix things.

Alon

Christine,

In the past, I’ve seen GZip cause an issue such that the update process was not verbose, but it still completed. It sounds like you’re describing a total failure to process, though. Is that the case? Also, I assume the account is running on a Linux server, but do you know for sure?
More importantly, are you still having this problem? If so, would you be comfortable posting the site’s domain name so we can take a look at it? Would it be OK for me to have someone contact you directly to try to help?

If you’d prefer not to post anything publicly, you’re welcome to contact us on Twitter. Just follow @godaddy and send us a direct message.

Thanks,

Alon

khaksar,

The best solution is for you to switch to a Linux server rather than Windows. WordPress is built with PHP which doesn’t run as well on current Windows servers than it does on Linux. I’m fairly certain that making the switch will eliminate these problems for you.

Changing over to Linux is normally very simple… just a few clicks and a bit of a wait while the service migrates. Here’s a quick guide: http://x.co/l3y5

If you have some other application(s) running on the server that require a Windows server, you can setup a separate Linux plan and move just the WordPress site. It’s more expensive than having only one plan, but you’ll get much better performance.

Not sure if you contacted Support to get the answer, but for the sake of anyone else who sees this thread… the easiest way to do this is to setup domain name forwarding (this is what I think Ipstenu was getting at when she mentioned parking domains).

Here’s a quick guide to walk you through applying domain forwarding in your Go Daddy account: http://x.co/l3sn