Verification and common problems - Joomla
The test event
In System - DockRay → Options click Send a test event. The plugin sends an event and shows the result without leaving the screen; the status area keeps the result and the timestamp of the last attempt. The event should appear in the panel under Errors for the project the token points at.
Verifying on a real error
The test confirms the connection, not automatic capture. On a test installation raise an error that makes Joomla render an error page - that is what the onError event covers - and check the environment, the time and the request context in the panel.
Common problems
The plugin is installed but reports nothing
Check that it is enabled under System → Plugins - installing an extension does not enable it. Then check the credentials: with no token and no key the plugin stays inert by design.
The connection fields disappeared from the options screen
The configuration source is set to configuration.php only. In that mode the connection fields are hidden on purpose and the values come from constants alone. Switch back to Auto or This screen only if you want to type them in the back end.
The stored token differs from the one I entered
DOCKRAY_TOKEN or DOCKRAY_PRIVATE_KEY is defined in configuration.php while the configuration source is on Auto - and then the constant wins. The status area lists the active constants.
JavaScript errors do not arrive
The collector is off by default - enable Collect JavaScript errors in the plugin parameters. Keep the 16 KB per-report limit in mind as well: a very long stack from a minified bundle can exceed it.
Transactions are missing
Transactions are only produced when the sample rate is above 0, and they close on onAfterRespond. A request cut short before that event - a redirect with exit in another extension, for instance - leaves no transaction behind.
Joomla cache after a plugin update
After updating the extension clear the cache under System → Clear Cache. An old cached page layout may still not contain the browser error collector.
The panel answers 200 but there is no event
A 200 {"success": false} response means the account has used up its monthly error quota. The integration does not treat that as a failure - and rightly so. You can see the quota on the account dashboard; until the end of the month it is counted from recorded usage, so deleting errors does not reset it.
Still not working
Work through the troubleshooting checklist, and if that does not help, write to us. Include the project name, the integration version and roughly when you ran the test: it shortens the way to an answer.