Hi, what version of LCP are you using.
Also, have you changed default template at all?
Quite a few people reported a problem similar to this which may be relevant. See
https://wordpress.org/support/topic/customfield_display-not-working?replies=6
I just downloaded it from the wp repo for the first time that day, so version 0.51.
I was using a template in my themes directory but I deleted it and it still didn’t work.
So then I tried adding the line:
$lcp_display_output .= $this->get_custom_fields($single);
to the plugin’s (wp-content/plugins/list-category-posts/templates/default.php) template and no change. I also tried by commenting out the original line, no change.
Also, changing customfield_display_name=”no” to YES does NOT display the field name.
Thanks for your help!
Here’s the dev site url:
http://instantguidance.com/strong2/news-listing/
Just updated the new version released and it’s still not displaying custom post types. I am really hoping for a fix for this, and would be willing to donate, if I can learn what the conversion rate from USD is 🙂
Hi, as far as I can tell, LCP does not use the default template that is in its own filespace (ie the one you changed) – it’s just there as an example of the sort of things you can put in a template.
Could you check that you have NOT got a default.php file in your theme’s (or child theme’s) directory at /list-category-posts/default.php
you maybe have one left over from a previous version. If that gets picked up it might not have the fix (calling using $single).
I just confirmed that I have no “list-category-posts” folder (and therefore no files within a folder of that name) in my theme’s directory (child, nor parent theme.)
I even deleted the default.php from the plugin’s template directory, and still no change. I don’t think anything could be left over from a previous version, because I just installed it for the first time.
But just to be sure, I deactivated the plugin, deleted all the files and reinstalled from the WP repo. Still the same result. I wondered if “pdf” was something reserved so I changed the field name to “press_release_pdf” no change.
** Resolved ***
Dumb as it seems, see above how
customfield_display_name="no" ]
wrapped to a second line? That was in text view even. All I did was delete the spaces between so the short code was all on one line and then it worked. I could kick myself.
It’s very glitchy if you enter a long string of short code directly into your wordpress page. However if you switch the view to “text” instead of “visual” you can then clean up your string. It seems wordpress adds code to the line for you if it spreads out onto extra lines.
When I saw this it was an easy fix and everything worked ok.
