This is fixed in the upcoming release later today.

Thanks,

Kevin

@tuckerjoenz

Of course 🙂 You will have to move your content from the post meta field to the post_content for anything already created, however for the field you just need to specify the scope and change the field name like so…

piklist('field', array(
  'type' => 'editor'
  ,'scope' => 'post'
  ,'field' => 'post_content'
  ,'label' => 'Add Story'
  ,'description' => 'Stories of Impact'
  ,'options' => array (
    'media_buttons' => true
    ,'teeny' => true
    ,'textarea_rows' => 5
    ,'drag_drop_upload' => true
  )
));

@tuckerjoenz-

Thats a odd one 🙂 You have two problems with the code you posted.

1. Remove add_action( ‘save_post’, ‘partners_post_type’ ); from functions.php, you just need add_filter(‘piklist_post_types’, ‘partners_post_type’); to register a new post type.
2. All of your fields have the same name so you are saving all of the data to one field (‘field’ => ‘text_class_regular’) and then when they render each field pulls that data and displays it, making it appear that it saved multiple times. Always make sure to give unique names to all fields.

@jason-

Thanks for the field information, I will see what we can do. Really its only serialized groups that have this issue and its not all of the time, it depends on the new field being added (we actually improved support for this in 0.9.4). While we consider this an edge case we will of course make every effort in the next release or so to see if we can make this even better.

Thanks

Kevin

@diegoliv-

First, thanks for the email, we will get back to you on the other items soon. As for your question, of course 🙂

So we include server side validation because its more secure and reliable, however you can add any client side improvements pretty easily. When defining the field just assign and classes or data attributes in the attributes parameter and you can use those to target those fields for the library of your choice. If you have one in mind and would like us to help you get started just let us know, we are here to help.

Thanks,

Kevin

PS We have already had users use this method to make select fields use the Chzn dropdowns and it was pretty easy.

@bicho44

What are the core features for such a field and how should they work. This would be a great place to get that discussion rolling. What kinds of things do you feel are necessary for such a field?

On a related note, in the coming weeks we will start to show people how to create their own fields easily with Piklist so stay tuned!

Thanks,

Kevin

@ianmuscot

You are so close 🙂 In your plugin folder create a parts directory and meta-boxes inside of that for your meta boxes. So to be clear, if your plugin is named piklist-test and your meta box file is named meta-box-test.php the path should be

piklist-test/parts/meta-boxes/meta-box-test.php

Let us know how it goes.

Thanks,

Kevin

PS On your field definition the position attribute is rarely needed as the system handles it for you.