what does your <Directory> directive of the DocumentRoot for the <VirtualHost> block look like?
i imagine something like this:
<VirtualHost …>
DocumentRoot /path/to/public_html/
…
</VirtualHost>
<Directory /path/to/public_html/>
AllowOverride All
…
</Directory>
or is yours structured in a different manner?
Hi Scaturan,
Don’t shake your head in frustration at me but my httpd.conf file does not have a <VirtualHost> block at all.
I host my own server. I am using Apache 2.0.52 with PHP 5.1.
<Directory “E:/My Files/Server Files”>
Options Indexes FollowSymLinks
AllowOverride None
Options Indexes MultiViews
Order allow,deny
Allow from all
</Directory>
This is my <Directory> block which happens to be all default values created when I installed Apache the first time.
As far as the AllowOverride None up above goes, if I change it to anything besides None, WP 2.0 gives me 403 forbidden error and won’t let me access my blog at all.
If I leave it as AllowOverride All I get the 403 error, but if I also add Options +SymLinksIfOwnerMatch to the top of my .htaccess file, the 403 errors go away but instead give me 404 errors for all post links and most PAGE links.
I am at a loss as what to do. I do wish to make it AllowOverride ALL so that I can also use User Authentification apps such as login scripts etc.
ahh, Apache 2.+ – sorry, not my forte. still using 1.3.34 here.
backup the current .htaccess file WordPress is using, replace with a blank, writeable one. then try this and see if it makes a difference:
<Directory “E:/My Files/Server Files”>
AllowOverride Options FileInfo AuthConfig
Options Indexes FollowSymLinks Includes MultiViews
Order allow,deny
Allow from all
</Directory>
it if does, regenerate your permalinks in WordPress.
Hello again Scaturan,
I gave your suggestion a whirl and I get the same results but in a round-about way as I decribed up above.
I stated previously that if I changed AllowOverride to something other than None I would get 403 errors unless I also added Options +SymLinksIfOwnerMatch to the top of my .htaccess file in which case it would give me 404 errors instead.
Well trying your suggestion gave me the same results, meaning I got 404 errors instead of 403 but this time I didn’t have that added line in my .htaccess file.
I just don’t get why this can’t play nice with everyone. What’s odd is four out of my nine PAGE pages work, I haven’t the foggiest idea why they work but everything else returns a 404 error.
Anyways, I am no further along in this than before and I am hoping you will find another rabbit to pull out of your hat. You are the only one responding to my request for help which I understand many people are tired of hearing about this persistant and dreaded PERMALINK issue.
Anyhow I’m still a no-go here.
Regards,
MAK
Haha! Woot!!!
After upgrading to WordPress 2.0.1 all my permalink problems appear to be gone! I can now use the date and time permalink structure like everyone else without using /index.php/ in my URL.
I knew there was a bug and that it wasn’t me, sweet deal!
My Thanks go to all the WP devs. Awesome work!
STATUS: RESOLVED
