• I’ve got a few sites, though some are on WPMU, some are not. The one in question, and the reason I spent 2 hours on the phone with GoDaddy support, is commentary.bensonreport.com.

    The site wouldn’t load at all, just a blank white screen. On the rare occasion that it would load, it would take f-o-r-e-v-e-r to load. So GoDaddy said the only thing they could find was that if I renamed the .htaccess file to .htaccessold (which basically disables it) that it would solve the problem. However, that file is in the root, which is not the bensonreport site. My root is sparklogix, the site I have installed with WPMU. By disabling the .htaccess file, it prevents my permalinks from working on my other sites.

    There has to be a better solution than this. Of course, GoDaddy won’t help with that because it’s a third-party thing or whatever. They assume it’s something in the .htaccess file that’s preventing the commentary site from loading. However, I didn’t have this problem until I switched to Linux hosting this weekend. I also switched to a dedicated IP, although I’m still on shared hosting.

    If it will help, here is the .htaccess file, if you can see anything that needs to be fixed in there:

    addhandler x-httpd-php5-cgi .php5
    addhandler x-httpd-php5-cgi .php
    addhandler x-httpd-php-cgi .php4

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    Thanks!

Viewing 15 replies - 1 through 15 (of 18 total)
  • It could be that the particular box (server) that your account is on, has alot of traffic and/or has too many users, it could be that you’ve got more installed to your account then your allocation of resources can cope with..

    Exactly how many installs do you have running under this one shared account?

    Thread Starter sparklogix

    (@mybenson)

    Well, I’ve got 3 accounts under my dedicated IP. 1 of those accounts is WPMU. The reason the other 2 are separate is because I didn’t know about MU before I set them up.

    They all work fine (as far as speed goes) once I disabled that htaccess file. It’s just that the permalinks don’t work anymore.

    What permalink structure are you using when permalinks are enabled?

    Custom or one of available the choices?

    Thread Starter sparklogix

    (@mybenson)

    One of the available choices. The site where permalinks aren’t working now is here.

    Well the htaccess rules if they exist on that site are not being applied..

    thesite-address-you-posted.com/?page_id=about

    Works with your permalinks enabled, which means either the htaccess doesn’t exist, hasn’t been updated correctly, or the mod_rewrite rules aren’t applying as they’re suppose to..

    You might need to enable symbolic links (this may not help at all)..

    Options +FollowSymLinks

    .. which would go at the top of your htaccess file.. i have to use this on my website (for some people it makes no difference though).

    There’s no harm in adding that, either it’ll help or do nothing..

    Thread Starter sparklogix

    (@mybenson)

    The problem isn’t the permalinks on the sparklogix site. They work fine when the htaccess file is enabled. The problem is that I’ve had to disable it to make the commentary.bensonreport site load. It’s the only way I can get it to load. So I’m wondering what’s wrong with the file that’s causing the commentary site to not load.

    I don’t currently have permalinks enabled on the bensonreport site.

    So is the WPMU site also in the root, and the problem site sits in a sub-directory of root? Would that be correct?

    Thread Starter sparklogix

    (@mybenson)

    I know, this is pretty confusing. The root is SparkLogix. I have multiple domains under my hosting account (root), BensonReport being one of them. WMPU is installed in the root. BensonReport has it’s own .org install, and Commentary.BensonReport has it’s own .org install.

    So to answer your question, yes ??

    Do both the non-MU installs suffer problems when permalinks are active for the WPMU install or just this one?

    I ask because i’m under the impression the issue is that the WPMU rules are cascading down into the sub-directories of your .org installs and messing with their own specific rules.. (that would be my guess at this point)..

    Thread Starter sparklogix

    (@mybenson)

    Only the subdomain site is having problems. Both non-MU installs have permalinks disabled, but only the subdomain site (commentary) is having the load issues.

    I have reactivated the htaccess file, to test it again, and the MU site is working perfectly, while the commentary site is not. The other non-MU install is also working fine.

    Do you have these problems when you don’t use the sub-domain?..

    Using the regular URL (the sub-domains real path)?..

    Thread Starter sparklogix

    (@mybenson)

    You mean using the root.com/subdomain?

    Well, sorta. Sometimes, it loads super slow, sometimes, not at all. It’s very hit and miss, whereas the other sites load perfectly, all the time.

    Yes that’s right..

    I imagine that blog is also configured to use the sub-domain to, would it be possible try having that blog operate under that path …

    I don’t mean load one page via the browser, because the blog istself will still be making it’s requests to sub-domain paths..

    Although you may be requesting..
    domain/subdomain/page1
    ..in your browser, your blog will still be making it’s requests using the URL configured in the backend, ie. subdomain.domain ..

    So you’ll not notice much if any difference by simply changing the URL in your browsers address bar.. (you’d need to reconfigure the URL in the backend – wordpress url, blog url)..

    I’m sure i remember reading of some sub-domains issues under WordPress, so i’m simply curious to see if using the real path will have any impact..

    The suggestion above isn’t a simple one, so don’t do it if you prefer not to screw with these settings, and it may make no difference (it might do to – i don’t know)

    I’m off to bed very soon, so i’ll not be here to reply soon, so don’t try what i said above unless you’re confident in what you’re doing and know how to fix it if you accidently mess something up.. as i’ll not be around again for several hours .. (i’m sure you know what you’re doing, just letting you know i’m off shortly)..

    Thread Starter sparklogix

    (@mybenson)

    I truly appreciate your help to this point! Thanks you ??

    I really can’t have these sites connected, I don’t want people having to type in the root/subdomain to get to the site.

    I’m not 100% positive what you’re suggesting, so I would rather not attempt anything right now, but I will need to get this fixed as soon as I can. Of course this problem happened after my husband sent out an email to tons of people letting them know the site was up. Irony is fantastic.

    If you (or anyone else) can think of something I can do that would not link the 2 sites, I would really appreciate it.

    And as I said, I really want to thank you for your time and knowledge. These forums are fantastic and I would be lost without them!

    Ok well how about this then..

    Create a new install, barebones, no content other then what is placed there by the installer (Hello world post etc..), set it up in a sub-directory, and test …

    Once you’ve done that, setup a sub-domain, and point the sub-domain at the new install, then update this new test install URLs (wordpress url, blog url) to use the sub-domain, and test …

    That way you don’t have to touch your existing install .. just create a new one to test with. All you’d be doing is seeing if there was a performace difference between using and not using the sub-domain on the new install..

    It was just a theory anyhow..

    I’ll check back on you after some zz’s .. ??

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘GoDaddy, htaccess, slow site, permalinks, Help Please!’ is closed to new replies.