roblgs

Hi,

The fold page list plugin generates an unordered list (or a whole set of nested unordered lists) and applies full styling of the page hierarchy and ancestry of the current page within those lists right back to the root.

Changing the behaviour to allow for drop-downs, or from horizontal to vertical orientation is achieved through CSS, and perhaps a little unobtrusive javascript for the recalcitrant browsers that don’t understand a full CSS vocabulary.

Cheers

Rob

Hi,

Did you contact me (the author of the plugin)? I don’t recall seeing anything in my mail… there’s an email address in the header of the plugin…

Anyway… I’m a little confused by what you mean by all this… You also seem to be mixing categories and pages/posts and I’m not sure the if… else (which afterall was created for handling pages) is doing what you think it is doing.

If the tested value is non-zero then the plugin will show the (sub-)categories of whatever that value is. If the tested value is zero it will display for catregory ‘4’.

I suspect that you are getting non-zero values where you expect to have zero, and maybe even zero where you expect to have non-zero.

Regards

Rob

Hi,

I’ve just posted an explanation of how to build multi-level page navigation lists which goes into a little more detail than above.

Cheers

Rob

Hi,
It would be useful to see what you have tried by way of css already, but essentially the fold page list plugin will generate a set of nested lists (ul’s), so any style rules need to address that hierarchy. For example:

ul ul li {…}

Will address list items that are inside a ul that is itself inside a ul. You may need to get more specific since this will also target list items that are more deeply nested than the rule (on the face of it) suggests, since list items that are 5 levels deep also satisfy the condition that they belong to a list that is inside a list.

But that’s the general direction to take.

The example you give though is also using javascript to achieve the visual effects, so exact duplication with css alone won’t be possible.

Cheers

Rob

Xue,

Can you be more specific… how are you calling the plugin?

I have tested it here on 2.3.1 and all is working as expected.

Need more info.

You can contact me via the email in the header of the plugin.

Regards

Rob

Hi,

Further upgrade to v2.02

Adds a case to handle the capture category of single post. In situations where the post in question is assigned to more than one category Fold Category List will use first returned category as the basis for building an appropriate folded category navigation.

Convention in WP is to not have category navigation on ‘single-post’ pages and those pages are not called with reference to a category, just the post id/name. Trying to fold the category navigation without knowing the current category isn’t possible, and the current solution is a compromise at best, but will work in all cases where posts are only assigned to a single category.

Best regards

Rob

Hi,

For anyone looking I have now rolled Justin’s mods into an ‘official’ release of Fold Page List, and extended beyond them to support some of the new arguments and default sort that are in the latest versions of WP.

This new version remains compatible with previous WP versions of WP as well, so no need to maintain two different versions of the plugin.

Get the new version from the Fold Category List Support page.

Cheers

Rob

Hi,

The problem with the above code fragment is that it only handles the case children of the current page or children of its parent… If the page list you are trying to generate is more than one generation above the current page, then it simply won’t work.

The Fold Page List plugin includes an internal function (_wswwpx_page_get_ancestor_ids) to return the entire ancestral tree as an array, from the root of the site to the current page (the order can also be reversed), allowing you to always get the id for any page ancestor. Simply feed it the id of the current page, and then select the id you need from the output array to get the navigation you require. For example, if $pageID is the current page located at the 4th level, then its grand-parent will be at the second position in the array of ancestors.

$ancestors = _wswwpx_page_get_ancestor_ids($pageID);
$grandParent = $ancestors[1];
wswwpx_fold_page_list("title_li=&child_of=".$grandParent);

Should do the trick.

Cheers

Rob

Hi,

From the plugin’s documentation page:

It is recommended however that at least the “hide_empty=0” option be set since without this any categories that lie below an empty category will not be shown

Let me know if this fixes problems of categories disappearing… Note also that there is an email address in the header of the plugin that will usually result in faster support than issues posted in the support forum…

Best regards

Rob

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

Hi,

Version 1.12, applying a similar permanent fix for possible warning messages arising from array manipulation is now available from the above links.

No reports were received of warning messages being generated from this plugin, so the patch is applied here as a preventive ‘just in case’ manner.

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,

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

Due to some compatibility issues that surfaced after release of version 1.0, the Fold Category List plugin has just been bumped to v1.11. This fixes the known issues of compatibility and a couple of bugs.

While compatible with WP2.1, the plugin should also remain compatible with previous versions down to WP 1.5, bringing cumulative post counts to these earlier versions.

The links remain the same as above.

Best regards

Rob

Hi,

Fold Page List has been updated to version 1.6 as of 28 December, 2006. This is a feature enhancement, designed to stop FPL from folding the page hierarchy and to act like wp_list_pages.

This might seem strange, but if you wish to implement drop-down page navigation then the full page hierarchy has to be both fully present in the html, and fully styled.

FPL provides the full styling necessary to do this, and can now optionally provide the full page hierachy. The drop-down functionality needs to be addressed in your stylesheet.

Installation guide and download link are available from the Fold Page List plugin support page. More details and links to some examples are planned to follow shortly.

Best regards

Rob