Parent:
1. shows the previous link ("Static Tab") -top link ("Parent static page") and next link ("Child static page") navigation block. The "top" link is useless - it is a link to the current static page I am already on. These others look somewhat related, but the "previous" and "next" links don't always relate to one another... they just happen to be the previous and next static pages in the list of all static pages. I consider this block nearly worthless and usually have it disabled. I noticed that 2k11 does not bother to include the code - even if enabled it will not show.
2 shows the bread crumb. Breadcrumbs are more valuable than the navigation block above, especially when using parent/child/dependent static pages. I don't like this for three reasons: 1) There is no "home" link. 2) The only link for this first level static page is the static page title itself. Why do I need a hyperlink to a page I am already on? I realize the static page headline is also a hyperlink, but I think that may have been done more for visual reasons. 3) There is no way to enable/disable the breadcrumb navigation without enabling or disabling the previous/top/next navigation. Can we get another smarty variable for showing breadcrumbs, like maybe $staticpage_showbreadcrumb ?? I have my own improvement for displaying the breadcrumb, and will show that below.
3. shows child pages. This parent static page only has one child, and that is correctly shown. This would be far more valuable if it also showed nested dependents (ie, grandchildren, great grandchildren....
Child:
1. In the parent static page above, the "top" link showed the static page title, and pointed to the static page url. In this first level child, it uses the text "TOP" and points to the base URL. I have no idea why. Although this is my first level "child", it is possible I created this static page before all others, and when the function is looking for the prior static page, it finds none???
My complaints for 2 & 3 are the same as above.
Grandchild:
1.Here the "top" link isn't this static page's parent, it is the grandparent "Parent Static Page".
Great grandchild:
1.As above, the "top" link isn't this static page's parent, it is the great-grandparent "Parent Static Page".
I find this breadcrumb code to be more useful:
Code: Select all
<a href="{$serendipityBaseURL}">{$CONST.HOME|lower|capitalize:true}</a> »
{foreach name="crumbs" from=$staticpage_navigation.crumbs item="crumb"}
{if !$smarty.foreach.crumbs.first}» {/if}{if !$smarty.foreach.crumbs.last}<a href="{$crumb.link}">{$crumb.name|@escape}</a>{else}{$crumb.name|@escape}{/if}
{/foreach}
In summary:
1) I find the previous/top/next navigation to be virtually worthless. It is disabled by default, and perhaps it works for some people. Not sure if I advocate complete removal, but does anyone have suggestions for how to improve it? Instead of a previous/top/next, how about showing a dropdown box of all static pages, much like when selecting a static page in the backend for editing?
2) I would like an option to enable/disable the breadcrumb separate from the prev/top/next navigation. I can probably figure out the code myself or if someone else wants to jump on it first go right ahead.
3) I think my suggested breadcrumb code works better: It adds a "home" link which points to the baseURL, and does not make the current static page title a link. I would like to add this to the plugin's smarty template(s), and I can add it to bulletproof. YL can choose whether to add it to 2k11 as that template does not currently use bread crumb navigation.
4) When showing child pages, would it be possible to also show further nested/"grandchildren" pages?
5) In the previous/top/next navigation box, the "top" link seems to always point to the first level static page. Is this operating as expected? If so, then nothing needs to change.
6) Sorry for the long-winded rant!!!