Go Daddy

indrago,

I *think* I know what the problem is and how to fix it… If I’m right, activating permalinks on the indihype.com site should resolve the issue (permalinks are a setting you can activate in the WordPress admin panel).

If you’re curious, this is what I think is happening:

Your primary site is in the root of your hosting account. Visiting the primary account, we can see that permalinks are enabled. What’s important to understand is that enabling permalinks produces an .htaccess file in your account. This .htaccess file controls how URL redirection is handled for content in the same folder as the file AND any child folders unless that child folder has its own .htaccess file with a rule in it to override the rule in the first file.
Because your secondary site is in a child folder, it’s affected by the .htaccess file in the root. Once you activate permalinks, though, an .htaccess file will be created in its own folder and override the one in the root.

I don’t think you would need to bother, but if you wanted to completely avoid this issue, you would need to treat all domains on the account as secondary/alias domains and use a placeholder name for the primary name. In other words, store all sites in subfolders under the root rather than using the root for one site and storing the rest in subfolders.

9grams,

It’s very rare for a WordPress database to approach the 1GB size limit unless you’re using a plugin that stores large amounts of data in it. I’ve seen this happen with some stats plugins, but there are alternatives that don’t store the info in the database. I recommend researching WHY your database is that large and fixing the cause rather than looking for a way to store such a large DB.

For the record, there isn’t currently an option to increase the storage available for a database when using Go Daddy’s traditional hosting plans. If you’re unable to stop the database from growing beyond the allowed size, you’ll have no choice but to find another solution (like a virtual dedicated server, fully dedicated server, or virtual datacenter).

Rev. Voodoo and lehenryjr,

I just wanted to let you know that we took the feedback from this thread and worked on a solution. One of our developers got involved in this bug report – http://core.trac.wordpress.org/ticket/18525 – and produced a patch that could resolve the issue if it’s accepted into a new version of WordPress.

We don’t know if or when it would be accepted into the WordPress core, but I wanted to show you that we took the information gathered here and worked toward making a real change to benefit the community.

amcauser,

It’s very difficult to troubleshoot a 500 error because there’s no explanation of what exactly is causing the error. As esmi suggested, though, it’s always a good idea to disable any special theme and plugins you have when trying to nail down the cause of a problem.
So, assuming you’re able to access the admin for your site, I suggest switching to the default “twenty ten” or “twenty eleven” theme and disabling all your plugins. If that resolves the problem, you can then re-enable the theme and plugins one-by-one and test to see which may be causing a problem. Replacing the core files (as esmi recommended) is also a good idea.

If disabling the theme and plugins does not solve the problem, it might also be worth while to install a fresh copy of WordPress to a subfolder in the account just to make sure that a fresh install works properly. If it doesn’t, you’ll want to tell Support immediately so they can investigate further. If it does work but you can’t get your original copy working, you can export and import your content from the old one to the new. This takes some more work because your blog and plugin settings wouldn’t transfer, but it’s a last-ditch effort to make sure you get everything working.

Unfortunately, this type of problem isn’t immediately familiar to me. That said, here’s how I would attack the problem. First, backup your hosted files and the database just in case any of these steps accidentally results in loss of important data. In case you aren’t aware of it, there’s a database backup tool in GoDaddy.com’s Hosting Control Center: http://x.co/a4th

Once you have everything backed up, I would install a fresh version of WP to a subfolder and test that it works as you’d expect (easy install for GoDaddy.com: http://x.co/a4tu ) – make sure it allows adding plugins and doesn’t run into any of the other failures you’re experiencing. This test will confirm that there isn’t some unknown/unique problem with your hosting plan.

Next, just to be sure the problem isn’t caused by a faulty or incompatible theme/plugin, set your theme to the WP default (twenty ten or twenty eleven) and disable all your plugins. Test to see if that resolves the issue. If it doesn’t…

I would try downloading the current WP version from WordPress.org and uploading it to your account to overwrite your existing core files (for your primary WP instance, not the new one you just added). If there’s a problem with any of the files, overwriting would fix that.

If none of this works, I would go recommend you abandon the old install and export your data to the fresh version you installed in a subfolder. You can copy your uploads folder to the new instance and export all your content using the WordPress export/import function. You can move over the themes and plugins as well, but you may need to reconfigure their settings if there were any. Assuming it works properly, you can then clear out the old installation and go about moving the working version to the root of your hosting account. WordPress has a guide that explains how to move an install to a new folder: http://x.co/a4sr

Hope some of this helps.

Chris,

I’m sorry to hear about your experience. I wish I had come across this thread when it was originally posted – I would have made the simple recommendation to switch to one of our Linux hosting plans. As most other users on this forum would tell you, you will generally get better performance and fewer headaches with WordPress (and often PHP in general) with a Linux plan. And, as Curtiss suggested, working with permissions is also more straight forward – it does sound like all your issues were related to permissions trouble.

I’m posting here now in case anyone else should come across the thread. Please note that if you are using a GoDaddy.com Windows hosting plan and would like to switch to Linux, the migration process is fairly trivial from the customer’s point-of-view. This is a quick guide to take you through the process step-by-step: http://x.co/a05o

Should you ever decide to give Go Daddy hosting another shot, I’d love to hear about it. If you’re so inclined, I’m directly accessible on Twitter with the username @godaddy.

Rev. Voodoo,

That’s great… so we’ve confirmed that it’s not an issue caused by the Go Daddy environment. That makes me happy 🙂

As for enjoying both gzip and the update text in WordPress – technically, you can enable compression for a site while disabling it for a single file. It would take some work, though.

Here’s some guidance if you (or anyone else) want to give it a shot…

Review our tutorial for enabling mod_deflate using .htaccess: http://x.co/ZsK8

Then learn about how to disable a filter for a single file. These articles may help:
http://httpd.apache.org/docs/current/mod/mod_filter.html#filterchain
http://httpd.apache.org/docs/2.2/mod/core.html#filesmatch

Those are the correct links – they SHOULD get you to your admin login page.
If you’re not getting there, my best guess is that your WordPress installation is in a subfolder rather than in the root of your account. When installing WordPress using Go Daddy’s Hosting Connection tool, the default installation folder is /wordpress
So, if that’s how you initiated the install, and you didn’t change the default folder, you would need to visit mysite.com/wordpress/wp-admin to get to your login page.
If that’s what happened and you’d prefer to have WordPress in the root instead, you can either install a new copy to the root (you should also uninstall the first copy that you don’t want to use) or use these instructions from WordPress’ Codex to move it: http://codex.wordpress.org/Moving_WordPress