Forum Replies Created
-
Posts
-
Each field name needs to be unique. This is not a Piklist “thing”, but standard on HTML forms… you can’t have more than one field with the same name.
Make sure all of these are unique, and the form should work perfectly:
,'field' => 'field_name'So they should be something like:
,'field' => 'vagelis_sellers_name'
,'field' => 'vagelis_phone'
,'field' => 'vagelis_mobile_phone'It’s always a good idea to prepend your field names with some unique so you don’t conflict with other plugins.
@vagelis– Happy to help. Can you post your field code here so we can take a look? Or email the plugin to [email protected]
@davidbyersc– Welcome to the Piklist community!
In includes/class-piklist-meta.php comment out these three lines:
//add_filter('get_post_metadata', array('piklist_meta', 'get_post_meta'), 100, 4); //add_filter('get_user_metadata', array('piklist_meta', 'get_user_meta'), 100, 4); //add_filter('get_term_metadata', array('piklist_meta', 'get_term_meta'), 100, 4);Let me know if that works.
It sounds like the idea of using Parent/Child categories (or a custom taxonomy), is the way to go. WordPress lets you style every page. Check the WP template hierarchy. You probably want
taxonomy-$taxonomy.php, which would betaxonomy-destination.php.@cosmocanuck– In most instances the scope is the database table to save to. In your code, you’re setting
'scope' => 'post'. The wp_posts table only allows you to save to existing fields, not create a new one, likefestivalsawards.My guess is that you actually want to save your data to wp_postmeta, which would be
'scope' => 'post_meta'. The only reason to set it to'scope' => 'post'is if you wanted to replace the default editor.In most cases for forms in wp-admin, you don’t even have to set the scope, you can let Piklist automatically set it for you.
Let me know if that makes sense.
@friendlyfire3– Hint received! You’re on the list and will receive the next beta when it’s ready.
If you want to help the project now, a 5-Star review on WordPress.org helps tremendously. (hint hint)
@friendlyfire3– Thank you for the feedback. I updated the Getting Started Tutorial based on your recommendation.
Thank you for making our Docs better!
@dougsandlin– Welcome to the Piklist community!
Piklist does everything the WordPress way so 99% of the themes available should work just fine. The ones we recommend staying away have lots of built-in features to help you customize your webpages via drag-and-drop objects. Those themes don’t always do things properly and may interfere with some advanced Piklist features.
With that being said, most of the themes in the WordPress.org directory should be fine.
@cosmocanuck– Quotes need to go around the meta key:
echo wpautop(get_post_meta($post->ID, 'field_name', true));
I also updated the doc page to fix this typo.
Let me know if this works for you.
@mcmaster– Glad you got it working! Those docs you mentioned are now cross-linked.
The reason your code in the first example didn’t work is because you called a sanitization method that doesn’t exist: “text”, should be “text_field“:
'sanitize' => array( array( 'type' => 'text_field' ) )This inspired a new notice in the next version of Piklist, if you have WP_DEBUG turned on:
Notice: Sanitization type "text" is not valid.@calman– Welcome to the Piklist community!
“Reviews” sound a lot like “comments”. Let a user add a comment (review). If a comment already exists, then don’t show the comment form.
Would that work?
(You really don’t need Piklist if you do it this way)
