| 开发者 | pluginlifeboat |
|---|---|
| 更新时间 | 2026年9月22日 01:45 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
sp_faq custom post type, the faq_cat taxonomy, the [sp_faq] shortcode, and the spfaq/sp-faq dynamic block.
If that original plugin has been removed or deactivated, Lifeboat – FAQ Rescue is for site owners who still have sp_faq posts sitting in their database and want their existing [sp_faq] shortcodes and spfaq/sp-faq blocks to render again — without reinstalling the original plugin and without migrating, rewriting, or converting the legacy content into a new format.
Lifeboat – FAQ Rescue reads legacy data in place. It registers compatible support for the legacy CPT and taxonomy, recognizes and restores the [sp_faq] shortcode, and recognizes and restores existing spfaq/sp-faq dynamic blocks. Legacy FAQ categories, published FAQ records, and featured images (where present on a legacy record) are all supported by the rendering path. The frontend accordion is accessible and dependency-free — no jQuery or external JavaScript library is loaded, and FAQ content remains readable in the page HTML even without JavaScript. A read-only diagnostics screen under Tools → Lifeboat – FAQ Rescue reports on detected legacy data and plugin status.
Lifeboat – FAQ Rescue does not migrate, copy, rewrite, or take ownership of legacy content, and does not offer an FAQ authoring or content-editing interface of its own. It does not phone home, does not use any external or cloud service, and does not collect telemetry.
Lifeboat – FAQ Rescue is an independent compatibility project and is not affiliated with or endorsed by the original plugin developer.
Security boundary. Lifeboat – FAQ Rescue is a compatibility and recovery tool, not a malware scanner and not a compromised-site cleanup tool. It does not scan for, detect, or remove malicious code, and it makes no claim about the security state of your site or its content. If you believe your site may have been compromised, complete a full security review and remediation using a dedicated security plugin or professional service before relying on Lifeboat – FAQ Rescue for content recovery.
[sp_faq] shortcodes and spfaq/sp-faq blocks already present in your content can now render using your surviving legacy data.No. Lifeboat – FAQ Rescue reads surviving legacy data in place and restores compatible rendering only. It does not migrate, copy, or rewrite your content.
No. Lifeboat – FAQ Rescue is designed to work without the original plugin being installed or active.
No. Lifeboat – FAQ Rescue only reads legacy data; it does not write to, modify, or delete legacy FAQ posts, terms, or content.
[sp_faq] shortcode?Yes. Existing [sp_faq] shortcodes already present in your content will render using Lifeboat – FAQ Rescue's compatible rendering.
Yes. Existing spfaq/sp-faq dynamic blocks already present in your content will render using Lifeboat – FAQ Rescue's compatible rendering.
Lifeboat – FAQ Rescue checks ownership before rendering and fails closed — if another plugin already owns the relevant identifier, Lifeboat – FAQ Rescue does not attempt to render in its place, avoiding conflicts.
No. Lifeboat – FAQ Rescue is a compatibility and recovery tool, not a security or malware-cleanup tool. See the Description section for its security boundary.
No. Lifeboat – FAQ Rescue does not use any external or cloud service and does not send data anywhere. All reading and rendering happens locally using your own WordPress installation.
No. Lifeboat – FAQ Rescue is a read-only recovery and compatibility tool for surviving legacy content. It does not provide an FAQ authoring or management interface.