• bitterrootbob

    (@bitterrootbob)


    Just upgraded to 2.7. The default permalink works but custom %postname% permalink gives me 404 error on all pages and full posts. .htaccess is writable.

    I have this problem on two sites. I have changed permalink structure, then gone back too the custom. These pages and posts are indexed so I don’t want to go to another structure.

    The sites are https://bitterroot-homes.com
    https://montana-guides.com

Viewing 8 replies - 1 through 8 (of 8 total)
  • truncale

    (@truncale)

    I had athe same issue and goofed around a bit… I solved it by making sure to include forward slashes on both sides. e.g. /%postname%/

    Thread Starter bitterrootbob

    (@bitterrootbob)

    I’ve tried that. It hasn’t worked.

    Roy

    (@gangleri)

    Bad idea:

    Using only %postname%
    If you use postname as the only element in your permalinks to create a structure such as example.com/post-title, the rewrite rules may make it impossible to access pages such as your stylesheet (which has a similar format) or the /wp-admin/ folder [is this true in WordPress 2.0+ versions?]. It’s best to include some numeric data (e.g. the post ID or date) in the permalink to prevent this from happening. Additionally, WordPress v1.2.x requires the use of a date structure in order for some features, such as the calendar, to function properly. /%year%/%monthnum%/%day%/%postname%/ is always a good start.

    Using %category% with multiple categories on a post, or %tag%
    When you assign multiple categories to a post, only one can show up in the permalink. This will be the lowest numbered category (see Manage Categories). The post will still be accessible through all the categories as normal.

    The same thing applies to using the %tag% field in your permalink structure.

    Thread Starter bitterrootbob

    (@bitterrootbob)

    I appreciate that but none of the preset permalinks works other than default. The other 3 give 404 also. The default permalink works. My pages are indexed as /%postname%/.

    I guess I’ll have to undo the 2.7 upgrade. Everything worked until this upgrade.

    Roy

    (@gangleri)

    Did it work previously? That’s odd. It can’t be this then either:

    Requirements:

    Apache web server with the mod_rewrite module installed
    In WordPress’s home directory,
    The FollowSymLinks option enabled
    FileInfo directives allowed (e.g. AllowOverride FileInfo, AllowOverride All)
    An .htaccess file (if this file is missing, WordPress will try to create it when you activate “pretty” permalinks)
    If you want WordPress to update the .htaccess file automatically, WordPress will need write access to the file.

    suarezst

    (@suarezst)

    I have the same problem has anyone find a fix for this?

    I am also facing the same problem….please help ??

    So you just upgraded to 2.7 and the default permalink works but custom %postname% permalink gives me 404 error on all pages and full posts.

    Is this true?

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘%postname% permalink not working in 2.7’ is closed to new replies.