Forum Replies Created

Viewing 15 posts - 1 through 15 (of 122 total)
  • Author
    Posts
  • in reply to: flexible content #5033
    Kevin
    Keymaster

    Hi @mcdonna-

    Switch add-more to add_more and it should turn on.

    Thanks,

    Kevin

    in reply to: Create CPT on frontend #4835
    Kevin
    Keymaster

    @hozefasmile-

    process_views is an old method, its not in trunk at all. Please re-download and re-install.

    Thanks,

    Kevin

    in reply to: post relationships not preserved in upgrade #4807
    Kevin
    Keymaster

    @mcmaster-

    The current table is wp_post_relationships (wp_piklist_cpt_relate is the legacy table) and thats where the data in the migration is pulled from. Try running the upgrade script on the latest version and let us know if the problem persists.

    Thanks,

    Kevin

    in reply to: Typo #4806
    Kevin
    Keymaster

    Thanks, its fixed in the next release 😉

    in reply to: Sanitizing doesn't work for settings pages #4798
    Kevin
    Keymaster

    @kplaneta-

    Grab v0.9.9.6 at piklist.com/trunk

    Thanks,

    Kevin

    in reply to: file upload input box overlays description #4794
    Kevin
    Keymaster

    @mcmaster- I think this could be solved by using a different field template. It looks like the add-more is just using template => field and its not clearing the responsive container above it. We will look into any additional help we can give these defaults templates on a later release.

    in reply to: teeny editor nests data in divs (0.9.9.4) #4793
    Kevin
    Keymaster

    @mcmaster- It looks like you have something inserting layout html into your editors?

    in reply to: Cannot output inline styles within editors #4792
    Kevin
    Keymaster

    @shayneol-

    We actually moved the description on the default field template to the bottom of the field to be more consistent with the wp-admin style guide. However you can change it if you like by defining your own field template or modifying the one being used, in this case ‘post_meta’

    Let us know if you need anything else.

    Kevin

    add_filter('piklist_field_templates', 'my_field_templates');
    function my_field_templates($templates)
    {
      $templates['post_meta']['template'] = '[field_wrapper]
                                               <div class="%1$s piklist-field-container">
                                                 <div class="piklist-field-container-row">
                                                   <div class="piklist-label-container">
                                                     [field_label]
                                                     [field_description_wrapper]
                                                       <p class="piklist-field-description description">[field_description]</p>
                                                     [/field_description_wrapper]
                                                   </div>
                                                   <div class="piklist-field">
                                                     [field]
                                                   </div>
                                                 </div>
                                               </div>
                                             [/field_wrapper]';
                                              
      return $templates;
    }
    in reply to: Numbering order based on drag and drop #4723
    Kevin
    Keymaster

    @rachel-

    The data in the add-more fields is stored in that order in the database. So in the case of your post meta field, the data is ordered by meta_id, the lowest id being the first item in the add-more field. Let me know if you have any more questions.

    Thanks,

    Kevin

    in reply to: Critical: Preview while editing metaboxes causes data loss #4722
    Kevin
    Keymaster

    @mcmaster-

    I wasn’t able to reproduce this on a fresh install. This was the only field on my edit screen, the preview worked as expected and several edits and updates worked as expected. If you would like to send credentials for us to login we would be more than happy to take a look.

    Thanks,

    Kevin

    in reply to: single quote marks are backslashed [0.9.9.4] #4712
    Kevin
    Keymaster

    @mcmaster-

    This is fixed in the next beta release.

    Thanks,

    Kevin

    in reply to: How to divide settings page with h3 sections #4642
    Kevin
    Keymaster

    Hi Chris-

    Are you using the parts/settings folder? Please add some example code and we will get you setup.

    Thanks,

    Kevin

    in reply to: Post_relate -bugs [0.9.9.2] #4637
    Kevin
    Keymaster

    @Justin-

    I tried the following field below and it works as expected (I just swapped the choices). Can you try it? Also please make sure you don’t have any other __relate_post fields on the form at all.

    piklist('field', array(
      'type' => 'select'
      ,'field' => '_' . piklist::$prefix . 'relate_post'
      ,'label' => __('Mission Trip', 'extreme')
      ,'choices' => piklist(
        get_posts(array(
          'post_type' => 'post'
          ,'numberposts' => -1
          ,'orderby' => 'title'
          ,'order' => 'ASC'
        ))
        ,array('ID', 'post_title')
      )
      ,'relate' => array(
        'scope' => 'post'
      )
    ));
    in reply to: Advice for sorting by date (with Date Picker) #4633
    Kevin
    Keymaster

    Hi Guys-

    Sorry I just read this one again, for future reference its very easy to write some code for piklist to handle this. Check out the render_field method in includes/class-piklist-form.php. The following hooks for pre render of a field would allow you to convert a datetime stored in the system.

        /**
         * piklist_request_field
         * Filter the request field
         *
         * @param array $field
         *
         * @since 1.0
         */
        $field = apply_filters('piklist_request_field', $field);
    
        /**
         * piklist_request_field_$scope_$field
         * Filter a specific request field
         *
         * The dynamic portions of the hook name, <code>$field['scope']</code> and <code>$field['field']</code>,
         * refer to the 'scope' and 'field' parameters, of an individual field.
         *
         * @param array $field
         *
         * @since 1.0
         */
        $field = apply_filters('piklist_request_field_' . $field['scope'] . '_' . $field['field'], $field);

    And the save hooks would allow you to format it back to a datetime after the save method.

          /**
           * piklist_save_field
           * Fires after fields have been saved
           *
           * @param $type Field type.
           *
           * @since 1.0
           */
          do_action('piklist_save_field', $scope, $fields);
    
          /**
           * piklist_save_field-{$scope}
           * Fires after fields have been saved and is scope specific
           *
           * @param $type Field type.
           *
           * @since 1.0
           */
          do_action("piklist_save_field-{$scope}", $fields);

    Let me know if you guys have any questions.

    Thanks,

    Kevin

    in reply to: user Flow 0.9.9.3 #4632
    Kevin
    Keymaster

    @justin-

    Grab v0.9.9.4 and check out the demo-common-profile.php and the demo-header.php files. We built in the functionality you have into a comment block parameter:

    Default Form: true/false

    This will allow you to show the default form for that admin page on that tab.

    Thanks,

    Kevin

Viewing 15 posts - 1 through 15 (of 122 total)