| bio | website | james.revillini.com |
|---|---|---|
| location | Winsted, CT | |
| age | 33 | |
| visits | member for | 1 year, 11 months |
| seen | Apr 11 at 15:15 | |
| stats | profile views | 4 |
|
Apr 16 |
awarded | Teacher |
|
Apr 16 |
answered | insufficient permissions; coding an action for plugin governed by custom capability |
|
Apr 13 |
comment |
insufficient permissions; coding an action for plugin governed by custom capability interestingly enough, the href of the admin bar link can go to pretty much any valid php page in the admin section. Originally it was options-general.php, but I've tried swapping it out for admin.php and post.php, and they work or don't work based on what capability I use for the capability when I run add_options_page (see previous comment). ... I still don't see the connection. |
|
Apr 13 |
comment |
insufficient permissions; coding an action for plugin governed by custom capability Here's the pertinent code. add_options_page( 'WP Super Cache', 'WP Super Cache', 'manage_options', 'wpsupercache', 'wp_cache_manager'); That manage_options bit is the capability that gets checked. If I change that up for the custom capability, I can run delete on the page for anyone with that capability, but it has the undesired consequence of letting the Editor into the super cache settings. I still need to learn how to change the code so I beat the capability check. Also, I don't fully understand why the capability for the options page affects running the action. |
|
Apr 13 |
asked | insufficient permissions; coding an action for plugin governed by custom capability |