hosting

GET /v1/sites/{siteId}/wordpress/update-policy

What this site is set to update by itself, and where it has drifted.

Ҳамаи нуқтаҳои ниҳоии hosting

Ҳамаи ҳуҷҷатҳои таҳиякунандагон

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати sites.view бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/wordpress/update-policy \
  -H "Authorization: Bearer zdk_live_…"

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли API кушоед

Тафсилот

Returns three things that must never be collapsed into one: the policy an operator stored, what the site is actually configured to do, and the drift between them. ⛔ A screen showing only the stored policy cannot tell a customer that the policy was never applied — which is the whole point. A decision is applied when a row changes, and the row that decides whether a WordPress updates itself lives on that WordPress, not in this platform's database. A customer can change any of it from wp-admin, a plugin can change it on activation, and a restored backup carries the old settings back. ⛔ observed_core is "" when WP_AUTO_UPDATE_CORE is not defined at all, which is NOT the same as off — an undefined constant means WordPress applies its own default, which is minor. Rendering the first as the second would tell an operator their sites are not taking security releases when in fact they are. ⛔ observed_read is false when the site could not be read (a managed hosting package, or a box that did not answer). An empty drift is only meaningful while it is true; otherwise an unreachable site renders as compliant, which is the worst default for a security setting. Ungated read — requires sites.view.

Параметрҳо

НомНамудТалаб карда мешавадИн чӣ аст
siteId (path)UuidБалеSite ID (UUIDv7).

Ҷавоб

НомНамудТалаб карда мешавадИн чӣ аст
corestring<off, minor, all>БалеThe stored policy for WordPress core updates.
pluginsbooleanБалеThe stored policy — whether every plugin should auto-update.
themesbooleanБалеThe stored policy — whether every theme should auto-update.
ringstring<canary, early, general>БалеThe staged-rollout ring this site belongs to.
applied_atstringБалеWhen the policy last reached the site, ISO-8601, or "" if it never has. ⛔ A timestamp and not a flag: "when did this last reach the site" is the question an operator asks, and a…
apply_errorstringБалеWhy the last apply failed, or "". Kept beside applied_at rather than replacing it, so a failed re-apply does not erase that an earlier one worked.
observed_readbooleanБалеWhether the site itself was read. ⛔ An empty drift is only meaningful while this is true.
observed_corestringБалеWhat WP_AUTO_UPDATE_CORE is set to on the site — off, minor, all, or "" meaning the constant is not defined at all, so WordPress applies its own default. ⛔ "" is…
plugins_offstring[]БалеThe plugins on this site that are NOT auto-updating.
themes_offstring[]БалеThe themes on this site that are NOT auto-updating.
driftstring<core, plugins, themes>[]БалеWhich of core, plugins, themes the site disagrees with the policy about.

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

401 · 403 · 404 · 429 · 503