Forum Replies Created
-
Posts
-
@friendlyfire3– When creating forms for the front-end of your website, you need to tell Piklist the scope of each field…where to save the data.
Add this:
'scope' => 'user_meta'
The field ‘my_image’ must be left over from something else. Piklist will save the field exactly how you specify it
@vayu– What happens if you set the value to a date, like today?
'value' => date('M d, Y', time() + 604800)@claude– While compatibility with other plugins, especially one as popular as PageBuilder is important to us, we are a small team and need to manage our time. Right now we are spending our time writing unit tests for Piklist and getting the next version ready.
If you would like to take a look and submit a patch please email us at [email protected]
@claude– Welcome to the Piklist community!
1) Not exactly sure what you mean by “life-cycle”, since your question seems to pertain to load time. Just like every WordPress plugin, they all get scanned on every page load (with the exception of caching). So Piklist will also look for
Plugin Type: Piklistin the comment block of all plugins.2) The empty widget title is not a known issue. Glad it was resolved.
Also, we recommend that you use the latest beta version. It’s more stable and feature-rich then the current version on WordPress.org.
Let us know if you have any other questions.
@abmcr– You can use the
Templatecomment block parameter.We’re writing unit tests for 0.9.9.x. Once completed, 1.0 should be done pretty quick.
@dameer– We really appreciate you using Piklist!
Your kind words are also appreciated. If you have a few minutes, it would be great if you could give Piklist a 5 Star review on WordPress.org. It really does help the project.
Make sure you add this to the comment block of your plugin:
Plugin type: PiklistYes. You can just create a standard text field with an add_more:
piklist('field', array( 'type' => 'text' // standard text field ,'field' => 'post_tag' // save to the post_tag taxonomy ,'scope' => 'taxonomy' // Tell Piklist that post_tag is a taxonomy ,'label' => 'Tags' // just a label ,'add_more' => true // make this a repeater field ));However, WordPress stores the term ID’s, not the name, so you’ll find, once you press save, the term ID’s will be displayed. Piklist has a filter for updating that:
add_filter('piklist_taxonomy_value_key', 'my_taxonomy_value_key', 10, 2); function my_taxonomy_value_key($type, $field) { return 'name'; }@conkid– I just emailed you back your code. The reason the taxonomy data wasn’t showing on the list table, is because you weren’t really saving the taxonomy data as taxonomy data… you were saving it as post_meta.
When using a taxonomy field on any page except editing terms (i.e. editing a post), you need to do two things:
1) The field name must be the exact name of the taxonomy.
2) You must set ‘scope’ => ‘taxonomy’Hope this helps.
In most cases, with the exception of validation and sanitization, the
optionsarray is not determined by Piklist, but by the underlying library. jQuery UI fields… the WordPress media uploader… etc.But we do this with our documentation everywhere (and probably should explain it better). For instance, when registering a Post Type using Piklist, we only document the unique Piklist parameters, but you can also use every WordPress parameter in register_post_type as well.
