Fold Page List updated for WP 2.1 compatibility

Hi,

Version 1.72 updates section-wise fullunfold to behave with greater consistency, avoiding situations where parts of a fully unfolded section would collapse as the section is navigated. Sections now remain fully unfolded wherever you happen to be within the section. Hope that’s clear!!

Version 1.73 provides a fix for various warning messages affecting some installations of the plugin.

1.73 is the current version and is available from the links in the previous post

Best regards

Rob

Hi,

Version 1.74, which applies a permanent fix for the warning messages is now available from te above links

Best regards

Rob

Hi Rob,

In your instructions it says: To use, simply replace the code fragment that looks like this
<?php wp_list_pages ($args); ?> with this: <?php wswwpx_fold_page_list ($arglist); ?>

Newbie question… I tried several themes, but nowhere I find ($args) in the sidebar.php… only things like: <?php wp_list_pages(‘title_li=<h2>Pages</h2>’ ); ?> or <?php wp_list_pages(‘sort_column=menu_order&title_li=’); ?>

So what to do?

Robberto

I’m having precisely the issue that Robberto is having above: that line doesn’t seem to exist, and replacing the apparently relevant line in sidebar.php just nukes the file.

Hi,

Apologies for coming late to this, but I don’t always check here in the forum, especially when busy.

The ‘$args’ or ‘$arglist’ is the list of arguments passed to the standard template tag, wp_list_pages, as documented in the mainwordpress codex, and mentioned on the plugin support page. To take one of Robberto’s examples above, replace this:

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

with this:

<?php wswwpx_fold_page_list(‘sort_column=menu_order&title_li=’); ?>

That is, just replace the wp_list_pages tag with the call to the plugin… don’t change the arguments unless you wish to, and the standard wp_list_pages arguments, with which Fold Page List remains compatible, are fully documented in the main wordpress codex.

Please note that, in general, for problems of this sort, email direct to the address in the header of the plugin is likely to be attended to faster than by posting problems here.

Hope anyway that this helps clear the murk.

Best regards

Rob