Asset dependency errors

Symptom

Unsatisfied dependency 'core' for an asset 'com_joomlaai.dashboard' of type 'style'

The Dashboard (and all other views) shows a white page or a Joomla error.

Cause

This error occurs when joomla.asset.json includes "dependencies": ["core"] on a "type": "style" asset. The core asset is registered as a script in Joomla 6; cross-type dependencies are not allowed.

Fix

Upgrade to JoomlaAI 2.5.3 or later. The fixed joomla.asset.json has no "dependencies" fields on style assets.

If you need to fix manually, edit [joomla-root]/media/com_joomlaai/joomla.asset.json and remove all "dependencies" fields from assets with "type": "style".

"Invalid Token" on chat send

Symptom

Every chat message returns "Invalid Token" or "JINVALID_TOKEN".

Cause

The CSRF token in the form is stale (session expired or page cached).

Fix

1. Hard-reload the page (Ctrl+Shift+R / Cmd+Shift+R).
2. If the issue persists, check that Joomla's session lifetime is not too short (System → Global Configuration → System → Session Lifetime).
3. If you use a caching plugin (e.g., JotCache, CDN), ensure admin pages are excluded from cache.

Scheduled jobs not running

Symptom

The AI Scheduler has active jobs, but no new Content Review items appear. Health Check shows "run_due_jobs last ran > 15 minutes ago".

Cause

The cron trigger is not configured.

Fix (Joomla)

Add to your server's crontab:

* * * * *  php /path/to/joomla/cli/joomla.php scheduler:run --all --no-interaction >/dev/null 2>&1

Verify the Task plugin is enabled: System → Plugins → Task - JoomlaAI.

Fix (WordPress)

Add a real cron job and optionally disable WP-Cron's traffic trigger:

* * * * *  wp --path=/path/to/wordpress cron event run --due-now >/dev/null 2>&1

Or via PHP:

* * * * *  php /path/to/wordpress/wp-cron.php >/dev/null 2>&1

Check that the cron events are scheduled:

wp cron event list

You should see wpai_run_due_jobs, wpai_provider_health, and wpai_cleanup_old_data.

API key errors

Symptom

Health Check shows ❌ Auth error 401 for a provider. Chat returns an error message.

Cause

The API key is wrong, expired, or has no credits.

Fix

1. Regenerate a new key at the provider's dashboard.
2. In JoomlaAI: Configuration → Providers (Joomla) or Settings → Providers (WP).
3. Paste the new key and save.
4. Re-run Health Check to confirm it shows ✅.

Claude model not found (404)

Symptom

Claude API returns 404 when a scheduled job runs.

Cause

Speculative model IDs (e.g., claude-sonnet-4 without date suffix) are rejected by the Anthropic API.

Fix

Use full model IDs with date suffixes:

Update the model in Configuration → Providers → Claude Default Model.

Ollama connection refused

Symptom

Health Check shows ❌ Connection refused for Ollama.

Cause

• Ollama is not running.
• The endpoint URL is wrong.
• Ollama is on a different host and not accessible.

Fix

1. Start Ollama: ollama serve.
2. Verify it's listening: curl http://localhost:11434/v1/models.
3. If running in Docker or on a different machine, update the Ollama Base URL in Configuration.

"Extension not found" or upload failure

Symptom

Joomla shows "Extension not found" when uploading the package zip.

Cause

PHP upload_max_filesize or post_max_size is smaller than the zip file (249 KB — should not normally be an issue).

Fix

Check your php.ini or .htaccess:

upload_max_filesize = 8M
post_max_size = 8M

Chat widget not appearing in WP admin

Symptom

The floating chat button does not appear in the WordPress admin footer.

Cause

• The plugin is not activated.
• The current admin screen is in the widget's exclusion list.
• A JavaScript error on the page is preventing the widget from initialising.

Fix

1. Confirm the plugin is active in Plugins → Installed Plugins.
2. Check Settings → Widget → Excluded screens — the current screen may be listed.
3. Open your browser's developer console (F12) and check for JS errors.
4. Navigate to a known-good screen like the Dashboard and check if the widget appears there.

"Schema version mismatch" in Health Check

Symptom

Health Check → Database shows a schema version mismatch warning.

Cause

The database was not updated when the plugin was upgraded.

Fix

Reinstall the package via System → Extensions → Install (Joomla) or upload via Plugins → Add New (WP). The install script will run pending migrations.

Budget "block" action not working

Symptom

Users continue to generate content even after a budget cap is reached and the action is set to "block".

Cause

Budget rules are evaluated per-request. If the cap was set after some requests already completed, those are not retroactively blocked.

Fix

Set the cap to a lower value. Budget enforcement works correctly for new requests once the cap is in place and the usage counter reaches it.

_Last updated: 2026-05-19 · v2.5.3_