Forum Replies Created
-
Posts
-
@lobsterman– That would be great. Thank you so much. Please email an svn patch to contribute at piklist dot com.
Taxonomy fields are supported! Here’s the documentation.
Good catch.
Please change all instances of:
WP_CONTENT_URLtocontent_url()WP_PLUGIN_URLtoplugins_url()That should fix the issue… let me know.
We’ll release the changes in the next version.
@studioleland– This is not currently supported. When we finalize frontend form validation we will make this available. To stay up-to-date make sure you sign up for email updates on the home page.
@james_MC– This looks good. Just curious though… why didn’t you use a slightly modified version of the default WordPress _update_post_term_count.
If you remove the hard coded references to “publish” and pass an array of post statuses it will work as well.
In class-piklist-form.php, we enqueue the style:
wp_enqueue_style('jquery-ui-core');
to remove, add this to your functions.php file:
wp_dequeue_style('jquery-ui-core');If you want to remove it on the frontend only, something like this should work (untested):
function my_scripts()
{
wp_dequeue_style('jquery-ui-core');
}
add_action('wp_enqueue_scripts','my_scripts',99);John– You definitely found a bug. I believe you have to register your statuses with Piklist for this to work. Within your TICKET CPT, add the register post status code. It can be an exact duplicate of the WordPress defaults. Try adding this when you register the TICKET CPT. You can see the full format here.
,'status' => array(
'draft' => array(
'label' => 'Draft'
)
,'auto-draft' => array(
'label' => 'auto-draft'
)
,'pending' => array(
'label' => 'Pending'
)
,'future' => array(
'label' => 'Scheduled'
)
,'publish' => array(
'label' => 'Published'
)
,'private' => array(
'label' => 'Private'
)
,'trash' => array(
'label' => 'Trash'
)
,'inherit' => array(
'label' => 'inherit'
)
)
Let us know if this works.
@johnmcalester– I updated this tutorial to explain how to show values on a group or range of post statuses. Let me know if you need further clarification.
Yes, a field can be set to always read-only by including all post statuses in the range.
Hi David– We have some basic internal code working, but we need to make it Piklist ready (and easy to use). Unfortunately, there are a few other items we need to take care of first. Sorry.
@sebascar– You can include Piklist in your plugin or theme just like any other plugin. You would want to require_once piklist.php from your main plugin file or your theme’s functions.php file.
However, this really is not recommended.
By doing this, your users will not be able to upgrade Piklist in the future. A better way is to include the “Piklist Checker” code in your theme or plugin. This code checks if Piklist is installed and if not, will notify the user.
You can see how it works by checking our our WordPress Helpers plugin. Try activating it without Piklist.
The latest version of Piklist Checker can always be found here.
