@pers– Conditionals are currently getting a rewrite. Your code will work afterwards.  Unfortunately, it’s taking a bit longer than we wanted.

@anderly– This definitely looks interesting.  Instead of changing the core Piklist code you can create a plugin that adds your new field.  Check out this forums posts from users that have created their own fields:

http://piklist.com/support/topic/new-field-type-switch/
http://piklist.com/support/topic/field-type-slider/

@pers– Just a little trick.  If you want to keep all your lists absolutely the same, you can define the array first:

$choices = array(
'option1' => 'Document Title'
, 'option2' => 'Site URL'
, 'option3' => 'Site Title'
, 'option4' => 'Page number'
);


And then include $choices in the field array:

'choices' => $choices


Makes it easier to manage all three lists.

That’s the first time we’ve heard of this issue.  Can you try another browser and let us know if you still get the error?

I still don’t 100% understsand… but here’s an idea:

-Create a generic Top Level menu that has no content (we do this with Piklist).

• When admin’s log in, the CPT will be the first item in the Top Level.
• When non-admin’s log in, the other page will be the first.

Thoughts?

@ahrale– Look higher in the menu.  It should be located under the APPEARANCE menu.

@johnmcalester– This is definitely something on our list. But until we put it together, this is how we would do it.

@johnmcalester– Glad we could help.  Wrote the tutorial here.

Also HTML has the readonly attribute, just not as flexible as on_post_status.  But this would work:


,'attributes' => array(
'class' => 'small-text'
,'readonly' => 'readonly'
)