Single View showing Post Type instead of Post Title

That’s interesting, looks like both

https://socialvillage.ie/hope/reformed-witness/are-you-sure-of-your-salvation/

and

https://socialvillage.ie/hope/reformed-witness/the-separateness-of-the-church/

are having the exact same issue (which is good in away as it means it is a repeatable issue). Now, you said this problem is not occurring with your other CPTs, is there anything different with this CPT in comparison to the others?

Note, that when I try to navigate to anything outside of /hope/reformed-witness/ I get the following error:

Fatal error: Call to undefined function get_userdata() in /home/mkuhs/public_html/hope/resources/plugins/hopeprc-custom.php on line 135

It looks like you have a caching plugin of some sort enabled (it is stripping all HTML comments out of your document body) you may want to disable it until this gets sorted out. Additionally, if you do not have WP_DEBUG defined and set to true in your wp-config.php, I suggest doing that as well (need to see if anything is spitting out PHP warnings or errors).

Thanks for such a quick reply!!

The fatal error is gone, I was doing some live plugin editing ??

I’ve also turned on debugging. Plenty of PHP errors ?? but I don’t think any have to do with your plugin.

I can’t find anything really different between that CPT and any other (e.g. sermons, https://socialvillage.ie/hope/sermons/jehovah-weary-with-repenting/). Rewrite, has_archive, query_var, etc are all identical. The different CPTs have different combinations of Excerpt, Title, Editor, etc enabled, that’s the only difference I can find.

For debugging purposes could you add class="%type%" to your breadcrumb templates, and change your breadcrumb “Template (unlinked)” settings to <span class="%type%">%htitle%</span>?

OK I am such an idiot and I am so sorry for wasting your time!!!

For some stupid reason, I had set “Template (unlinked)” for that CPT to “The Reformed Witness”!!!

So… nothing wrong with your plugin, everything wrong with me…

At least you figured it out. I was a little stumped as to what was up with it (especially since some resources worked correctly). Hence the request to add the class="%type%" so I could get a better glimpse at what the plugin was thinking internally in that situation.