Viewing 5 replies - 1 through 5 (of 5 total)
  • Yup, same here. my custom fields disappeared as well after updating to latest version 0.51. rolling back to version 0.50.3 solves the problem for now.

    Same problem. To author: please, edit “Other notes” or fix it.

    Same problem here too. It’s showing when you don’t use the posts.php template.

    [catlist name=your_catlist_name template=something_here_but_not_the_template customfield_display=your_custom_field_name ]

    For me it’s seems that this line in posts.php don’t work: $lcp_display_output .= $this->get_custom_fields($this->params['customfield_display'], $single->ID);

    I downgraded as well.

    Hi, several people have noticed this.

    I think I’ve just found the problem and here’s the response I’ve put to the other threads. Hope it helps:

    I’ve found a bug in the LCP version 0.51 lcp-catlistdisplayer.php code.
    In an older version which I have the get_custom_fields function used to have several parameters, the first of which was the setting of customfield_display. For some reason, the author has removed that and the function now only has the post_id as a parameter passed to it.

    For a quick fix if you change this line in your template:
    $lcp_display_output .= $this->get_custom_fields($this->params[‘customfield_display’], $single->ID);

    to
    $lcp_display_output .= $this->get_custom_fields($single->ID);

    you may find it works. Let us know, because there must be hundreds, if not thousands, of templates that are now broken.

    [As an afterthought, you may be better off having both lines in your template as that will allow you to go back or forward on versions, and help if the author goes back to the previous way of doing things.]

    ***CORRECTION***

    sorry, the author has also changed the way the post id is send to get_custom_fields so your new line should be:
    $lcp_display_output .= $this->get_custom_fields($single);

    ie without the ->ID (he now picks up the info about whether customfields are to be displayed from the object, so you don’t need to send the parameters separately).

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Pulling Custom Field Not working’ is closed to new replies.