1) A top-level Page has no sub pages, even if it has sibling pages

and

2) A sub page at any level has neither sibling pages nor sub pages

When a Page has neither sibling pages nor sub pages, your widget produces an empty box that clutters the sidebar. I think it would be ideal if the widget would display nothing at all under these circumstances, just as it shows nothing on non-Pages like posts and archives.

Thanks for your consideration, and thanks again for the plug-in!

*@sebastian*: Thanks for trying to help out! I’ve finally updated the widget :-)

Fatal error: Call to undefined function: register_sidebar_widget() in /home/m/a/mattkevan/public_html/wp-content/plugins/widgets/subpages.php on line 72

I tried Eric and Sebastian’s code but it doesn’t work.
Thanks.

You’ve to change the code as followed:
at the top of the code put following
function subpages_control_init() {
and at the end of the file please insert
}
add_action(‘plugins_loaded’, ’subpages_control_init’);

So it work’s fine for me.
Best regards from good old Germany to all of You!

Did a little digging around and it looks like the registration sequence in the plugin is incorrect. For some reason, WP chose to load the subpages plugin before it loaded widgets plugin on my server, so the call to register_sidebar_widget was hitting the dreaded undefined error.

I replaced the two register_ calls at the end of the file with the following sequence, and all was good with the world:

function subpages_init() {
if ( !function_exists(‘register_sidebar_widget’) )
return;

// Tell Dynamic Sidebar about our new widget and its control
register_sidebar_widget(‘Sub Pages’, ’subpages’);
register_widget_control(‘Sub Pages’, ’subpages_control’);
}

add_action(‘plugins_loaded’, ’subpages_init’);

Unfortunately, it looks like this plugin isn’t going to do what I need it to do, but I hope this info helps.

Fatal error: Call to undefined function: register_sidebar_widget() in /home/m/a/mattkevan/public_html/wp-content/plugins/widgets/subpages.php on line 72

Any ideas of what’s going wrong?

Thanks for your help!

Matt

I would like a back-link. So if I am on a Subpage a link to the parent page is listet (maybe named back).

get_var(“SELECT post_parent FROM $wpdb->posts WHERE ID = $current_page”);

to

get_var(“SELECT post_parent FROM $wpdb->posts WHERE ID = ‘$current_page’”);

Hope my corrections are shown. Otherwise, current_page needs to be in single quotation marks.

if ( is_single() || is_page() ){

to

if ( is_single()){

And that was that! Wonderful. You might consider adding an option to the widget so that people can choose whether it appears on posts, pages or both. But in the meantime, this certainly works fine for me.

When I first installed UTW and had it automatically display tags on all posts, it turned out that this caused a strange behavior. Because I also had it automatically adding Categories as Tags, it was taking my default Category and adding is as a Tag even on my *pages*, not just my posts. That word then showed up, bizarrely, on all my pages. I had to have UTW stop automatically displaying tags everywhere, instead adding it only as I wished on particular templates. That fixed that.

However, now, even a tag archive shows only posts and not pages, when I go to a post that is in my default category, lo and behold, your UTW Related Posts widget shows a number of my pages!!! I’m guessing that UTW is somehow continuing to add that default category as a tag even on all my pages. An archive knows to only look for posts, but your widget seems to look for everything. Do you know if:

1) There is a way to eliminate that default item from the pages somehow, and/or

2) If you can revise your widget to act just like tha archive, looking only at posts and not both posts and pages?