Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Except we allow to edit the settings for each post type/taxonomy, what’s registered for what, as well as exporting to output that you can paste elsewhere if you want to move away from the plugin itself. We also store the intended settings in an option that we fetch when registering, so it’s not something saved to a separate theme or plugin file. There’s many reasons why we should not remove the menu item.

    Also if you’re a developer who knows what they’re doing, why do you need the plugin in the first place? Other than quick convenience? ??

    Thread Starter eduardoarandah

    (@eduardoarandah)

    You are right!

    I use your plugin a lot for many projects because it makes it easy to develop themes.

    However, when the project is ready, I export the code so the user don’t see the “complicated nerd stuff on the menu”

    That solves the problem, however, when the user asks for changes, It would be awesome to “unhide” the plugin, make the changes and hide it again so I don’t have to remember what was the settings at first.

    This is just a suggestion, the plugin does the job and I am thankful for it, great work!

    If you add an “editor” role account for the user, CPT UI (and also other settings) won’t be visible for them.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Remove menu shortcut’ is closed to new replies.