Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • workvista
    Participant

    Hi Steve,

    I deactivated all the plugins (I just have piklist enabled now) and also tried changing my theme. The warning still show up.

    Can you paste the screenshot of your relate – advanced demo. In addition to the warnings, the add mores (ones which were already added) also show up empty. Is that expected ?

    in reply to: add_more with relate to custom post type #7012
    workvista
    Participant

    @arranfraser – were you able to get this working ?

    I am doing a similar thing. I have a CPT1 which can hold many CPT2’s but I can’t get it working.
    I have spent a lot of time in it and I cannot get it to work.

    Another question. If CPT2 has a field called field_1 how would I populate that field from one these add mores. Right now any field except for post_type / post_status / post_content / post_title goes to CPT1’s post meta.

    Also would you mind pasting your code for CPT1 and CPT2. It could provide some hints.

    in reply to: Custom Taxonomy Count always shows 0 items in admin #7011
    workvista
    Participant

    Yes. One more observation:

    The counts work fine as long as I use a custom taxonomy and display it as the default metabox in admin UI.

    When I follow steps on https://piklist.com/learn/doc/display-taxonomies-radio-checkboxes-select-list/
    to convert the input as checkbox – only then the issue with count comes up. So it may have to do with Piklist.


    @kattagami
    – are you displaying taxonomy as select/checkbox/radio too ? That may explain why you see the issue too ?

    workvista
    Participant

    I looked at the code in /plugins/piklist/includes/class-piklist-form.php on line 923

                
                if (!is_wp_error($object) && is_object($object) && $allowed)
                {
                  array_push($return, $object->$field['field'] ? $object->$field['field'] : $field['value']);
                }
    

    Looks like there is no attribute $object->$field[‘field’] in the post object.

Viewing 4 posts - 1 through 4 (of 4 total)