Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter michaelingp

    (@michaelingp)

    function posts_join_filter($join){
    global $wpdb,$wp_query;

    if(is_author()){
    $join_string = ” INNER JOIN $wpdb->term_relationships ON ($wpdb->posts.ID = $wpdb->term_relationships.object_id) INNER JOIN $wpdb->term_taxonomy ON ($wpdb->term_relationships.term_taxonomy_id = $wpdb->term_taxonomy.term_taxonomy_id)”;
    if (strpos($join,$join_string) === FALSE) {
    $join .= $join_string;
    }
    }
    return $join;
    }

    Basically, I just created a variable equal to the same text you appended, then checked to see if was already there before appending it.

    By the way, I also ran into a conflict between co-authors-plus and collapsing-archives, but that problem looks like its not in your code or implementation. I think your implementation is fine, I just mention this in case someone else brings it up.

    Thread Starter michaelingp

    (@michaelingp)

    Hmmm… On reflection, I was worried what the new SQL would do if a post wasn’t in a category, but on testing, it appears, that at least in 3.0.1, every post is in at least one category, even if it’s in the category named “uncategorized”.

    Thread Starter michaelingp

    (@michaelingp)

    The second problem turned out to be rather easy to fix. Just add “AND taxonomy = ‘category’ to the SQL. So line 87 in collapsArchList.php becomes:

    $inExcludeCatQuery =”AND $wpdb->terms.slug $in ($inExclusionsCat) AND taxonomy = ‘category'”

    Since problem one has a work-around (just use one category per post if you want to exclude that category from your archives), I think I’m done.

    Mike here, answering my own question. The answer turned out to be in the hostname. I was using ‘localhost’ as the form suggested. The correct answer for my environment was ‘127.0.0.1’. I’m using EasyPHP on a Vista computer, if that means anything. Obviously, “localhost” and “127.0.0.1” should be equivalent, but they’re not on my system, and I’m not in a real hurry to find out why. Still, you’d think the install program would come up with an error instead of the mysterious blank screen.

    Any other ideas? I have the exact same problem. The first install page works fine, but after a long time the address bar says: https://127.0.0.1/wp-admin/setup-config.php?step=2
    but the screen is blank.
    Curiously, the file wp-config.php is not created, which it seems it should be at this point.

Viewing 5 replies - 1 through 5 (of 5 total)