Support » Plugins and Hacks » Bug or feature? ->index.php?cat=13&w=34

  • Hello community,
    Is this a serious design flaw or am I just unlucky ?
    I first call e.g. /index_title.php?cat=11&m=2004&w=34
    (It lists all titles to articles in a certain week)
    This yields all news in Cat 11 of Week 34. So far so good.
    But then I use the same index_title.php to call e.g. Cat 13 of week 34
    and it shows the same output , no matter what. AND NOW THE FUN:
    If I use a fantasy category# , lets say index_title.php?cat=999&m=2004&w=34, which doesn´t even exist, it shows the same content again, no 404 or empty result or what but the same. The delimiting by date is working fine.
    FINDING Until now: Using a date like w=34 in the query ALWAYS overrides the cat=”n” query.
    Where (and even better how) can I change that ?
    my relevant code
    <?php wp_get_archives(‘type=weekly&format=link’); ?>
    <!–<?php get_archives(‘daily’,”,”,”,”,’TRUE’); ?>–>
    <?php //comments_popup_script(); // off by default ?>
    <?php wp_head(); ?>
    </head>
    <body>
    <div id=”rap”>
    <h3 id=”header”><?php bloginfo(‘name’); ?></h3></div>
    <div id=”content”>
    <?php if ($posts) : foreach ($posts as $post) : start_wp(); ?>
    <?php the_date(”,'<h2>’,'</h2>’); ?>
    <h3>” rel=”bookmark” title=”Permanent Link: <?php the_title(); ?>”><?php the_title(); ?><?php _e(‘ – ‘); ?><?php the_time() ?></h3>

Viewing 3 replies - 1 through 3 (of 3 total)
  • Have just tried this (in 1.2 Mingus) – with the same results, it returns all posts in that week regardless of which cat is chosen.

    Well this is interesting. I am now using a single cat on my front page. A side effect is that my archives do not work (so now temporarily deleted) Odd.

    Solved: Strange behaviour with “w” (week).
    Problem was: uncontrollable behaviour if&when “week=x” was used with some other query like “cat=x”
    Solution:
    Delete “intval($w) ||” in Line 242 of wp-blog-header.php

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.