wlindley

Two widgets are provided, for displaying a vastly condensed 
hierarchial list either of pages, or of categories and custom 
taxonomies. Designed for large sites with hundreds of pages, or when 
using custom post types or custom hierarchical taxonomies.
With Pages: Always displays the current page, the pages above it back 
to the home page, and the current page’s children. Detects nested 
categories and custom taxonomies, and likewise displays the categories 
or taxonomies above and below the currently displayed one.
The behavior of the widget is all configurable through its 
configuration screen, as follows:
<ul>
<li>The Categories widget will also display custom taxonomies. 
The admin screen includes a list of the defined ones; 
leave the field blank to use the built-in post categories.</li>
<li>The title is optional (blank will emit no heading); with 
a blank heading and top-level entries (pages/categories/ 
taxonomies) disabled, you can have the widget only display 
when the user is “currently inside” a page/post that matches 
what the widget is set to display.</li>
<li>Pages may be sorted in Menu Order or alphabetically. 
To sort pages in menu order, with pages of the same order 
alphabetical, set the Sort Field parameter to: 
menu_order,post_title … some sites have reported issues 
and seem to require that only menu_order be specified.</li>
<li>Categories and custom taxonomies may be sorted by name, 
slug, or other fields displayed on the admin form.</li>
<li>Sort order can be ASC or DESC</li>
<li>Siblings to the current page, if enabled, means that child 
pages of the current page’s parent will be displayed. 
Disabling this makes for shorter page lists but the user 
might not be able to move “sideways” in the site.</li>
<li>If there are many top-level pages (pages with no Parent set), 
you can disable their listing.</li>
<li>If your site has an Introduction or splash page, as a static home 
page, you might want to disable showing it (presumably it is 
accessible through an icon link). However, if the homepage has 
children, it will always be displayed (otherwise you could never 
navigate to those pages).</li>
<li>For Pages, you may optionally specify a meta-key and value 
which must be matched for pages to be listed in the widget.</li>
<li>Also for Pages, you may select posts that match a given 
Author or post status. Leave these blank for “all authors” 
and “publish” status.</li>
<li>Empty categories/taxonomies may be hidden.</li>
<li>Both plugins permit specifying either an include list or 
an exclude list. These are comma-delimited lists of 
ID numbers. You may specify either include or exclude, not both.</li>
</ul>
Spanish translation provided courtesy Andrew Kurtis of WebHostingHub.com 
Thanks, Andrew!

Hierarchical Pages Widget

Two widgets are provided, for displaying a vastly condensed

Frank Neumann-Staude

Torsten Landsiedel

Drivingralle

Hinnerk Altenburg

Caspar Hübinger

Ralf Koller

Child Themes are used to avoid overwriting your customizations. But if you preserve a file in a child theme, then you maybe preserve a security risk. After an update from the parent theme you always should check the changes and maybe add them to your child theme. This plugin helps you keeping track of these changes in the parent theme.
For full usage of the plugin your parent theme has to define the version of the template file in the header of the PHP file with an additional @version info.
For example: <code>@version 1.0.0</code>
If this is the case you will see a warning if the version of the parent theme file is higher than your child theme file. And you can see the differences between the parent theme file and the child theme file per wp_text_diff()-function like in revisions.
Some posts about this plugin:
<ul>
<li><a href="https://krautpress.de/2016/child-theme-dilemma/" rel="nofollow ugc">KrautPress</a> (German)</li>
<li><a href="https://wptavern.com/child-theme-check-plugin-helps-wordpress-users-navigate-parent-theme-updates" rel="nofollow ugc">WP Tavern</a> (English)</li>
<li><a href="http://www.elmastudio.de/en/wordpress-plugins-child-theme-check/" rel="nofollow ugc">Elmastudio</a> (English)</li>
<li><a href="http://www.elmastudio.de/wordpress-plugin-tipp-child-theme-check/" rel="nofollow ugc">Elmastudio</a> (German)</li>
</ul>
These themes from <a href="http://www.elmastudio.de/en/" rel="nofollow ugc">Elmastudio</a> are already using the @version info in the header:
<ul>
<li>Uku</li>
<li>Uku Light</li>
<li>Weta</li>
<li>Pukeko</li>
<li>Zeitreise</li>
<li>Werkstatt</li>
<li>Neubau</li>
<li>Hawea</li>
</ul>
Please spread the word and if you are a theme developer, please add this to your themes too! Thanks 🙂

Child Theme Check

Just found it, great tool, thanks for sharing



Wow! great tool

I was bored to verify if my child themes were up to date and this plugin is a great tool to see in a glimps if you have to rework your child theme.



Great tool

This tool have been really helpful for me. Thanks a lot!



Very helpful

Thank you Thorsten et.al for this very useful plugin. I think it's a fantastic idea to check for a version header and this plugin is a good reminder of developing with a useful standard.



Does what it is supposed to

Warns you about outdated template files in your child theme and shows a diff view of the changes between parent and child theme template.

Hierarchical Pages Widget vs Child Theme Check