Comment box not enabled

as Ive already stated, SOME of your files are sending 500s.

additionally, youve NOT answered my question regarding your .htaccess

lastly, I find you to be smug and not willing to do anything except “blame” something else, and not look at your own set up. And then make excuses about your remarks.

Good luck. I’ve moved on. people get one shot with my help — thats all.

Thanks for nothing.
And for doing your best to make sure no one else looks at it either.

I ahve to agree with whooami…
Instead of writing this kind of long nonsenses, like

Whether or not it’s a WordPress bug, it is an oversight. It seems that just about everyone would want their permalinks set to post name rather than questions marks and numbers.

The option to change the permalinks exists, but it virtually disables the functionality of the blog, because people can’t view individual posts by clicking the title, and cant respond by clicking the respond button.

…you should read carefully the replies and please, answer the questions if the helpers request more information.
You were asked twice about your htaccess file. Instead of answering you went ranting about a “bug” that doesn’t exist. Don’t be surprised if helpers gave up on you. Less ranting and more focus!

The reason why the ugly links (p=???) etc work is because all they have to do is go directly to your index.php with the querystring attached. They can do that without any rules to rewrite ULRs from .htaccess.

The reason why the default mechanism is to use ugly permalinks is because not all hosts support .htaccess files. so if the default was to use pretty permalinks lots of new installs would be broken from the start.

I’m 90% sure the reason why your install is having problems is down to the .htaccess file, but it’s incredibly difficult to say exactly what is wrong with it without seeing it.

For comparison, this is the (relevant) bit of mine –

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

# END WordPress

That’s *all* you need in it to do the pretty permalinks.

Try to check yours.

This is my .htaccess. Couldn’t get my permalinks running. I don’t find the “?” that ugly..

# 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 for the response

I read every reply carefully and try to address each point and question made. I answered mrmist yesterday about my .htaccess files

Quote-“Well, that could have something to do with it…
I tried to view the .htaccess file and the the message came back –
Forbidden
You don’t have permission to access /consciousness/.htaccess on this server.

I changed the perms for full access for the owner, public can read and group can read and write (public and group are set to default…)

but the comments are still not working.

What should the .htaccess be set to?

Could there be another way to set the URL correct? ”

I never got a clear answer.

It was suggested that I set the the .htaccess to full perms and try to resave the permalink structure and see if it works and then change the .htaccess back to the default.

I believe that I have literally tried every combination of .htaccess and permalink structure to no avail.

I’ll try this new code – does anyone know whether line 4 is better written –
RewriteBase /blog/
or simply
RewriteBase /

and Which folder should I look for (or insert?) this code into?

The bit that you need to use here

RewriteBase /blog/
or
RewriteBase /

Depends on where your blog is. If it’s in a subdirectory called blog, use the first, if it’s in your main web site directory, use the second. If it’s somewhere else, use

RewriteBase /somewhereelse/

It was suggested that I set the the .htaccess to full perms and try to resave the permalink structure and see if it works and then change the .htaccess back to the default.

Did you do that? What were the results? Did the .htaccess file change as you changed the options for permalinks?

you read the replies carefully?

you missed this:

Well, that could have something to do with it…
I tried to view the .htaccess file and the the message came back – Forbidden You don’t have permission to access /consciousness/.htaccess on this server.

Yeah. You won’t be able to view it directly through the browser, you’d have to look at it through shell access onto the server, or by downloading it in your ftp client.

——–

this is apparantly a second domain on the same web space that is hosting amanamission.com, therefore, it would be helpful to NOT ONLY know what the .htaccess inside the root of your WP install says, but the other .htaccess at the root of your webspace says, assuming there is one there, and I bet there is.

rules, and what not inside ANY .htaccess are hierarchical.

whooami”Good luck. I’ve moved on. people get one shot with my help — thats all. “

please do.

mrmist- “Did you do that? What were the results? Did the .htaccess file change as you changed the options for permalinks? “

thank you for your help mrmist!
I did try doing that quote:

It was suggested that I set the the .htaccess to full perms and try to resave the permalink structure and see if it works and then change the .htaccess back to the default.

I believe that I have literally tried every combination of .htaccess and permalink structure to no avail.

I was changing the perms in the .htaccess contained within the blog directory.

I am hosting 5 domains and 3 blogs on this host. All of the blogs are having the same problem.

Each directory containing a blog has a corresponding .htaccess file. Each .htaccess file looks like this –

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

# END WordPress

There is also one .htaccess file in the root directory for all of my domains. It looks the same.

Do I need to change the .htaccess in each blog directory to say the location, or is the rewrite base location implied because the .htaccess file is in that directory.

To answer your question – Did you do that? What were the results? Did the .htaccess file change as you changed the options for permalinks?”

I am not sure. But above is how it looks now.

There must be some odd thing with your whole setup: either theme related or related to the different directories/redirects.

In an earlier post you said your blog is here:
https://www.bookofmoron.com/
Well, if you click on a post’s permalink, you get this:
https://www.bookofmoron.com/off-beaten-paths-no-way-by-ram-tzu/
This is almost OK, it shows the single post view and it has a link below saying View Comments… Now that’s odd.
Clicking on that link it will bring up your existing comments AND the comment form:
https://www.bookofmoron.com/off-beaten-paths-no-way-by-ram-tzu/?p=1#comments

Now, that’s not a normal WP behaviour and something has to be not normal in your setup!
1. The single post view behaves like an index or other multipost view
2. When clicking on the “View Comments” your URL becomes = a nice permalink + an ugly permalink

This is NOT a WP bug. It is your installation. Unless you describe in detail where the WP install is, where is it displayed, any redirect, pointing etc. – nobody will be able to help you. Don’t rant. Just list the facts!

Yeah, that’s the work-around I put in to compensate for the error…that link is part of the post. I discovered that I could reach the comment page by adding that link, so it’s almost ok…except that I have to add it to each post.
I’m not sure what information you want about my setup. It’s pretty straightforward and a lot of the oddities users seem to be seeing are the result of many, many experiments, most of which have been undone.
I am hosting five domains, three of which are blogs, and I assure you that nothing is unusual about my setup.
What facts do you think would be helpful?

You should have started with one single fact – that you are hosted on netfirms.
Do a search for your host’s name and then you will be much more educated.
But I can tell you the end-result: get a decent host. Nothing works on their servers when it comes WP and permalinks.

I’m aware that Netfirms stinks, but what has that to do with it? I’m not using the one-button install…and I can’t change hosts, for a variety of reasons I’m stuck with it. What, exactly, prevents Netfirms from completing this transaction. Is it a lack of software?

I don’t know. And not even interested to learn, sorry.
They just got on my blacklist of hosts after trying to help a lot of users… all having problems with permalinks on that host.
Ask them “what prevents them” to become a decent host.

Well, actually, this is the first real piece of information I’ve gotten about this. It does seem that Netfirms started having compatibility issues with 2.0. Fortunately, I’ve found a couple of articles containing hacks that users say worked for them, and if I solve the problem, I’ll post it here so future users can waste less time with this.
The issue seems to be that Netfirms does not support Allow Overwrite.
So not a WP bug after all, just a compatibility issue with a large host. Hopefully these hacks still work.