I Still Need HELP with WordPress htaccess on Apache server PLEASE

by 34 replies
40
I just created and uploaded a new PUBLIC video explaining the problem in detail.

YouTube video explanation: I Need HELP with WordPress htaccess PLEASE - YouTube

If anyone is really experienced in htaccess and multiple domains on one account - should not matter if it's on GDDY, hostgator or anywhere, it's still htaccess on Apache - or if anyone knows of anyone who knows of someone who knows how to fix this, it will very much appreciated! Thank you!

This "might" be an Apache problem, but after three emails and a phone call, GDDY tech support says it's a problem with WordPress and no one so far has been able to help. :confused:

I've also asked this question on StackOverflow: http://stackoverflow.com/questions/1...robably-apache

#programming #apache #htaccess #server #wordpress
  • in your root .htaccess you need to add this
    ErrorDocument 404 /404page.html <-- whatever you call you 404 custom page

    for each site you have in other domains you need just use the regular WP default htacess file in there root dir.

    Let me know if that works for you
    That should fix you up
    • [ 1 ] Thanks
    • [1] reply
    • Where in the htaccess file do I place this part of the code? Before or after the
      </IfModule>
      # END WordPress

      Also, my other sites/domains are not WordPress. They're html sites. I know I had put an errordocument line in the htaccess file before, and what happened was every page or category from ksmusselman.com went to the custom 404 page for the-bookmarks-store.com It's all so confusing. :-/
      • [1] reply
  • I would do the above and get the main working with the 404 and other WP sites operational first then tackle the HTML sites separately. Those HTML sites should already have there own .htacess files in there root.

    Sorry add that code I have above before the #END WordPress
    • [ 1 ] Thanks
    • [1] reply
    • Okay, did that, but it's still coming up as a one or the other deal. If the WordPress blog (ksmusselman.com) works, the html sites don't.

      If the html sites work, the WP blog doesn't.

      I don't know what htaccess files to put in the other directories and I don't know how to code the htaccess in the root (blog) directory so that it doesn't override what's in the other directories.

      I NEED to have the custom 404 page active on the-bookmarks-store.com AND I need the pages and categories to work on the ksmusselman.com blog - at the same time.

      So I need to know - can this even be done? Or is there something in the Apache server that won't ALLOW it to happen? Or is there a piece of code that I'm missing that won't allow it to happen?

      Or do I need to convert ALL of my sites to WP just because the site that's on the root directory is WP and there will always be a conflict with the other html sites?
  • Do you have these separate sites set up as 'addon' domains in your hosting account, or are you just pushing the domain to a subdirectory?

    In other words, are you using an 'economy' GD hosting account that only supports one domain, or are you on a multiple-domain account?
    • [1] reply
  • I'll explain a little why I asked the above questions: if you are using a 'Deluxe' or better GD hosting account, then a request to kmusselman.com should never encounter the .htaccess file on the-bookmark-store.com. If this is the case, it IS a NO-NO-NO-NO-NO-NO-NO- problem. Their server setup should never allow two domains to interact with each other.

    On the other hand, if you're trying to run multiple domains out of an 'Economy' package, you're going to continue to run into major headaches. WordPress handles 404s internally when any kind of permalink structure is used. The .htaccess file checks to see if the file requested exists. If it does, it is served. If it doesn't, the request is shunted to WordPress. You'll have to come up with a VERY complicated set of rewrite rules to get around this, and you won't be able to use the ErrorDocument directive, you'll have to order Apache to serve it up and send a 404 header.
    • [ 1 ] Thanks
  • You posted while I was explaining further...

    Go into your NO-NO-NO-NO-NO-NO-NO- account, and look to see what plan you're signed up on. It should say 'Deluxe' or 'Economy'.

    EDIT - at the moment, I am totally pissed off at the WF. I need to talk about G O DAd and it gets changed to this NONONONO bullshit
    • [ 1 ] Thanks
  • BTW, making a 10 minute video was not necessary. I almost didn't watch at all. You're better off to explain your problem as best you can and wait for questions if anyone has them.
    • [ 1 ] Thanks
    • [1] reply
    • Maybe not, but I got tired of typing and re-explaining. It was either that or transcribe my recording. I've been at this for three days without any relief.

      Anyway, my GD plan is "Hosting - Shared - Deluxe - Linux - Monthly (recurring)."

      I've emailed GD three times with an exact explanation and each time they gave me the same response - it's an Apache problem and I need to do some coding; it's inside the htaccess, etc., etc.

      So should I call GD again? I'm about to the point where I'll give somebody access to my computer AND my GD account to fix this. I'm not a programmer. This stuff is really foreign to me.

      I've gotten three different answers from three different sources and the results are always the same. It's really making me nuts.
  • The Deluxe account allows for multiple domains, so you should be safe there.

    Here's the raw deal, and you can quote me to GD's support: the .htaccess file for one domain should not - never, ever - affect any other domains, even in a multiple account environment. This isn't an Apache problem, it's a problem with your hosting account. If the .htaccess file for the-bookmark-store.com is affecting kmusselman.com or vice-versa, something is wrong at the server level. No two ways about it.

    Even in subdirectories - for example, your bookmarks site, where you have WP in /blog - WP-written .htaccess files have a RewriteBase directive, which restricts rewriting to that subdirectory. That's how you can have a WP install 'under' an HTML site and permalinks will still work for the WP install.

    People talk trash about GD hosting because their unconventional way of going about things sometimes causes problems. There are, even now, popular WP plugins that won't work with GD hosting because of their setup.
    • [1] reply
    • I'm on the phone with them now. THIS rep "gets it." (I did quote you by the way, thank you! :-) He knows EXACTLY what I'm talking about and he's got me on hold to talk to their server people to see about getting me answers.

      But this guy actually brought up my websites and walked through the problems with me so he was able to see what was going on and why it has to be changed somehow.

      At this point, I don't care if I have to have a 10-page workaround code in my .htaccess - as long as it works!

      Will update later on... one way or the other.
      • [1] reply
  • EDIT: we're crossing posts LOL disregard the next sentence
    Read a couple of posts up where I outlined what should go in the htaccess file for the two html domains.

    If you do that and it screws up the WP installs in those domains, add this to the top of the WP htaccess files:
    Code:
    ErrorDocument 404 default
    In normal Apache, that sets the error doc back to the server default and overrides any ErrorDocument directives in parent directories.
  • When you say, "didn't work" I don't have a lot to go on. Did you get 500 errors, and what URLs did you get them on?
    • [1] reply
    • Yes, 500 Internal Server errors when I typed in a non-existent page to both the-bookmarks-store and jimscustomcrafts.

      The monster blog - frankenblog - creating the havoc is still working fine with its WP-generated .htaccess file.
      • [2] replies
Join the discussion

Next Topics on Trending Feed