Forum Replies Created
-
Posts
-
Try this it works for me:
piklist('field', array( 'type' => 'select' ,'field' => 'my_relate' ,'template' => 'field' ,'label' => 'Relate Posts' ,'choices' => piklist( get_posts(array( 'post_type' => 'rf_show' ,'numberposts' => -1 ,'orderby' => 'title' ,'order' => 'ASC' )) ,array('ID', 'post_title') ) ,'relate' => array( 'scope' => 'post' ) ,'attributes'=> array( 'multiple' => 'multiple' ) ));This will save relate data in the post_meta table
@felix– Welcome to the Piklist community!
Actually, the add more field sounds perfect for what you want.
Make sure you are using the latest beta. Then activate the Piklist demos. Add new Demo, click on the “Add More’s” tab and find the “Slide Images” field. I believe that’s what you want to use.
@4michaelcoleman– Are you using out latest beta? If so, you should see an very simple array to loop through.
@hirschbrat– This is not expected and is a bug. Will fix in next version.
@digger149– Sorry, Workflows are an admin only feature right now.
@digger149–
get_post_meta()works once the post is saved and the page refreshes.You may want to divide this up into Workflow tabs. The first tab can be your
pricefield, and the second tab can be the calculation.To edit the form after submission, pass the ID of the object. Here we can edit Post ID 145:
http://mydomain.com/my_form/?_post[ID]=84Does that help?
You can add a standard update button to any parts file.
For instance, if your Workflows are for a Post Type, just copy the HTML from the standard WordPress update button and add it to your Workflow file.
<input type="submit" value="Update" class="button button-primary button-large" name="save">@web2feel– Welcome to the Piklist community!
@cjwebdesigntt is correct. Make sure you post_type name is actuallystaff.This works in the built-in demos, so I’m sure it will work for you.
One of the best parts of Piklist is that it’s code based so you can do anything you can think of.
In this situation you can just use the standard HTML INPUT attribute READONLY. Add this to your field to make a field readonly if the user can’t manage_options:
,'attributes' => array( 'readonly' => !current_user_can('manage_options') ? 'readonly' : '' )
