hosting
POST /v1/sites/{siteId}/wordpress/checksum
Restore a site's modified WordPress core files.
Xaqiijinta aqoonsiga
U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda sites.view; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.
Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.
Isku day
Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/wordpress/checksum \
-H "Authorization: Bearer zdk_live_…"Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API
Details
Asks the vendor to replace every core file that differs from the published checksum with the published one. Local modifications to core files are lost, which is the point — but a legitimate customisation living in core goes with them, so the client names the files back first. `202` and not `200`: the platform restores the files afterwards, so the report in the body may still list them. A security screen that says "fixed" before it is fixed is worse than one that says "still checking". `404` for a site with no vendor hosting package. Requires `sites.view` and `sites.panel_access`.
Cabiraha
| Magaca | Nooc | Loo baahan yahay | Maxay tahay |
|---|---|---|---|
siteId (path) | Uuid | Haa | Site ID (UUIDv7). |
Jawaab
| Magaca | Nooc | Loo baahan yahay | Maxay tahay |
|---|---|---|---|
ok | boolean | Haa | Whether nothing differs. |
files | string[] | Haa | The core files that differ, by path. Empty when `ok` is true. Read from the vendor's path-keyed map, so a file is named rather than merely counted. |
Cilladaha ay bartaani soo celin karto
401 · 403 · 404 · 409 · 422 · 429 · 503