feat: n8n can replace the JSON-LD of content elements via PUT /api/json-ld/{uid}
n8n is the source of truth for the SEO markup: the element's bodytext is overwritten with the posted object, wrapped in a ld+json script element. Values are escaped with JSON_HEX_TAG so they cannot close the element. The endpoint has its own key (jsonLdApiKey, header only) and writes through DataHandler as the non-admin backend user _n8n, so every change is in the record history and can be undone there, and the page cache is cleared. Until the key and the user exist on prod, every request answers 403/503. Prod setup (group n8n, user _n8n) is in docs/cms-api.md. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
1 parent
81a8013e8a
commit
7ae9aa266e
6 files changed
+185
-11
No files matched your search
@@ -22,6 +22,8 @@ return [
|
||||
'ep_products' => [
|
||||
// /api/hotel, /api/product, /api/content/* (X-Api-Key or ?key=)
|
||||
'cmsApiKey' => '',
|
||||
// n8n: PUT /api/json-ld/{uid} (X-Api-Key only), writes as backend user _n8n
|
||||
'jsonLdApiKey' => '',
|
||||
// MyE&P OAuth2 client credentials (import, price calendar); locally e.g. https://myep.ddev.site/api/
|
||||
'myEpApiBaseUrl' => '',
|
||||
'myEpApiClientId' => '',
|
||||
|
||||
Reference in new issue
Block a user