I would like to verify if Classic Menu Block is compatible with PHP 8.2. If not, do you have a timeframe when the plugin will be tested and released with 8.2 compatibility?

Great plugin for what it is – as a wrapper for the classic menu insert fn wp_nav_menu(), and so to be able to insert a classic menu into a full block theme. ?BUT ?….??

• The documentation is totally absent for who this plugin is for, how you use it , whats the prerequisites ???.. So the plugin provides a block to insert a classic menu? …So I assume you can insert a classic menu into a website which is using a Block theme. But if I simply start with block theme 2024, install and activate the plugin, then I don’t get in the Backend the menu item ‘Menus’? under Appearance? … so I cannot first setup/create a classic menu ….

• But then I realised if you? include the function register_nav_menus() in an action hook in the theme, then I get the MI ‘Menus’? –?

function register_my_menu() {

   register_nav_menus();         

}

add_action( ‘after_setup_theme’, ‘register_my_menu’ );

So now I can create a classic menu in the Backend, insert a Classic Menu block  in a page and select a classic menu for that  block insert. So for example, theme 2024 has no such register fn, so I  added it to  a child theme   

• And then to the styling?? ….?? The plugin? comes with some simple menu styling? – that’s ?OK, at least its something? … But? if you want to do? your own styling the Spacemonkey article mentions? a filter? .. but its not clear? what it’s for / how? you? use it? …?? But after looking in the code of the plugin? top file ?classic-menu-block.php, ?you? can use the filter? to change the? params? which ?in the plugin are then passed to the classic menu insert function ?wp_nav_menu() .?? So? I? used this to change the class neme of the outer? wrapper div of the inserted menu from the default to my own? …? as such I could remove the default styling, and style the menu as I? want without the need for !important or mega specificity. ???

• So in conclusion it would be useful to simply add this info? in the diocumentation ???….?

• A comment on improving the default styling / adding styling config ?(there isn’t any config at the moment)? …? I don’t know how far this should go? … simply because there would be so many? possibilities ?to? suite each person’s needs so the whole thing becomes totally overweight? … ??I think its best as is? –? the simple current? styling – at least ?it works for the? non-dev, but? with the filter? a developer can do? their own styling.

Hi!

The default behaviour of dropdown links is on “hover”. Is there a way to change it to “on click”?

Does your block allow use of a custom nav-walker class? I have a theme based on w3.css with a nav-walker class to create w3.css based menus, and I am creating a w3.css block theme based on that theme. But I want the w3.css nav menu in it. But there is no doc on how to use nav-walker classes with the new block menu nav. So I’m hoping I can customise your block or that your block provides customisation.

Hi there,

here is detailed issue that appears in conjunction with WooCommerce: https://github.com/woocommerce/woocommerce/issues/44170

I just translated the text strings of the plugin into German. As for some reason the translation of the plugin doesn’t seem to work as expected, I tried to look into the code if I could spot any issues, but had issues reading the code in directory build and couldn’t find any source files within in the plugin.

Accordind to the plugin handbook …

Obscuring code by hiding it with techniques or systems similar to p,a,c,k,e,r‘s obfuscate feature, uglify’s mangle, or unclear naming conventions such as $z12sdf813d, is not permitted in the directory. Making code non-human readable forces future developers to face an unnecessary hurdle, as well as being a common vector for hidden, malicious code.

source: Plugin Handbook

May I suggest that you either include the source-files in the plugin or (probably more helpful as it would include the package.json-file, too) mention your GitHub repo https://github.com/spacedmonkey/classic-menu-bloc in the readme file of the plugin?

Best regards, Bego

Localhost Xampp on Windows 10, php 7.4.x, WP 5.9, Chrome.

After installing and activating the plugin the Legacy (Classic) Menu block is nowhere to be found, telling me that somehow the plugin fails to even register it to begin with:

BTW, thanks for this, as this is very needed. Looking forward for a fix, so I can give it 5 stars…

Thanks,
Nick.