Field notes
What does read-only compatibility mean?
Every Plugin Lifeboat rescue is built around the same idea: read what survived in your WordPress database, render it safely, and leave the original records untouched. Here's what that means in practice.
When a WordPress plugin disappears from the official directory, the content it created usually doesn't disappear with it. Logo records, countdown timers, FAQ entries, and the shortcodes that display them can still be sitting in your site's database, waiting on a plugin that's no longer there to read them.
Every Plugin Lifeboat product is built around the same design principle for handling that situation: read-only compatibility. This note explains what that phrase actually means, using only what's already documented on each product's own page.
Read in place, not migrated
Logo Rescue, Countdown Rescue, and FAQ Rescue each read your existing, surviving legacy records directly, in place. None of them create a second, competing copy of your data, and none of them require reactivating the original discontinued plugin first.
Across all three products, the same boundaries apply: no migration, no copy, no writeback, and no deletion of the original content. The legacy records stay exactly where WordPress already stored them.
What each rescue actually reads
Logo Rescue reads existing legacy logo records, their featured images, destination links, and category relationships, and displays them through the existing [logoshowcase] shortcode. Logo Rescue
Countdown Rescue reads supported surviving countdown records and renders the historical [wpcdt-countdown] shortcode with a maintained, accessible countdown view. Countdown Rescue
FAQ Rescue reads supported surviving FAQ entries and category relationships, and renders the historical [sp_faq] shortcode and block through a maintained accordion view. FAQ Rescue
Diagnostics are read-only too
Each rescue includes a read-only diagnostics screen, under Tools in the WordPress admin, that reports what it found: surviving records, category relationships, eligibility or metadata issues, and shortcode or block references. The diagnostics screen does not edit or repair anything; it exists to help administrators understand what remains and what may need attention.
What read-only compatibility does not mean
Compatibility is not security remediation. None of the three rescues are malware cleanup tools, vulnerability scanners, or proof that a site is uncompromised. If a site was compromised, complete security remediation comes first; a Plugin Lifeboat rescue is not a substitute for it, and reactivating a historical vulnerable plugin to use one is not recommended.
It also doesn't mean feature parity with the original plugin. Each rescue targets a specific, documented legacy data contract and shortcode, not every historical Free or Pro feature the original plugin may have offered.
No account, no cloud, no tracking
Normal operation for all three products stays inside WordPress: no telemetry, no analytics, no account, no cloud dependency, and no external runtime service requirement. Nothing about reading your legacy content in place depends on a service relationship with Plugin Lifeboat.