• Resolved loopme

    (@loopme)


    I’ve tried to do my due diligence with searches and testing out several things; but to no avail!

    I am new to WP (and not entirely technically proficient with it, although I try!) and hope to import my old blog soon, but wanted the new stuff up and running first. The install went great. However, when I went to set my permalink prefs, it mentioned not being able to write to my .htaccess file. (seems like a common thing!)

    I’ve verified my host does allow this. I checked my ftp file listing and I do not currently have this file, so I created one and placed it at the same root level as my WP index file.

    Whenever I add the .htaccess file, I get the error 500 msg and can’t see anything on my site. Without the file, I can get to the index.html page, but no other pages (such as about or expanding the single post there); this yields a 404 error.

    my site: https://www.bebackonmonday.com

    I’ve tried a blank file, in case WP could write on it. no.
    I’ve tried

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

    and

    RewriteEngine on?RewriteCond %{HTTP_HOST} ^www.bebackonmonday.com$ [OR]?RewriteCond %{HTTP_HOST} ^bebackonmonday.com$?RewriteRule ^(.*)$ https://sub.domain.com/ [R=301,L]

    Does anyone have other suggestions?
    Thanks so much!!

Viewing 7 replies - 1 through 7 (of 7 total)
  • Clayton James

    (@claytonjames)

    I’ve tried a blank file, in case WP could write on it. no.

    Were you able to log into your dashboard with the blank .htaccess file in place?

    Thread Starter loopme

    (@loopme)

    no! just tried that and received the error 500 msg.

    Clayton James

    (@claytonjames)

    Strange. As long as there are no sub-directory issues or misplaced .htaccess files involved, I would think things would be okay. The 404’s are a mystery though. I can’t even pull up your About page.

    I know it seems redundant, but revisit your permalinks settings and make sure they are reset to the default and saved – then create the blank .htaccess file again. Once you do, this time change the file permissions to at least 666 (remember, these permissions are only temporary). If you can access your dashboard, and if WordPress will update the file automatically for you without the error message, you’re good to go. I’m afraid after that I’m out of ideas.

    Thread Starter loopme

    (@loopme)

    ah, very interesting! I changed the permalinks to default and the other pages now work! However, when I added the blank .htaccess file, once again the 500 error msg appear.

    Where are the file permissions located that you mention?

    thank you for helping me get the other pages to appear!

    Clayton James

    (@claytonjames)

    You can usually set the file permissions using your ftp client or file manager. There is some good info on that here:

    Changing File Permissions

    Thread Starter loopme

    (@loopme)

    Thanks CJ. I’ve read that page now, but to be honest, get a bit lost! I don’t see how to change permissions from within my ftp client (Fetch). I can see how to do it to a file on my desktop (which I could then upload), although the dialog box on my Mac looks quite diff than that shown in example. No place for entering numbers; just assigning read/write. I am thinking I am not in the right spot!

    So far, I’ve only tried modifying the index.php file. If only I could find that number box…

    Thread Starter loopme

    (@loopme)

    well whatyaknow… so sooner did I post that when I found a button and the box to enter in permission codes! I entered “666” to my index.php file. However, once I add that .htaccess file (again, with permissions set to 666), error 500 msgs pop up and I can’t access my site, nor the admin page.

    I think I’ve exhausted your knowledge/recommendations…
    Hoping someone else might have an idea?

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘that pesky .htaccess file = big headache!’ is closed to new replies.