Support » Plugin: OptionTree » [Plugin: OptionTree] Bug? capability manage_options vs edit_theme_options

  • Resolved chocks


    Hi guys, thanks for this plugin, it’s awesome!

    I’m wondering if this was intentional or not.. I wanted to give the editor permission to access the Theme Options and updated the role to edit_theme_options, this didn’t work (although I believe this cap is intended to allow these kind of settings) so I added manage_options (which.. ok, seems similar). The last capability worked and now the editor is able to see the menu Appearance -> Theme Options, yet he can also edit the OptionTree settings! Can we have different capabilities for one section and the other? This would give us a lot more flexibility to let other users modify settings in a multisite environment for instance.

    Or if you want to make it super simple for everyone you could may be include a sub menu in settings with the current Roles and have a ‘minimum’ level user such as Administrator, Editor, Contributor, etc.

    Thanks again!


Viewing 1 replies (of 1 total)
  • Plugin Author Derek Herman


    In version 2.0.10 the capabilities are set to edit_theme_options as others thought it was the correct capability to use, which I don’t disagree with for the theme options page but the settings page could have been argued either way and after reading your request I’m leaning towards separate capabilities. I think I’ll be reverting my change to the settings page in the next release.

    We can certainly discuss some of your other requests but ultimately my goal is to give you as much as possible without going overboard. Altering capabilities from within OT seems kind of drastic in that regard, but that’s just my opinion.

Viewing 1 replies (of 1 total)
  • The topic ‘[Plugin: OptionTree] Bug? capability manage_options vs edit_theme_options’ is closed to new replies.