Questions & answers
Getting started
Section titled “Getting started”Where is the catalog?
Section titled “Where is the catalog?”Open Plugins → Add New → deckerweb. WordPress.org remains the default view.
Does it contact external services?
Section titled “Does it contact external services?”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.
Requirements and installation
Section titled “Requirements and installation”Why is an installation unavailable?
Section titled “Why is an installation unavailable?”Check the card for missing or inactive dependencies and WordPress/PHP requirements. Prerequisites are not installed automatically; activation is separate.
Can I hide it?
Section titled “Can I hide it?”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.
Catalog and update checks
Section titled “Catalog and update checks”Does each plugin release require a new Library?
Section titled “Does each plugin release require a new Library?”No. An approved online catalog revision can carry a newer plugin version independently of the embedded component.
Why can the catalog and updater show different freshness?
Section titled “Why can the catalog and updater show different freshness?”Discovery is cached for 24 hours; installed-plugin updates use an independent cache in the WordPress cycle. Package actions recheck approval freshly.
Do users need a GitHub token?
Section titled “Do users need a GitHub token?”Public catalog and release downloads do not require user tokens. Optional operator credentials remain outside distributed files.
Shared settings and data
Section titled “Shared settings and data”What happens when I remove a host?
Section titled “What happens when I remove a host?”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.
Does it support Multisite?
Section titled “Does it support Multisite?”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.
How do I report a vulnerability?
Section titled “How do I report a vulnerability?”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.
Additional questions about coexistence
Section titled “Additional questions about coexistence”Do I still need Git Updater? How do the update mechanisms coexist?
Section titled “Do I still need Git Updater? How do the update mechanisms coexist?”Current deckerweb plugins with the embedded updater do not need Git Updater as an additional update mechanism. I often recommended and used Git Updater in the past. Other plugins or themes may still depend on it, so do not remove it indiscriminately.
The Updater and Library locally recognize active Git Updater or older GitHub Updater installations and may show one shared dismissible notice. They do not deactivate anything automatically. Library 1.1.0 also includes targeted adjustments for Git Updater nonce checks and passing the plugin identity. This does not guarantee every combination of versions and extensions.
If an installation or update fails, temporarily deactivate Git Updater and retry. Reactivate it afterwards if other extensions need it. Only leave it disabled permanently when every affected plugin and theme has another reliable update mechanism.
Coexistence in detail · Library FAQ
Can the Library update an older plugin without its own updater?
Section titled “Can the Library update an older plugin without its own updater?”For matching installed catalog entries, the Library may offer a verified update directly in the card, even when the old version has no embedded updater. This requires an unambiguous match and an approved compatible package.
If no matching offer appears or you want to migrate independently of the catalog, use the manual ZIP method above. Neither the catalog nor an update silently installs required third-party dependencies.
Manual update steps · Catalog actions
Imported from the published component 1.1.0. Original source · Deutsch