Public Access
fix(seo): mirror the visible version chain (14 → 15 → … → 20) into the EN FAQPage JSON-LD
The visible FAQ answer used arrows while the structured-data copy spelled the chain out with 'to', so acceptedAnswer.text was not verbatim-present on the page. FAQ parity check now reports 8/8 on EN/DE/ES.
This commit is contained in:
1 parent
b9a730942f
commit
141bf20c03
1 file changed
+1
-1
@@ -418,7 +418,7 @@
|
|||||||
"name": "Can we upgrade straight from Odoo 14 to Odoo 20?",
|
"name": "Can we upgrade straight from Odoo 14 to Odoo 20?",
|
||||||
"acceptedAnswer": {
|
"acceptedAnswer": {
|
||||||
"@type": "Answer",
|
"@type": "Answer",
|
||||||
"text": "No. It is one major version at a time: 14 to 15 to 16 to 17 to 18 to 19 to 20. Skipping a version is not a supported path. Our own migration service documents support for databases on Odoo 17, 18 and 19, main releases only — no patch releases — and older databases need a compatibility review first, which starts with a support ticket."
|
"text": "No. It is one major version at a time: 14 → 15 → 16 → 17 → 18 → 19 → 20. Skipping a version is not a supported path. Our own migration service documents support for databases on Odoo 17, 18 and 19, main releases only — no patch releases — and older databases need a compatibility review first, which starts with a support ticket."
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
|
|||||||
Reference in new issue
Block a user