Contents

Table of Contents

Troubleshooting

Meta tags don't appear on the frontend
A page shows a 500 error after editing structured data
OG image is missing or 404s
Sitemap is empty or missing entries
AI generation returns nothing / an error
"Forbidden" when running Batch or Import
The Options screen is empty
Multilingual: wrong language tags
Reporting issues

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Troubleshooting

Meta tags don't appear on the frontend

Confirm the System - MokoSuiteOpenGraph plugin is enabled (Extensions → Plugins).
Meta tags are only injected on the site (frontend), on HTML documents — not in the admin or on JSON/feed views.
View the page source and search for og:title. If your template or another SEO plugin also sets OG tags, the last one to run wins — disable the duplicate.
Tags are emitted on onBeforeCompileHead; a template that builds its own <head> without calling the document head may bypass them.

A page shows a 500 error after editing structured data

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.

OG image is missing or 404s

Set a Default Image (1200×630) in the plugin config as a fallback.
Ensure the GD PHP extension is installed if you use auto-resize.
Auto-resized files are written to images/mokoog/generated/ — that directory must be writable. Failed writes are logged (Joomla logs, category mokoog).

Sitemap is empty or missing entries

Enable Sitemap in the plugin config; sitemap.xml is regenerated when an article is saved.
Only published articles at public view levels are included — registered/special-access and noindex items are intentionally excluded.
JPATH_ROOT/sitemap.xml must be writable; failures are logged.

AI generation returns nothing / an error

AI must be enabled and an API key and model configured for the chosen provider.
The user must have article-edit permission — otherwise the request is rejected.
Non-200 responses from the provider now surface an error (HTTP status) instead of a blank result; check the message and your key/quota.
A hung provider times out after 20 seconds.

"Forbidden" when running Batch or Import

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.

The Options screen is empty

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.

Multilingual: wrong language tags

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.

Reporting issues

Open an issue at the repository with your Joomla and PHP versions and steps to reproduce.

Pages