[wp-trac] [WordPress Trac] #18285: New Settings API and workflow

[WordPress Trac]

#18285: New Settings API and workflow
----------------------------+------------------
 Reporter:  nacin           |       Owner:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  3.3
Component:  Plugins         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by F J Kaiser):

 @WraithKenny +1 for template tags and template-able option pages. One imo
 important thing would be that those template tags could have an additional
 callback parameter to override their behavior (like if the callback would
 hook into a filter). Another thing I want to mention are "shared" option
 pages. In detail: In some cases you don't have hundreds of options and
 therefore you don't need 10 option pages, but only a single one - with
 let's say 15 options. Now 5 of those options are better off when they are
 only viewable by the developer and the other 10 are meant to get set by
 the owner/client who wants - of course - have an administrator account. If
 we would have a capability per field, we could use custom capabilities to
 show all fields only to the developer and the rest to the "public"
 majority. Sure, we can still do this in for example an options template,
 but having the capability check built in right into the field the process
 would be much more seamless.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/18285#comment:51>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software