Forum Replies Created
-
Posts
-
You didn’t use the
validateparameter correctly. It should look like this:'validate' => array( array( 'type' => 'number' ) )Your code only defined ONE array.
@angelique– If you don’t use PiklistHelper does it work?
@alicegege– Welcome to the Piklist community!
Your code is working fine for me. Usually when you are having an issue like this, you have duplicated the field name on another field. Try changing the field name and see if that works.
If you are still having issues, feel free to email your entire plugin or theme to [email protected], and we’ll take a look.
Also, in most cases it is best NOT to include the
scopeparameter and let Piklist figure it out automatically.The documentation was incorrect. Your code should look like this:
add_filter('piklist_validation_rules', 'check_valid_numeric', 11); function check_valid_numeric($validation_rules) { $validation_rules['valid_amount'] = array( 'rule' => "/^[1-9]+(.\d+)?(.\d+)?/" ,'message' => __('is not a valid number.') ); return $validation_rules; }Documentation has been updated. Sorry for the inconvenience.
Let us know if you’re still having issues.
@hirschbrat– Welcome to the Piklist community! Thanks for posting.
WordPress doesn’t do a very good job of cleaning up expired transients. We are aware of this, and it will be fixed in the next major version of Piklist. We recommend you use this plugin to clean up the transients. It’s a quick and painless solution.
@ewafford– Welcome to the Piklist Community!
It would be appreciated if you could email the plugin with TGM so we can debug. Email to [email protected]
@michaellautman– Nice! Thanks for letting us know. Great job.
@angelique– I just tested on Post Meta and Settings and it worked for me. If you are still having issues, please zip up your plugin and email to [email protected] We’ll be happy to take a look.
As for the Email validation, please verify that it works in the Demos.
@claritywebworks– Welcome to the Piklist Community!
Unfortunately on_post_status is not designed for this… though it would be cool in future versions of Piklist.
I suggest you stick with standard WordPress functions. The codex shows a great example of how to send an email automatically using the save_post hook. Use this hook to check the value of your custom field and then trigger the necessary events.
Does that help?
Custom fields for NEW Terms are not supported because the WP admin does not really have the space for it.
We are considering putting it in Piklist anyway.
The WordPress capability parameter is for only showing pages. This is default WP behavior.
To change the capability for saving settings you need to use a WP filter.
The bottom of this doc explains this.
1) To place a settings page under the WordPress Settings use:
'sub_menu' => 'options-general.php'
2) You can definitely make a settings page under a settings page you created. When you make a settings page, WordPress creates a url like this:
admin.php?page=my_settings_page. Use this code to place a page under this one:'sub_menu' => 'my_settings_page'
Let us know if this works for you.
@igor– We are always working towards v1.0. The current version of Piklist at WordPress.org works great. When 1.0 is released it will have more features… but you can definitely use what’s at WP.org for your products.
