puckrat

@myers1984 … I think maybe I understand what you’re asking for ==> you’d like for the comments references (i.e. comments off) to not show when a given post is not set to have comments. I found a method that works for me, with the theme I’m using. Perhaps it will work for others as well. My particular theme was showing the comment input box even when comments were off *and* I wanted to get rid of that oh so annoying “comments off” message. So …

With my theme it meant editing three theme files:

• archive.php
• comments.php
• index.php

In each case, where I didn’t want the comment info to show if comments were off I placed the comment line display in an if statement:

<?php if ('open' == $post-> comment_status) : ?> ... <?php endif; ?>

i.e.

| <?php comments_popup_link('Leave a Comment', '1 Comment', '% Comments'); ?>

becomes

<?php if ('open' == $post-> comment_status) : ?> | <?php comments_popup_link('Leave a Comment', '1 Comment', '% Comments'); ?><?php endif; ?>

Note: This has some additional work needed, as the comments info will not show at all if comments are off. Meaning if you had comments on, received comments, and then turned comments off … nothing of those previously received comments will be seen. I imagine something to do with

<?php if ($comments) : ?><?php endif; ?>

might be helpful in evaluating, and some sort of tiered if/then/else statement with the comments and comment_status variables. But that’s as far as I got this morning. :p

Drat, can’t edit. … I also set the wp_options table recently_edited option_value to null.

Ahhhh … following info in http://ww.wp.xz.cn/support/topic.php?id=26896 I went into the template-functions-post.php file’s get_pages() function and commented out the …

if (!isset($cache_pages) || empty($cache_pages)) {

… line, and it’s closing bracket, and uploaded the file. Works great! I do have empty categories (something that post menthioned the cache check might be gaurding against) and thus far am having no issues. Will keep an eye out, but hope all this helps someone else too. :0}`

lines

I too am experiencing some oddities with the wp_list_pages function resulting in a line 368 error.

I’m calling the wp_list_pages function from a static page, and there it works beautifully. But in the sidebar call for that page I then get the line 368 related error.

If I click to another page, the sidebar call resovles itself, but if click back to the page where the additional wp_list_pages function is called, it burps again.

code in page see result image
():

< ?php
global $id;
$pagesArguments = “child_of=”.$id.”&title_li=”;
//echo $pagesArguments;
wp_list_pages($pagesArguments);
?>

code in sidebar: see result image

&lt?php wp_list_pages(); ?>

I’m not sure I understand why the two seperate calls would affect one another. And there is certainly other code being successfully executed between the two.

I tried adding to the page the one line as mentioned in the comment above:

<?php wp_list_pages(‘sort_column=menu_order’); ?>

and then that call, and the call I make in the page, and the call in the sidebar then all work. But of course that first call displays *all* pages, and that’s not what I want.

I tried then removing that line again, and adding in the sort_column argument to just the page call, the page call & the sidebar, and then just the sidebar call, and all had the same results as shown in the images above. {sigh}

I’m having the same issue, having installed this plug-in last night. If I figure out the cause and hopefully fix, I’ll let you know too. :0}`
http://blog.puckrat.com