amcnicoll

I should add: I’ve added a temporary fix:
if(!is_array($notes)) { $notes = array($notes); }
This means that the page listed above no longer shows an error.

Thanks, @danbru. I wanted to check because the last post from @wpforchurch seemed to imply that everything was fixed in the latest release.

Sorry, just for clarity, is this the process?
1. We delete current plugin files (will this lose settings, or are they in database?)
2. We reinstall 2.16.1 using the download link you provided
3. We are then on the latest and most fixed version of the plugin – we shouldn’t need to make any more changes until the next version comes out.
Is that right?

OK, hopefully this is helpful to plugin devs. I have the exact same behaviour. On single sermon pages only, if I change the template to “Elementor full width” then I get the same behaviour as @wshosted – that is, no media assets and a pipe-separated set of data displayed as the page content.
See https://imgur.com/a/hjBISoT for screenshot, given that I’m not going to leave the page that way. Note from Inspect panel – no javascript errors or 404s.
@wshosted – the good news is that you can bulk-edit the templates as a stopgap (if you want). Go to Sermons -> All Sermons, then click the checkbox next to “Sermon Title” to select all. Under bulk actions, select “Edit” then “Apply”. Under the other options (speaker, series, etc.) you’ll see “template”. You can change this to “Default Template” (or some other one) and then hit Update.

If that’s helpful then I’ll keep posting back test results in the hope of helping you isolate the issue.

I was using the built-in “sermon archive” page (as specified in /wp-admin/edit.php?post_type=wpfc_sermon&page=sm-settings) but I’ve just spun up a blank non-elementor page using the same shortcode as you, and it seems to work fine: https://new.wheatleycommunitychurch.org/test-page/ (though I’ll be the first to say that our layout is not as pretty as yours!)

Three thoughts cross my mind – feel free to take them or leave them:
1. Is it possible that it’s down to something specific with your theme? Perhaps it extends Elementor somehow? It might be worth briefly switching to another Elementor theme and seeing if it breaks. We’re using Overlay (https://en-gb.www.ads-software.com/themes/overlay/).

2. Under Sermon Manager settings, on the Display tab, is “disable sermon manager’s CSS” ticked? Ours isn’t, but if something’s going wrong in the display, it could be a CSS clash.

3. As you have admin access, can you take a backup and try restoring it to a dummy WordPress install, perhaps on your local computer, to see if the issue persists? I realise that this is a bigger process than the other things, but presumably this is a serious enough issue for you that you’re up for a bigger task? You could install a local WordPress instance (use a Bitnami installer if you’ve not set up your own WordPress before – https://bitnami.com/stack/wordpress/installer) and then use a backup plugin (we use Updraft Plus) to create a backup of your live site, which you can then “restore” to your local version.

Of course, it may be that the plugin maintainers come up with something else in the meantime, or have better questions to ask!

@wshosted – I use the embed code, but have just now tried using a link too, and both seem to work fine (https://new.wheatleycommunitychurch.org/sermons/living-sacrifices-for-god/).

I’m using Elementor, and I’m running WP 5.4.2 on PHP 7.3. I briefly updated to PHP 7.4 and nothing broke. Sorry, I know that doesn’t help much; but hopefully it rules out a straight-up incompatibility with Elementor.

Out of interest, which site is it that you’re having trouble with?

@wpforchurch I’m guessing you know this, but just in case – some source control setups are configured by default to ignore filename case changes. That could result in your staging server working beautifully but the patches not fixing the problem.
Thanks for a great plugin.

Just a word in defence of the plug in authors (quite apart from the fact they’re providing the plugin for free).
Depending on their work flow, it’s entirely possible that the filename case issue doesn’t cause problems on their testbed system, and does in deployment. That’s been the experience of a few other plugin authors hitting similar snags.

For the benefit of anyone else who’s struggling with this issue and has the tech knowhow to fix it, the clue is there in the error messages. The plugin is looking for /wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/includes/CMB2_Hookup.php, but if you look in the relevant folder you’ll see it has the wrong case: /wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/includes/CMB2_hookup.php. Rename it to have an uppercase H and it all works fine.