In the menu editor, you have several different choices for items that you can insert into the menu. For example, you can insert "custom links", "pages", "categories", etc (pages being the most common). I propose that there be a new option to allow you to insert a reference to another menu. For example, if I create 2 menus: Menu A and Menu B, it would be nice if you could insert a reference to Menu B from anywhere inside Menu A.

As wp_nav_menu() loops through each item in the menu to compile an unordered list to return, it should check if the item is a menu reference, and if so it should make a recursive call to itself to return the referenced menu in that location.

If you have any questions or need further explanation, feel free to ask. Thanks!

[redacted]

Thanks,

Jason

As far as inserting HTML tables, I only use them to display data in tableture formats. I use Notepad to get the table formatting write and paste it into my post using the HTML view of the editor.

If they can come up with a better editor then great... I'll use it. But I, for one, have not needed to do anything with TinyMCE that I couldn't do using either the Visual or HTML view of the editor.

Tommy
Social Media Marketing

Hope you understand me and sorry for my english i am from germany

Best regards

Hidden pages contain content that should not be widely promoted in the usual traffic source channels like search engines and social media. A hidden page's content is accessible to any visitor who knows the URL, but there are no automatic links to it on the site itself or in the sitemap, and the site owner does not want to publicise the page on the Internet generally.

Typical uses for a hidden page are:
- Bonus promotions in advertising literature: "For a special bonus offer, visit site.com/bonusoffer"
- Marketing promotions on business cards and in audio files.
- Any time you want to make a page with non-sensitive content easily accessible, but not widely promoted

A hidden page differs from the existing page visibilities like this:
- Public: A hidden page isn't widely advertised. They don't get added automatically to menus even if that option is selected, but they can still be included in menus manually.

- Private: A hidden page's content is accessible to anyone who knows the URL, regardless of their authorisation level.

- Password Protected: A hidden page requires no password to access.

Hidden pages should be marked "noindex", but this alone isn't sufficient. This needs to be a core feature, because many existing plugins can use this information about a page, and a standard mechanism for specifying it is required. Most of the decisions treating public and hidden pages differently occur in plugins that advertise pages to the outside world.

Plugins should treat hidden pages as follows:
- Site Map plugins would not list the page in the XML or human readable sitemap.
- SEO/Robots Meta plugins would mark hidden pages "noindex" by default so they don't get indexed
- Social Network integration plugins would not automatically publish hidden page references to social networks
- Social Network bookmarking plugins would not generate bookmarking features for hidden pages
- Facebook Like plugins would not add a Like button to hidden pages.
- Automatic cross-linking plugins like SEO Smart Links would not generate links to them.
- Etc

Hidden pages offer a weak but nonetheless useful level of security. The content of a hidden page should not be damaging if publicly released. Nothing stops a visitor from publishing a hidden page's URL on the Internet once they know what it is. The idea is to stop WordPress and it's plugins from promoting them automatically, and to discourage visitors from promoting by trivial actions.