Megamenu block no longer sees template parts

[tomfinitely]

As of 6.7.1 (haven't tested lower versions) the Megamenu block doesn't see relevant template parts including any that have already been associated with the block.

Note: I don't see any console errors, and also haven't had sufficient opportunity to disable plugins and/or enable debugging output.

EDIT: the only logged error that I can find that might be indicative of the issue is:

[28-Nov-2024 23:04:17 UTC] PHP Warning: Attempt to read property "ID" on null in /Users/me/Local Sites/mysite/app/public/wp-includes/rest-api/endpoints/class-wp-rest-autosaves-controller.php on line 167

[ndiego]

Thanks for reporting @tomfinitely. I just tested in 6.7.1, with and without Gutenberg active, and I am seeing the menu template parts in the block. Any additional info you can share?

[bmx269]

I too am finding a strange error here. I create templates for menus, and unless I add the template to the menu category in the theme.json, they get put into the General category, but only after I save the changes to the theme with Create Block Theme.

I have not had time to debug.

To keep that menu working on deploy, I have to add them manually like this example:

theme.json

"templateParts": [
		{
			"area": "header",
			"name": "header",
			"title": "Header"
		},
		{
			"area": "footer",
			"name": "footer",
			"title": "Footer"
		},
		{
			"area": "menu",
			"name": "about-mega-menu",
			"title": "About Mega Menu"
		}
	],

[ndiego]

I too am finding a strange error here. I create templates for menus, and unless I add the template to the menu category in the theme.json, they get put into the General category, but only after I save the changes to the theme with Create Block Theme.

The Create Block Theme plugin does not support custom template part areas (in this case, menu), which is why they end up in the General category. The manual step is expected.

[bmx269]

Good to know.