Forum Replies Created
-
Posts
-
Is this still being looked into? I can’t seem to see the description…
piklist('field', array( 'type' => 'html', 'label' => 'Send email', 'field' => 'document_send_mail', 'description' => 'Send email with document.', 'value' => get_submit_button( 'Send document email', 'primary', 'send_document_mail' ) ));Oh, it just occurred to me that maybe you wrote this, when it was on version v0.9.9.9. If so, then I will edit the file myself and look forward to the next major release. 😉
Hi Steve.
When I download the latest version of Piklist v0.9.9.9 I see that the hidden field value is still not fixed.
It still returns:
value="<?php echo esc_attr($value); ?>"
and not
value="<?php echo is_array($value) ? esc_attr(end($value)) : esc_attr($value); ?>"Should it not do that or do a have a reason for not implementing this after all?
@smallgreenpinky, I don’t think you are being ignored. My problem is identical to mine and I have given you a possible solution. Steve is trying to help by getting some more info. 🙂
Hi Steve.
The custom post type is called “invoice”. No the default editor is not visible. I have not set it to support it in the code.$post_types['invoice'] = array( 'labels' => $labels, 'title' => __( 'Enter a new Demo Title' ), 'publicly_queryable' => true, 'exclude_from_search' => true, 'map_meta_cap' => true, 'capability_type' => array('invoice', 'invoices'), 'public' => true, 'hierarchical' => false, 'rewrite' => array( 'slug' => 'faktura', 'with_front' => true, 'pages' => true ), 'supports' => array( 'author', 'revisions', 'title', 'comments', ) ); return $post_types;My text field is not saving the text. I then read this thread https://piklist.com/support/topic/editor-field-not-saving-data/. If I remove the scope parameter, the warning disappears. However, then the text is saved to the postmeta table, which is not what I want. It is the post_content field, and I want it saved to the posts table.
This is how I set the wysiwyg field:piklist( 'field', array( 'type' => 'editor', 'scope' => 'post', 'field' => 'post_content', 'label' => 'Evt. tekst besked', 'value' => '', 'options' => array ( 'wpautop' => true, 'media_buttons' => false, 'tabindex' => '', 'editor_css' => '', 'editor_class' => '', 'teeny' => false, 'dfw' => false, 'tinymce' => true, 'quicktags' => true ) ) );Hi.
I have the same warning displayed when I edit a post (custom post type) in the admin.
It is shown right below a date field and above the main text wysiwyg field.I just noticed that if use a string on
capability_typethe Menu item in the admin disappears for all users that are not superadmins and they do not have rights to access the custom post type page in the admin. So there must be some difference in the way WordPress registers the capability_type if it’s a string or if it’s an array.
So this works but throws a warning:
'capability_type' => array('invoice')
This does not work and throws no warning:
'capability_type' => 'invoice'Well spotted Jason! That fixed it. 🙂 But I still don’t understand why it throws a warning? In the docs it says that it’s optional to use either string or array.
https://codex.wordpress.org/Function_Reference/register_post_typeOk no problem :-). I have used pastie: http://pastie.org/private/ornacmvb9lfuryv8qnddsg
