Hi Anthony!

I assume that’s not working? I’d probably just use get_posts, use 'fields' => 'ids' to make the query leaner, and check to see if the result is empty. In a shortened form you probably won’t use exactly, something like this: if ( empty(get_posts($args)) ) { }

Hope this helps! 🙂

Hi Sergey!

Thanks for taking an interest! Please don’t take a dip in public activity as Piklist being dead. That’s a bit of a leap users sometimes make in a panic. Piklist is free and open-source, as such all users are able to fork Piklist and do whatever they need. That said, it’s a project of passion for us authors and we use it regularly so we want it to be high quality. If there’s a specific bug that’s breaking all of your work, can you please open another thread and point it out so we can best look into it? Thanks!

Hi @johnvanham!

So you’re adding Bootstrap to the whole of the admin-side? Not sure I’d recommend doing that as it could have unexpected results down the line with WordPress since it’s an entire CSS framework (assuming itself to be the threshold), whereas Piklist is extending the WP admin-side styles. You could try fixing it yourself by adding another stylesheet that more acutely reverses Bootstraps hiding styles for Piklist forms, but I can’t guarantee that won’t create new issues elsewhere.

Hope this helps! 🙂

Hi @norboo!

The label isn’t stored in any way, it’s simply there to help the user when filling out fields. If you really want something like that, then you can use a group field with either a hidden or settable label field:

piklist('field', array(
  'type'    => 'group',
  'field'   => 'clothes_width',
  'label'   => 'Width',
  'fields'  => array(
    array(
      'type'      => 'text',
      'field'     => 'value',
      'columns'   => 12,
      'value'     => 'N/A',
      'attributes'=> array(
        'class'     => 'text'
      )
    ),
    array(
      'type'    => 'hidden',
      'field'   => 'label',
      'value'   => 'Width'
    )
  )
));

Hope this helps!

@girindev: WordPress 4.6 broke the ability for Piklist to fields to write directly to post fields (e.g. post_content, post_title, etc.). The bug has been fixed but we need to release a version of Piklist with the fix. I’ll try to push this along.

The most reliable way of fixing this is to use remove_post_type_support to remove the custom-fields feature for the page/post post types. Also, make sure not to add that for your own custom post types. It’s problematic with Piklist as it writes over the meta immediately after Piklist writes to it.

@Mehdi Salem: Glad you figured it out! Can you please elaborate on the js performance issues you had?

Hey guys!

I’m one of the authors of Piklist and, while Kevin has been very busy this year, Steve and I are still around. I apologize I’m not as reliably on the forums as Steve. He’s killer at support. My agency uses Piklist on every single project, so it is far from dead. We haven’t really added any new features in a while, but in my opinion Piklist has needed a season os solidifying and fixing bugs for a while. I’ve continued to fix bugs as I find them, but I’ve really found very few as it is getting pretty solid (and the bugs are pretty niche).

Rest assured the project is by no means dead. 🙂