Dates are those of the changes in the repository. Every package version carries the same number in the component and in the five plugins.
1.1.6 (10 October 2026)
Version bump aligned with the evoaddons.com licence server. The history records no behaviour changes in this release.
1.1.5 (10 October 2026)
- The updates XML is open, like that of any other Joomla extension. The Download ID is required when downloading the ZIP, and you paste it in Joomla's "Download Key" field.
- The update site URL no longer carries the key.
1.1.4 (10 October 2026)
- The Download ID is pasted only in the Joomla update site. The extension picks it up, activates the domain and copies it to the URL.
- The License tab in the options now shows the licence status.
1.1.3 (9 October 2026)
- New control tools for evoMCP: delete visits by id, delete attribution summaries by id and run the purge now. All three require human approval and support
dry_run.
- The read tools are unchanged and do not return the full IP.
1.1.2 (7 October 2026)
The licence client finds the update site by the product in its URL, not by the extension name. This was needed after the rename to "evo".
1.1.1 (7 October 2026)
The component options title is now translated into the administrator language.
1.1.0 (7 October 2026)
First release of the pkg_evoorigin package, with tiered logging:
- Visit log (level 1), with a truncated IP, a salted hash or the full IP, and a retention period.
- Lead attribution (level 2) through the
onEvooriginLead event.
- Anonymous monthly statistics (level 3), fed by the purge.
- Option to store click identifiers, with a period of their own.
- Option to log only with consent, reading the banner cookie.
- Admin component with statistics, visits and lead attribution, and manual deletion.
- Read-only REST API and read-only MCP tools for evoMCP.
- Privacy plugin to export and delete a user's visits.
- Daily purge as a scheduled task.
- Panel warnings when the configuration is risky.
- All logging ships off.
1.0.0 (6 October 2026)
System plugin that stores the visitor origin in the Joomla session: gclid, UTM parameters and the first-contact external referer. With a configurable session key and own domains. No own cookies, no JavaScript and no database.