WordPress.org
Get WordPress

Plugin Directory

Changeset 1336504


Ignore:
Timestamp:
01/26/2016 05:41:25 PM (10 years ago)
Author:
wizzud
Message:

tag 3.2.3

Location:
custom-menu-wizard/tags/3.2.3
Files:
1 edited
3 copied

Legend:

Unmodified
Added
Removed

  • custom-menu-wizard/tags/3.2.3/readme.txt

    r1272452 r1336504  
    44Tags: menu,widget,navigation,custom menu,partial menu,current item,current page,menu level,menu branch,menu shortcode,menu widget,advanced,enhanced
    55Requires at least: 3.6
    6 Tested up to: 4.3.1
    7 Stable tag: 3.2.2
     6Tested up to: 4.4
     7Stable tag: 3.2.3
    88License: GPLv2 or Later
    99
    … …  
    289289It only comes into play (possibly) when a `Branch` filter is set as "Current Item", and the `Starting at`
    290290and `For Depth` settings are such that the output should start at or below the current item,
    291 and would normally include some of the current item's descendants (eg. `Starting at` "the Branch",
    292 `For Depth` "1 level" does *not* invoke the fallback).
     291and would normally include some of the current item's descendants
     292(eg. `Starting at` "the Branch", `For Depth` "1 level" does *not* invoke the fallback).
    293293The fallback allows for the occasion when the current menu item *does not have* any immediate children.
    294294
    … …  
    876876
    877877== Changelog ==
     878
     879= 3.2.3 =
     880* tweak : minor updates to documentation, and verified for WordPress v4.4
    878881
    879882= 3.2.2 =
    … …  
    10331036== Upgrade Notice ==
    10341037
     1038= 3.2.3 =
     1039Tweaked documentation and verified for WordPress v4.4
     1040
    10351041= 3.2.2 =
    10361042Fixed a bug on the very first rendering of a newly added widget via the customizer, where the widget output rendered in legacy mode until an option got changed or the widget was saved.
Note: See TracChangeset for help on using the changeset viewer.