124 reputation
113
bio website
location
age
visits member for 1 year, 11 months
seen Aug 6 at 15:56

Oct
22
awarded  Notable Question
Oct
10
awarded  Popular Question
Jul
2
awarded  Curious
Mar
9
comment Registering custom post type menu editor problem
No, only register post type first argument. But in database it seems somehow 3.8.1 puts into hidden custom post types. Bug is reported to core as it looks like non user friendly solution. Same problem happens when you update. But to give you a hint about the solution - custom post type do not disappear cpempletly - it is hidden in "screen options" somehow.
Mar
9
comment Registering custom post type menu editor problem
Digged even a little more... It looks like some strange bug, or perhaps it's in purpose - if the custom post type menu entires are invisible - they are hidden in screen options for that user. It seems WP somehow hides it when it is added in wrong moment or after updating to 3.8.1 what was a problem in my case.
Mar
9
revised Registering custom post type menu editor problem
added 574 characters in body
Mar
9
asked Registering custom post type menu editor problem
Nov
17
comment Custom wp_nav_menu output (displaying all child elements of top menu element in current branch)
Seems I was able to solve it by connecting your method with one pointed in comments to original post. I have edited original message and posted working solution. Still - without your help I wouldn't have a working solution ;)
Nov
17
revised Custom wp_nav_menu output (displaying all child elements of top menu element in current branch)
added 2083 characters in body
Nov
14
comment Custom wp_nav_menu output (displaying all child elements of top menu element in current branch)
have you been able to find a monute or two?
Nov
12
revised Custom wp_nav_menu output (displaying all child elements of top menu element in current branch)
added 29 characters in body
Nov
12
comment Custom wp_nav_menu output (displaying all child elements of top menu element in current branch)
No problem. From analytical point of view script should detect 2 cases: 1. Current item is 1rst (main) level item (menu_item_parent==0) and has child elements - then it should collect all child elements and display their structured code (starting from menu 2 level elements that are children of this top level element) 2. If element is not 1rst level element (menu_item_parent!=0), then it should find its top parent element, and again - collect all child elements of that parent element and print them hierarchically.
Nov
12
comment Custom wp_nav_menu output (displaying all child elements of top menu element in current branch)
The biggest problem that I see now - is that 1rst level elements are shown by our custom menu - and the menu should show nothing when 1rst level element has no child elements, and should show all child elements (hierarchically structured) when it has child elements (it should show children but parent should not be visible).
Nov
12
comment Custom wp_nav_menu output (displaying all child elements of top menu element in current branch)
Now the tricky part happens when we talk about 3 level menu. When active site is a parent of submenus, $tree holds only its child elements. When one of them has another child - item is not listed (perhaps its correct). When second level element is active - than all second and third level elements goes to $tree. Same when third level element is selected.
Nov
12
comment Custom wp_nav_menu output (displaying all child elements of top menu element in current branch)
Yes, Im going through every step and already when in function gmfnv_filter, there is a $parents array that holds all first level elements - and they should never get back from filter as allowed - just because if current page is top level element - our custom menu should return nothing, Now $tree seems to collect data correctly (at least when menu has 2 levels) but then is merged back to parents - and that returns original structure as long as menu has 2 levels.
Nov
12
comment Custom wp_nav_menu output (displaying all child elements of top menu element in current branch)
Hmm... Somehow after few days of break code don't work anymore :/. And as I cant seem to understand the code completely - I don't know where the problem lies :(
Nov
5
accepted Using post ID in custom tinyMCE button
Nov
5
comment Using post ID in custom tinyMCE button
Yes, in 3.7 for sure :)
Nov
4
comment Using post ID in custom tinyMCE button
hmm it seems that post_id is available just after opening new post or new page - the ID is assigned right away and is available.
Nov
4
comment Using post ID in custom tinyMCE button
In other words - to be able to have the access also while creating new page/post - I would need to hook into autosave feature, get the ID from there and add to global variable? Is it even possible?