Forum Replies Created

Viewing 15 posts - 1,726 through 1,740 (of 2,964 total)
  • Author
    Posts
  • in reply to: title translation #3854
    Steve
    Keymaster

    @graup– Currently this is not possible. We are working on a solution.

    in reply to: Fail to create custom meta boxes for simple plugin #3852
    Steve
    Keymaster

    @graup– Thanks for letting us know. We have this tutorial, but obviously it’s not working. We are in the process of redoing our user guide and will take this into consideration.

    in reply to: show_in_admin_all_list #3851
    Steve
    Keymaster

    @justin– Great! Let us know if you need anymore help. Closing this ticket.

    in reply to: show_in_admin_all_list #3848
    Steve
    Keymaster

    @justin– Post Statuses are an example of how Piklist just makes it easier to use WordPress functions. This is actually all WordPress, and this is a known WordPress bug.

    One of the comments in the trac ticket suggest a temporarily fix of adding this parameter:
    protected => true

    Let us know if that works.

    in reply to: All Fields Read by Yoast SEO? #3846
    Steve
    Keymaster

    @dre711– This is really a question for Yoast, on the best way to add all your custom fields (Piklist or others) to his plugin.

    However, I found this post that might help >.

    Essentially, you can use the WordPress function get_post_custom to pull all your custom fields, and then loop through theme and add them to the $content parameter.

    Does that make sense?

    Steve
    Keymaster

    @kattagami– Unfortunately, not. Definitely on our list… but not yet.

    in reply to: All Fields Read by Yoast SEO? #3842
    Steve
    Keymaster

    @dre711– Welcome to the Piklist community!

    Since Piklist does everything the WordPress way, any information you can find on the Yoast wpseo_pre_analysis_post_content filter would work.

    Here’s what I found. Add this to your theme’s functions.php file or your main plugin file:

    function my_custom_content_analysis($content)
    {
    	global $post;
    
    	return $content . ' ' . get_post_meta($post->ID, 'PIKLIST-FIELD-NAME', true);
    }
    
    add_filter('wpseo_pre_analysis_post_content', 'my_custom_content_analysis');
    

    The PIKLIST-FIELD-NAME is the field parameter when in your field array.

    This code will only work with text, textarea and editor field. If you want to do something fancier, you may have to pull the post_meta and loop through the data.

    Let us know if you need any more help.

    in reply to: File upload in group #3838
    Steve
    Keymaster

    @agi– [0] => undefined is a bug with the file upload field. We will address in the next version. Are you able to get around it or do you need help?

    in reply to: Piklist and Unyson #3836
    Steve
    Keymaster

    @quanganh– Thanks for letting us know. We never tested with Unyson. We’ll add it to our list of plugins to test.

    in reply to: Is piklist is for me ? #3831
    Steve
    Keymaster

    Great! Closing ticket!

    in reply to: Piklist saving error #3830
    Steve
    Keymaster

    @justin– Odd. We haven’t seen this before. We will try to reproduce.

    in reply to: Piklist saving error #3825
    Steve
    Keymaster

    @justin– Do you have any Piklist code running?

    in reply to: Replacing the WordPress Post Editor Observation #3824
    Steve
    Keymaster

    @joedostie– Welcome to the Piklist community!

    The function in that tutorial, my_remove_post_type_support(), uses a standard WordPress function remove_post_type_support(). The reason this removed the Avada editor is because of the way Avada registered their editor. This is not an issue for Piklist or WordPress, but for Avada.

    So, the answer to your question is: It depends on how the theme/plugin authors register their editor with WordPress.

    The only thing you can do is try different editors, or ask the theme/plugin author beforehand: “If I run this function remove_post_type_support(‘post’, ‘editor’) will it remove your editor”?

    Hope that helped.

    in reply to: Display code examples? #3823
    Steve
    Keymaster

    @davisdp– While building Fields and Forms we released that Piklist itself needed some work. We decided to work on getting Piklist as stable as possible so we would have a good foundation to build on.

    We don’t have a public roadmap, but you be assured that we work on Piklist everyday and are getting closer to the next release.

    I hope that answers you question.

    in reply to: Is piklist is for me ? #3822
    Steve
    Keymaster

    The default WordPress post_ID is an integer, so you can’t use DVD0001. However, you can automatically set the post title to this using the Piklist filter piklist_empty_post_title

    Check out this example >

Viewing 15 posts - 1,726 through 1,740 (of 2,964 total)