og:title. If your template or another SEO plugin also sets OG tags, the last one to run wins — disable the duplicate.onBeforeCompileHead; a template that builds its own <head> without calling the document head may bypass them.Older builds could crash if a scalar (e.g. 42) was saved into the Custom JSON-LD / Event / Recipe field. This is fixed: such values are now rejected on save and ignored on render. If you hit it on an older version, edit the record (or re-import a corrected CSV) so the JSON field contains an object { … } or is empty.
images/mokoog/generated/ — that directory must be writable. Failed writes are logged (Joomla logs, category mokoog).sitemap.xml is regenerated when an article is saved.noindex items are intentionally excluded.JPATH_ROOT/sitemap.xml must be writable; failures are logged.Grant the relevant action under Options → Permissions: mokoog.batch for batch generation, mokoog.import for CSV import/export. Users with core create (batch) or core create+edit (import) also pass.
You're on an older build without config.xml. Update to the current version — the component now ships a config.xml with a Permissions tab. OG/SEO settings themselves live in the System plugin, not the component Options.
OG data is stored per language with the unique key (content_type, content_id, language). Language-specific rows take priority over the * (All) wildcard. If an article's language is changed after saving, re-open and re-save its OG tab so the row is keyed to the new language.
Open an issue at the repository with your Joomla and PHP versions and steps to reproduce.
Printed from wiki · Troubleshooting