scotcrop

For a possible solution for redirects on woocommerce login/registration forms see

https://github.com/woothemes/woocommerce/commit/014e31952828377bf7a1ebf4e812a43d0bcefa67#commitcomment-3351995

Adding the hidden input ‘redirect’ approach works on the login form but not the registration form. However, you can now use a filter. See

https://github.com/woothemes/woocommerce/commit/014e31952828377bf7a1ebf4e812a43d0bcefa67#commitcomment-3351995

For doing this on registration see

https://github.com/woothemes/woocommerce/commit/014e31952828377bf7a1ebf4e812a43d0bcefa67#commitcomment-3351995

Create a home.php, front-page.php or index.php template with the graphic and map tag code. Providing a regular menu at the top or side would be helpful but if thats not an option just follow the proper syntax for the map tag:

https://www.w3schools.com/html5/tag_map.asp

Just be descriptive in the alt tags to help with SEO etc.

Submitted a ticket

https://core.trac.www.ads-software.com/ticket/16936

Not sure if this is expected behavior or not. I could see one use for it, when displaying a category/tag post list being able to easily grab a corresponding menu if one exists. However, that seems more handy than a common need.

I can confirm that this is an issue and a disturbing one. It basically boils down to the slug. On menus you can’t specify a slug. If you happen to create a menu with the title that matches a slug it gets the same id in the database. Later if you change the tag or menu title they both change. This can cause problems if you are asking for a menu by name or have links to /tag/tag-name. I don’t believe naming your menus some unorthodox name should be a requirement. Categories can get in the mix as well if you name a menu the same as a category slug and then rename either. Seems the menu creation isn’t creating its own taxonomy record to set itself a part from existing tags or categories.