calendar permalink broken?

  • It seems to me that generation of calendar permalinks are broken in 1.2 release. ??
    Here are my permalink settings:
    /archives/%year%/%monthnum%/%day%/%hour%-%minute%-%second%/%post_id%/
    And this is the code the wordpress generated for me:
    RewriteEngine On
    RewriteBase /blog/
    RewriteRule ^archives/category/(.*)/(feed|rdf|rss|rss2|atom)/?$ /blog/wp-feed.php?category_name=$1&feed=$2 [QSA]
    RewriteRule ^archives/category/?(.*) /blog/index.php?category_name=$1 [QSA]
    RewriteRule ^archives/author/(.*)/(feed|rdf|rss|rss2|atom)/?$ /blog/wp-feed.php?author_name=$1&feed=$2 [QSA]
    RewriteRule ^archives/author/?(.*) /blog/index.php?author_name=$1 [QSA]
    RewriteRule ^archives/([0-9]{4})?/?([0-9]{1,2})?/?([0-9]{1,2})?/?([0-9]{1,2})?-([0-9]{1,2})?-([0-9]{1,2})?/?([0-9]+)?/?([0-9]+)?/?$ /blog/index.php?year=$1&monthnum=$2&day=$3&hour=$4&minute=$5&second=$6&p=$7&page=$8 [QSA]
    RewriteRule ^archives/([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([0-9]{1,2})?-([0-9]{1,2})?-([0-9]{1,2})/([0-9]+)/(feed|rdf|rss|rss2|atom)/?$ /blog/wp-feed.php?year=$1&monthnum=$2&day=$3&hour=$4&minute=$5&second=$6&p=$7&feed=$8 [QSA]
    RewriteRule ^archives/([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([0-9]{1,2})?-([0-9]{1,2})?-([0-9]{1,2})/([0-9]+)/trackback/?$ /blog/wp-trackback.php?year=$1&monthnum=$2&day=$3&hour=$4&minute=$5&second=$6&p=$7 [QSA]
    RewriteRule ^feed/?([_0-9a-z-]+)?/?$ /blog/wp-feed.php?feed=$1 [QSA]
    RewriteRule ^comments/feed/?([_0-9a-z-]+)?/?$ /blog/wp-feed.php?feed=$1&withcomments=1 [QSA]
    evrything works fine with it except of the calendal links like https://aim.pp.ru/blog/archives/2004/05/24/
    They give the “404 not found” error.
    Can someone advise me how to fix this problem?
    You can see the problem by yourself pointing your brouther to https://aim.pp.ru/blog/ – it’s in russian but I suppose it doesn’t matter in this case. ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter aim1159

    (@aim1159)

    I can’t use the default permalink structure because I’m using russian in my post topics — non ASCII symbols currently not allowed in URLs :(((
    And the solution descriped there doesn’t work for me too.

    Thread Starter aim1159

    (@aim1159)

    Currently I find the solution – I removed the %hour%-%minute%-%second% from my permalink structure and now it works.
    I suppose this could help to find the solution to fix this bug.
    No my settings are:
    /archives/%year%/%monthnum%/%day%/%post_id%/
    and the rules generated:
    RewriteEngine On
    RewriteBase /blog/
    RewriteRule ^archives/category/(.*)/(feed|rdf|rss|rss2|atom)/?$ /blog/wp-feed.php?category_name=$1&feed=$2 [QSA]
    RewriteRule ^archives/category/?(.*) /blog/index.php?category_name=$1 [QSA]
    RewriteRule ^archives/author/(.*)/(feed|rdf|rss|rss2|atom)/?$ /blog/wp-feed.php?author_name=$1&feed=$2 [QSA]
    RewriteRule ^archives/author/?(.*) /blog/index.php?author_name=$1 [QSA]
    RewriteRule ^archives/([0-9]{4})?/?([0-9]{1,2})?/?([0-9]{1,2})?/?([0-9]+)?/?([0-9]+)?/?$ /blog/index.php?year=$1&monthnum=$2&day=$3&p=$4&page=$5 [QSA]
    RewriteRule ^archives/([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([0-9]+)/(feed|rdf|rss|rss2|atom)/?$ /blog/wp-feed.php?year=$1&monthnum=$2&day=$3&p=$4&feed=$5 [QSA]
    RewriteRule ^archives/([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([0-9]+)/trackback/?$ /blog/wp-trackback.php?year=$1&monthnum=$2&day=$3&p=$4 [QSA]
    RewriteRule ^feed/?([_0-9a-z-]+)?/?$ /blog/wp-feed.php?feed=$1 [QSA]
    RewriteRule ^comments/feed/?([_0-9a-z-]+)?/?$ /blog/wp-feed.php?feed=$1&withcomments=1 [QSA]

    Putting static strings and characters into post permalinks will break the calendar links. By static strings I mean anything that is not a %keyword% or a forward slash. The RewriteRule generated by WordPress will break for calendar links if there are static strings present. It is possible to change the RewriteRule by hand to get it working. I’m working on a fix for the next release.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘calendar permalink broken?’ is closed to new replies.