Sermon Library

Yes. Choose Sermon Manager on the Import / Export screen and click Scan. It reads the sermons already on your site, whether they came from Sermon Manager, Sermon Works or Mattytap Sermons, and shows you what it found before writing anything. Your existing plugin and its data are left exactly as they are. The old plugin does not have to be active. If you already deactivated or deleted it, your sermons are still in the database and this will find them. Preachers and series become full profile and series pages rather than taxonomy terms, so they gain a headshot, a bio, cover art and their own descriptions. Sermons keep their audio, video, scripture reference, date, image, notes, bulletins, view counts and publication status.

The scan finds them and shows you. Any plugin that lets a name be typed freely into a tag box ends up with several spellings of the same person, each with its own archive page. Sermon Library groups the likely duplicates, suggests which record to keep, and lets you merge them before the import writes anything. You can also choose to leave them separate.

Yes, in two ways. The scan is read only, so you can look at what would happen and stop there. And when you do import, you can bring everything in as drafts, check it, and publish when you are happy. Nothing in your old plugin is changed either way, so both plugins can run side by side while you compare.

Only if you skip a step, so do this one first. Your feed URL changes when you move, and directories need telling. Before deactivating your old plugin, set its podcast Redirect field to your new feed URL, which you will find under Settings in the Sermon Library section. Leave both running for a couple of weeks so every app has time to follow, then switch the old one off. Your subscribers come with you.

Yes. Export your sermons from Series Engine as CSV, then upload it on the Import / Export screen. The importer parses the file, lists every series it found, and lets you map each one to a new series, an existing one, or skip it. Nothing is written until you have reviewed that mapping.

Yes. Transcripts, articles, Bible studies and sermon notes each get a PDF download button on the sermon page. Nothing extra is required.

Yes to both. The RSS feed is iTunes compatible, and the show settings cover everything Apple checks for, including the owner email it uses to verify ownership and the artwork requirements. Your feed URL is on the Sermon Library settings screen. For a single series, speaker or topic, append ?series=ID, ?speaker=ID or ?topic=slug to that URL. The result is a feed containing only those sermons, which can be submitted separately.

Yes. Scripture is entered through a structured picker rather than a free text field, so the whole library can be filtered by book, and every passage links out to Bible.com or BibleGateway. Every passage also has a page of its own, listing the sermons preached from it. Put [scsl_scripture_list] on a page under Sermons for a full index, grouped by book.

Yes. Passages are compared as spans rather than as text, so anything covering the same words counts. A page for a single verse finds the sermons preached on the paragraph it sits in, on the whole chapter, and on the whole book. It works the other way too. A page for Ephesians 6:10-20 lists sermons on the individual verses inside it. Passages that merely sit next to each other are not treated as overlapping. A sermon on 6:10 does not appear under 6:12.

Because a run of consecutive verses reads better as the span it actually was. A sermon entered as 6:10, 6:11 and 6:12 shows as 6:10-12. Only verses that genuinely run together are joined. If a sermon covers 6:10 and 6:12 they stay separate, because writing 6:10-12 would say verse 11 was preached when it was skipped. What you entered is not changed. This is only how it reads on the page, so nothing is lost if you would rather list them out.

No, and deliberately. Almost every translation a church would choose is under copyright, and only the Bible site you are sent to is licensed to show it. Printing the words here would put your church in breach of a license it never agreed to, on the strength of picking a translation from a menu. Instead each passage page links out to read it, in whichever translation you have set.

Yes. All five shortcodes render inside page builders, and the styles load in the Elementor editor as well as on the front end.

Sermon Library requires a non-plain permalink structure. Go to Settings > Permalinks and choose "Post name" or any other option besides "Plain."

Yes. Copy any template from wp-content/plugins/seedcast-sermon-library/templates/ to wp-content/themes/your-theme/seedcast-sermon-library/ and edit freely.

No. Sermon Library adds its own post types and taxonomies. Your posts, pages and any other plugin's content are untouched.

Your sermons, series and speakers stay in the database. Deactivating hides them from the front end; it does not delete anything. The weekly completeness record is kept as well, since it cannot be rebuilt after the fact, so reactivating picks up where you left off rather than starting over.

PHP 7.4 or later. The plugin is tested against 7.4 on every release.

Nothing is contacted while a visitor reads your site, and nothing is sent anywhere in the background. Completeness scores, the weekly record and your church details are held in your own database and are never sent anywhere. Three things reach outside this site, all of them only when something is done deliberately. Scripture links point to Bible.com (YouVersion) or BibleGateway. These are ordinary links in the page. Nothing is sent unless a visitor clicks one, and then only by their own browser. Audio reclaim downloads files from Seedcast's public media storage (media.seedcast.ai) into your media library. It runs only when an administrator starts it from the Import / Export screen, and only for sermons whose audio is already hosted there. It requests the file and nothing else: no account, no key, and no information about your site is sent. Seedcast's terms are at seedcast.ai/terms and its privacy policy at seedcast.ai/privacy. Spam checking is part of the shared Seedcast library this plugin bundles, and Sermon Library does not switch it on: there are no public forms here, so it never runs. It is described because the code is present. Where a Seedcast plugin does use it, and only if an administrator has entered keys for one, a submitted form sends that form's challenge token and the submitting visitor's IP address to Google reCAPTCHA, hCaptcha or Cloudflare Turnstile so the answer can be checked. No keys are set by default, and with none set nothing is contacted.

Every sermon is scored on the details that make its page usable, speaker, series, focus passage, a recording and an image, and on the written sections you have said you use. Your library score is the average across every sermon, not a count of finished ones, so it moves whenever you fill anything in. The exact fields being counted are listed at the bottom of the Completeness report, so the page always documents the rules it is applying rather than sending you elsewhere to find out.

The weekly scores record whether the work happened while it was that week's work, so they lock once the week has passed. A sermon dated back to an earlier week after that week has closed still counts toward your library score, but it does not change the record of the week itself. Correcting a genuine mistake does work. If you mistype a date and fix it, the weeks involved are recalculated and marked as amended, because the sermon did exist at the time.

Yes. Settings, Display, and untick Show completeness scores. That removes the scores from the sermon list, the sermon editor and the menu. Weekly scores carry on being recorded quietly. They cannot be worked out after the fact, so if you switch the display back on a year from now the record is still there rather than starting from nothing. None of it leaves your site.

Yes. When a dedicated SEO plugin is active, Sermon Library steps aside and lets it handle meta descriptions, Open Graph and Twitter Card tags. Structured data for sermons is still added, because SEO plugins do not know what a sermon is.