• Resolved abitofmind

    (@abitofmind)


    Can this plugin “Menu In Post” be considered obsolete in a Gutenberg only working environment?

    Or does “Menu In Post” have any extra features that are not possible with the native Gutenberg navigation block?

    Thanks for infos.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author linux4me2

    (@linux4me2)

    When I first heard about the Gutenberg Navigation Block, I was hoping it would make Menu In Post obsolete, but I don’t think there is a definitive answer. Yet.

    As far as I know, the Navigation Block creates menus as an unordered list of links, and can collapse them for a mobile menu, but it doesn’t (yet) give you the option of creating the menu as a select element; i.e., a drop-down, which Menu In Post will optionally do. (You can set the menu to display either as a list of links or a drop-down select.)

    While it’s possible to convert an unordered list of links like the Navigation Block creates into what appears to be a drop-down menu with CSS, it would be extra work, so I guess if you’re determined to have a drop-down select element, and don’t mind adding an additional plugin to do it easily, then Menu In Post would still be the way to go.

    Personally, I always prefer to accomplish things with native elements like the Gutenberg Navigation Block instead of using a plugin, so I recommend trying to make the Gutenberg Navigation Block meet your needs.

    Thread Starter abitofmind

    (@abitofmind)

    Thanks for your infos! What I take from it:

    – Gutenberg Navigation block is the preferred way for a navigation menu rendered somewhere inline (=within the pageflow). Through CSS an unordered list of links can be transformed practically into any kind of visual menu representation (dropdown, flyout, etc). The Gutenberg navigation block already offers quite some formatting options, and may even extend these over time.

    – In case you need a navigation menu rendered somewhere within the pageflow truly as a HTML <select> element (a.k.a. “dropdown menu”) then “Menu in Post” is the way to go.

    Plugin Author linux4me2

    (@linux4me2)

    Hi @abitofmind,

    Yes, that’s the way I understand it.

    As you mention, the Navigation Block already offers a lot of features, and more may be added.

    Thread Starter abitofmind

    (@abitofmind)

    Note that in some other native Blocks you can set which semantic HTML to use for that block.

    E.g. Select a Group block > Inspector > Advanced > HTML Element > You can choose: div, section, article , etc.

    Maybe the navigation block will one day also offer a choice for its representative HTML element, and <select> may be among the choices.

    Plugin Author linux4me2

    (@linux4me2)

    That would be good. I wouldn’t mind being off the hook for maintaining this plugin.

    PLEASE @linux4me2 don’t stop to support this plugin. There are some people (like me) who refuse to use Gutenberg (look at the reviews…).
    I love your plugin and I still use it. THANKS!

    Plugin Author linux4me2

    (@linux4me2)

    Hi @brisch, it’s really nice to hear that you love my plugin. If WordPress drops the classic menu system, which Menu In Post relies on, supporting it would be difficult, but for now, I am continuing to keep it updated.

    I recently added the capability to bring the classic menu system menu entry back to the Appearance menu when using a block-based theme that hides it, and yesterday I released a version with some PHP 8.2-compatibility fixes, so I have not given up on it yet.

    Thanks! ?????? ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Menu In Post plugin obsoleted by Gutenberg navigation block ?’ is closed to new replies.