Having trouble seeing output

Create 2 instances of the widget : leave the first one set to Show All and just change to the appropriate menu (if you have more than one); leave all other settings at their default. This instance is the Control.

The second instance is your Test widget, and set it up (for the same menu) however you want … specific items, or children of, whatever, and Save it (you don’t have to close either widget or the “assist”). In the “assist” for that instance, click on an appropriate menu item to make it the current menu item, and check that the assist shows the output you would expect if you were actually on that page.

Open up the frontend of your site in another browser tab and check that (at least) the Control is visible. Using the Control widget, navigate to the same page that you have set in the Test instance’s “assist” : if the “assist” shows some output then you should see the same output in the Test widget at the frontend. If you don’t then there’s a problem.

Can you paste the shortcode shown by the widget into this thread (after having Saved the settings!) so that I can see which options you have set?

Ahh, this is helpful. I take back what I said about “Show All” works as specified; I only see it list the top level menu items, but none of the subitems. This means that I can’t directly follow your suggestion: I can’t navigate to my subitems via the control widget, since they’re not appearing there. I could navigate there via the menus that my theme provides, but I’m not sure if that would get you the information you want. Would it?

(and thanks for the quick response, much appreciated)

The shortcode (for the Show All that only shows 1 level) looks like … ?

[ copy – paste it from the bottom of the “assist” ]

[custom_menu_wizard menu=3 title=”Control”]

If you view the source of your frontend page, and find the Control widget : is the HTML only listing the top level items? Or are the sub-level items actually there but they are just not visible?

The reason for asking is that if the menu has sub-levels, and you can see them in the “assist”, and you’re running Show All with everything else set to the default (which you are), then there is absolutely no reason why the sub-levels items would not be produced by the frontend widget unless either something else is removing them, or they are there but are not visible due to some CSS styling.
One check for something else removing them is to compare CMW’s Show All output with the output of WordPress’s own Custom Menu widget – they should show exactly the same items.

Alas, they aren’t present in the HTML — just checked via a view source.

I also just tried WordPress standard Custom Menu widget: it _does_ show the subitems.

Feel free to see for yourself, if you like:

https://oremet.org/wp/news/

Any suggestions on how I’d go about looking to see if something is removing them?

Hi vultan.
If it sounded like I was doubting what you were telling, then that wasn’t my intention and I apologise. It’s just extremely frustrating when I can’t reproduce a problem, or properly investigate what might be happening.
If you wouldn’t mind helping me out by giving me temporary access to your backend, maybe we could continue this conversation by email – [email protected] ? Ideally what I’d first like to do is simply dump $elements and $args out of custom_menu_wizard.php (immediately after $args = $args[0]; in the walk() function) [var_dump($elements,$args);].
I’m sorry I can’t be of more immediate help, but it’s got me stumped at the moment.

Hi wizzud –

Thanks for the offer to help; I’m obviously a bit skittish about having someone walk into our site, but I really appreciate the offer. I tried to do some more debugging on my own today, but I’m going to move on… got my day job to be concerned about too. ??

I completely understand.
If you could spare a couple more minutes though, you might consider doing me a big favour and testing CMW (a simple Show All setting) against Custom Menu widget in WordPress’s own Twenty Fourteen theme, please?
You can switch between Twenty Fourteen and your Micah theme without losing any data or settings, and you just need to add the 2 widgets (assuming you still have CMW installed, which you may not by now!) to 2014’s primary sidebar, look at the frontend, remove the widgets, and switch back to Micah. If the 2 widgets produce the same output then it’s the Micah theme that is getting in the way of CMW. If they still don’t then would you give me a list of any other plugins you are using, so I can continue testing for myself?
I’m sorry you’ve had these problems, but I would like to determine what isn’t working and why, and I sincerely appreciate any assistance you can provide this one last time.

It’s definitely Micah. Just verified it on a local install. Well, that’s a bummer. It’s causing menu widget problems not just with your plugin, but with other similar ones as well.

Guess I’ll contact them, or just move on. Thanks so much for your help and direction.

Hi vultan.
Thanks for letting me know. It’s a relief for me, but I appreciate that it’s probably a pain in the proverbial for you! I’m extremely grateful for your assistance and perseverance in getting to the root of the problem, and I wish you luck. I’ll mark this as Resolved, but if you do decide to contact the Micah theme authors, I’d still be curious to hear the outcome.

I found the bug in Micah on my own. Definitely not your problem! Thanks for pushing me and getting me obsessed, though I need to get back to sleep.

They had this code right before displaying the main navigation menu:

add_filter( ‘wp_nav_menu_objects’, create_function( ‘$menu’, ‘return array_reverse( $menu );’ ) );

That’s because they were floating their

• right, which reversed the order of the menu, which they then “fixed” after the fact via the above. Removing the above PHP code fixes the issues with CMW. Of course, I’ve now got to figure out the associated layout problems. ??

If there’s good news here, I’ve learned a bunch about WordPress.