urbanscout

Hm. Actually changing it fixed the new galleries, but broke the old ones. ??

@erik,

I was having this problem too, and tried your code and it worked. Thank you!

Um… I have no idea what I did, but it works.

I have only one .htaccess file, and it’s in the root.

I think the key was you having me copy the index.php into the WP directory.

Than I deleted all the .htaccess files and changed everything back to normal in the permalinks. This must have created a default .htaccess file, which I was than able to change to /%postname%/ and bam!

All that screwing around with the .htaccess must have messed it up. Now I just hope my site doesn’t crash after 20 minutes…

It automatically created this one in the root:

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

# END WordPress

I changed it to your mark up with “wordpress” in the appropriate places, and created the same one for the directory folder as well. The site still reverts to text only when I put in your code to the .htaccess file in the WP directory. And the links still don’t work.

…and the site now has a 500 internal server error again…

post less read more…

Haha. I’m trying. I’ve been at this for over 12 hours now and still no luck. I am not computer savvy, but it looks like even the savvy ones are having a hard time with this one. I really appreciate your help. You’re the first person actually helping me figure it out.

It looks like wordpress has created an .htaccess file in the root directory, but not the wordpress directory. Yet when I create an .htaccess file, blank or with the same code as the other, the site reverts to text only and the links still don’t work.

Even though when I click Update Permalinks, and it says, “Permalinks Updated” the links still don’t work. it doesn’t even tell me to update my .htaccess files anymore. What does that mean?

Yes I just noticed that! I missinterperetted the “copy” as “move to.”

So I went backwards. I created another index file for my /wordpress directory and changed it back to

require(‘./wp-blog-header.php’);

Now I need to create two .htaccess files? I don’t understand that part. Are they empty? Do they both need to have the mod_rewrite code? WordPress doesn’t automatically create them?

Thanks Moshu,

My general options say this:

WordPress address (URI): https://www.urbanscout.org/wordpress
Blog address (URI): https://www.urbanscout.org

I read the Giving wordpress it’s own directory… but I still don’t get what I have done wrong.

Interesting… So I gave up and deleted the .htaccess file. Of course my graphics came back immediately. I then went into my admin and changed the permalinks back to the default. Than I changed them back to /%postname%/ and I this time when I clicked the update permalink button, it said, “Permalinks updated” instead of “you need to update your .htaccess file.” WTF? Could it be that I activated some feature in the godaddy 2.0 hosting configuration? That must be it… Though, the links still don’t work. I will wait for an hour again and see if they get updated.

Okay, so when I move the .htaccess file into the wordpress directory, I can access the main page of my site, but the main page comes out as just text.

…still cannot access individual pages.

Now my error log says:

[Sun Nov 11 15:56:48 2007] [alert] [client 69.5.109.191] /var/chroot/home/content/s/c/o/scoutwithclout/html/wordpress/.htaccess: Invalid command ‘(This’, perhaps mis-spelled or defined by a module not included in the server configuration

At this point, I don’t know what to do. I am going to move the .htaccess file to the urbanscout.org/wordpress/.htaccess directory and wait. If that doesn’t work after a while I will just delete the .htaccess file and change my permalinks back to their ugly ass selves. What a waste of time.

Okay, I got into the CGI admin and checked the error log and found a whole bunch of these:

[Sun Nov 11 15:45:27 2007] [alert] /var/chroot/home/content/s/c/o/scoutwithclout/html/.htaccess: Invalid command ‘(This’, perhaps mis-spelled or defined by a module not included in the server configuration

I upgraded my godaddy account to their hosting configuration 2.0:

https://help.godaddy.com/article.php?article_id=1076&topic_id=412

I activated the error log, but I still can’t access it. I’ll wait another hour or so and see if that’s working… though I don’t know why that should change anything.

Here is what godaddy had to say:

Thank you for contacting Online Support. Please note that while Go Daddy Customer Service Representatives cannot debug your CGI Scripts or HTML website coding the information below should help you with your CGI enabled hosting account. There are many variables that could cause a page not to work correctly. As you troubleshoot the problem, bear in mind some of the more common causes of problems with scripts:

? If you are using Perl, make sure that the path to the interpreter is listed correctly as:

#!/usr/bin/perl

? Look for capitalization errors or other kinds of typos. (in both you CGI and HTML)
? Check the permissions for the files in your CGI bin. (Hosting subfolder “CGI” is your “CGI-BIN” folder; as many customer CGI scripts call for the “CGI-BIN” folder, rename this to the “CGI” folder.)

Many problems with Perl CGI scripts can be resolved by paying careful attention to the three issues mentioned above.

I have no idea what this means. How does this relate to the .htaccess file?

Okay, so I waited about an hour, checking frequently if the site would work. Now all of a sudden the main page of the site is not working. At this point I think I’ll just wait a little longer and see if anything else happens.