Using only %postname%

0 Views

So I see everyone’s arguements against using this, but that seems like a huge flaw in WordPress because a domain name as close to the root is crucial to a site’s SEO.

I want my site which has rough 8 pages total to be able to be found by their simple titles, if they’re preprended by a date, it just look convoluted and out of standards with most web standards.

Read More

Fast forward to me adding %postname% to my custom permalinks tab, all my url’s were updated, and clicking on them brings me a 404.

No .htaccess file was made so I made one from scratch and included this : 

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

# END WordPress

Update

Any of the permalinks except for the post ID option do not work. None of them work.

What o’ what am I missing from this to make it actually work?

UPDATE 12/13/2011

WordPress 3.3 was just released. And all these problems still exist. Clicking on any of the permalinks writes this to your .htaccess . The same text for any of the options : 

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

# END WordPress
#

Using /%postname% doesn’t work. At all.

Post Views: 0

Related posts

Leave a Reply

3 comments

  1. What I did was reinstalled WordPress from the Dashboard Update area…then I made the Permalinks like this

    /index.php/%postname%/

    It worked fine

  2. Just had the same problem.

    Turns out that my host (names.co.uk) doesn’t use Apache, instead it uses Zeus – which does not support Mod_ReWrite, and so no .htaccess file.

    They have published a workaround here:
    http://www.names.co.uk/support/hosting/linux_hosting/1119-wordpress_rewrite_script.html

    #Zeus webserver version of basic WordPress mod_rewrite rules
map path into SCRATCH:path from %{URL}
look for file at %{SCRATCH:path}
if exists then goto END
look for dir at %{SCRATCH:path}
if exists then goto END
##### FIX FOR LOGIN/FORGOTTEN PASSWORD/ADMIN ETC #####
match URL into $ with ^/wp-.*$
if matched then goto END
##### FIX TO ALLOW SEARCH TO WORK #####
match URL into $ with ^/(.*)
set URL = /index.php/$1

    For installations up any level from the docroot:

    #Zeus webserver version of basic WordPress mod_rewrite rules
map path into SCRATCH:path from %{URL}
look for file at %{SCRATCH:path}
if exists then goto END
look for dir at %{SCRATCH:path}
if exists then goto END
##### FIX FOR LOGIN/FORGOTTEN PASSWORD/ADMIN ETC #####
match URL into $ with ^/blog/wp-.*$
if matched then goto END
##### FIX TO ALLOW SEARCH TO WORK #####
match URL into $ with ^/blog/(.*)
set URL = /blog/index.php/$1

    Maybe check your host and see if uses Zeus too.

  3. Looking around, and after hrs of trying to figure out why all of the sudden, /%postname%/ stopped working,

    i read somewhere(Found it!)

    http://digwp.com/2011/06/dont-use-postname/

    about performance issues reguarding

    URL/postname

    and all the running around WP does with the server just to return said data

    and long story short, it was recommended for performance reasons (usually with bigger sites) to start with a number etc…

    Since my /%postname%/ stopped working out of the blue.

    i changed my newly not working permalink of /%postname%/ to /%post_id%/%postname%/
    and its now working.