Repository navigation
FAQ
Open Plugins → Add New → deckerweb. WordPress.org remains the default view.
Local browsing does not. Installation downloads the selected GitHub release. Optional online approval updates contact the configured first-party HTTPS endpoint; its server sees the requesting IP. No site URL, user ID, inventory or telemetry is sent.
Check the card for missing or inactive dependencies and WordPress/PHP requirements. Prerequisites are not installed automatically; activation is separate.
Use Settings → deckerweb Library (Network Settings on Multisite). Hiding discovery preserves dependency checks and existing managed updates. Disable online catalog retrieval separately to stop its requests.
No. An approved online catalog revision can carry a newer plugin version independently of the embedded component.
Discovery is cached for 24 hours; installed-plugin updates use an independent cache in the WordPress cycle. Package actions recheck approval freshly.
Public catalog and release downloads do not require user tokens. Optional operator credentials remain outside distributed files.
Another installed host, even inactive, preserves shared data. The final host removes temporary Library data and caches. Settings remain unless optional deletion was enabled. Installed plugins and their content remain. Hosts must call the supplied uninstall contract.
Library settings are shared per network. Daily Scripture 1.0.0 and newer support network activation; earlier installed versions must be updated first. Bricks QuickNav retains its per-site restriction. Permissions and dependency checks still apply.
Use Security → Advisories → Report a vulnerability in the host plugin repository. Include host and Library versions; do not post security details in public issues. Hosts must enable private reporting before publication.
- README EN · DE
- INTEGRATION EN · DE
- SERIES EN · DE
- CATALOG EN · DE
- FAQ EN · DE
- DATA EN · DE
- UPDATER EN · DE
- CHANGELOG EN · DE
- TESTING EN · DE
- SECURITY EN · DE