Forum Replies Created

Viewing 15 replies - 286 through 300 (of 390 total)
  • Weird – just tested it and it worked fine here.

    http://russ.innereyes.com/menu.txt <– an example menu template

    http://russ.innereyes.com/sidebar.txt <– the line for sidebar.php to exclude page 16 from the menu

    These are exactly what I used (except my menu.php file has the Kubrick div tag in it) and it worked fine (looks stupid, but works).

    “She moves in mysterious ways, ahhhhh.”

    And i’m not editing it again!!! Obviously, I meant pages 69 and 66 in that top paragraph 🙁

    Moose, yup, as soon as we nail it down 😉

    <?php wp_list_pages('title_li=<h2>' . __('Pages') . '</h2>&exclude=69,66' ); ?>
    would exclude pages 69 and 63. Make sure there’s no single-quote between the numbers. It’s the exact same syntax as the exclude argument for wp_list_cats.

    Your exact line in the sidebar.php template file should read:
    <?php wp_list_pages('title_li=<h2>' . __('Pages') . '</h2>&exclude=16' ); ?>

    Just copy and paste 🙂 Let me know. It’s possible WP doesn’t like this because you’re ON page 16 but it’s trying to exclude it from the pagelist in the sidebar.

    EDIT: Gads I hate posting code in this thing 🙁

    The Jan11 nightly has flood-protection built-in, but it’s calculating time funny.

    In /wp-admin/functions-post.php, comment out the flood-control section from lines 447 to 454. Just stick a /* at the beginning of line 447 and a */ by itself on line 454. That’ll fix it for now.

    Well, not fix, but bypass so people can post comments at least 🙂

    Yup, there’s a comment bug in the Jan11 nightly for sure, I’m getting the same error.

    Gonna try to slap it around a little…

    While we’re on forum thingses 🙂

    It’d be nice to have page numbers available to click somehow. There are threads here approaching five and six pages long, and having to click “Next Page” that many times just to see the latest post is a bit of a pain.

    Second, it’d be nice (too) if, after you post a new response to a thread, you were taken directly to it (or at least it’s page) instead of being sent back to the beginning of the thread 🙂

    Create a template file in your theme folder and name it menu.php (any name is good, really). It should contain the following lines:

    <?php
    /*
    Template Name: Menu
    */
    ?>

    <?php get_header(); ?>

    <div id="content" class="widecolumn">

    <h2>Menu:</h2>
    <?php get_sidebar(); ?>

    </div>

    <?php get_footer(); ?>

    (this is using the 1.5 default template as an example).

    Then, in the admin section, create a new page (or edit the menu page you’ve already created there), and change the template to menu. Viola 🙂

    I think….

    The exclude support was already in the routine, just buried a little compared to the wp_list_cats one so I didn’t see it until I started digging for the thing 🙂

    I’m a liar!

    The tag you call from your template, wp_list_pages, will accept an exclude parameter 🙂

    So, in your admin interface, look up the ID number of the page you want to make invisible, then change the tag from:
    <?php wp_list_pages('title_li=<h2>' . __('Pages') . '</h2>' ); ?>
    to:
    <?php wp_list_pages('title_li=<h2>' . __('Pages') . '</h2>&exclude=69' ); ?>
    for example 🙂

    If you created a page in WP1.5 named “menu” using WPs page feature, then your actual URL would be http://www.mysite.com/menu/.

    Unfortunately, after looking at the WP source, there doesn’t seem to be an easy way to hide a page currently. I’m looking into adding the exclude argument from wp_list_cats to the wp_list_pages routine though, to see if it works 🙂

    Bad bad idea. While technically 1.5 can use the same database as 1.2, it’s only possible if you modify the wp-config.php file so you’re using a prefix other than the default wp_. In other words, any number of WordPress installations can share a database, but the must all use their own group of tables within it.

    So no, you will not be able to use 1.2 data with 1.5. The database would need to be upgraded (/wp-admin/upgrade.php), which would make it break with 1.2 after.

    Your page is starting 2 divs for a post – post and post2, but only post is being closed each time, which is causing post2 to nest inside itself over and over again.

    So, in your template, add a </div> right below the other one at the bottom of the post section, before the <?php endwhile; ?> line. That should fix it I think.

    Forum: Plugins
    In reply to: Rust’s 1.5 Plugins
    Thread Starter rustindy

    (@rustindy)

    Wouldn’t be much point I don’t think – people who are having that problem don’t seem to be able to activate any plugins 😉

    and you’ve renamed the .htaccess file?

Viewing 15 replies - 286 through 300 (of 390 total)