Run Your First Sync
The full sync imports sermon content from Planning Center Publishing. Events do not use this import; event blocks request current Calendar data when they render.
Prerequisites
Section titled “Prerequisites”Kleis must show Connected to Planning Center, and at least one episode should be published in Planning Center Publishing.
Run the sync
Section titled “Run the sync”- Go to Settings > Kleis for Planning Center.
- Find Manual Sync.
- Select Run Manual Sync.
- Watch the progress under Manual Sync, or return later to review it.
- Note the value beside Last Full Sync.
- Open Episodes in WordPress and inspect a recently published episode.
Large libraries and recovery
Section titled “Large libraries and recovery”Manual sync runs in small background batches instead of one long settings request. Each batch processes up to 10 pages or episodes within a 10-second budget. Kleis saves its place after each page or episode, then starts the next background batch. The time budget stops new work between records. A slow record can take longer.
The job continues without visitor traffic when background requests work. Keep the settings page open to help the job advance if your server blocks background requests. An existing job continues from its saved progress after a plugin update.
The progress display shows the current stage and processed record counts. Starting another manual sync does not create a second job while one is running. Last Full Sync changes only after the whole job completes. Refresh the settings page after completion to update the controls and completion time.
- To stop a running job, select Cancel sync. Cancellation takes effect after the current page or episode.
- If a job stops after repeated failures, resolve the displayed error and select Resume Manual Sync.
- To start over after a failed job, select Discard saved sync progress first.
Resuming retries the saved batch instead of importing the whole library again. Previously imported content remains after cancellation. Kleis retries interrupted batches and stops after three unsuccessful attempts. A resumed batch can repeat an update if the server stopped before saving its progress.
WordPress scheduled tasks provide recovery after an interrupted background request. If progress stops, keep the settings page open and resolve scheduled-task or loopback errors in Tools > Site Health. Sites that disable WordPress cron need an external cron runner for recovery after interruptions. Large libraries take longer, but the settings request does not wait for the import.
What the sync imports
Section titled “What the sync imports”Kleis creates or updates native Episode posts and synchronizes:
- title, description, and Planning Center publish date
- episode artwork as the featured image
- hosted or external sermon audio details
- on-demand video URLs and iframe embed codes
- episode resource links
- the Church Center episode URL
- channel, series, and speaker terms
The source fields are managed by Planning Center. A later sync can replace WordPress edits to synchronized episode fields. Build the shared presentation in WordPress templates rather than manually redesigning each imported episode.
If you merge duplicate people in Planning Center, Kleis keeps their existing WordPress speaker archive and sermon links connected to the primary person on the next sync.
If content is missing
Section titled “If content is missing”Confirm the episode is published to the Planning Center library and that the connected account can access Publishing. Then rerun the sync. See sync and connection help for individual missing fields.