Releases: wagoio/WagoAnalytics
0.0.25
0.0.24
Wago Analytics
0.0.24 (2026-01-14)
Full Changelog Previous Releases
- Update Interface-BCC version from 20504 to 20505
0.0.23
0.0.22
Wago Analytics
0.0.22 (2025-04-28)
Full Changelog Previous Releases
- Add support for Mists of Pandarida Classic
0.0.21
WagoAnalytics
0.0.21 (2024-07-08)
Full Changelog Previous Releases
- Bump interface versions, add cataclysm support.
0.0.20
WagoAnalytics
0.0.20 (2024-06-15)
Full Changelog Previous Releases
- Update API's for 11.x Beta
Provides backwards support for existing APIs
0.0.19
WagoAnalytics
0.0.19 (2024-05-17)
Full Changelog Previous Releases
- Move ADDONS_UNLOADING event hook to after login handler
This way, the data will only save if the user has fully logged in and datasets are appropriately defined.
0.0.18
WagoAnalytics
0.0.18 (2023-09-05)
Full Changelog Previous Releases
- Fix :Error function. It should accept string or table references.
0.0.17
0.0.16
WagoAnalytics
0.0.16 (2023-05-04)
Full Changelog Previous Releases
-
Avoid errors when querying unknown addons (#34)
Patch 10.1 applied an extra subtle change to C_AddOns.GetAddOnMetadatathat results in it now erroring if the supplied addon name does not
exist.
If the analytics error handler fails to extract an addon name from the
error message it ends up passing "Unknown" as the addon name, which
is almost always never going to be an installed addon - and as such
will raise an error.
This can be trivially tested from the chat frame via the following,
which will result in two errors - one for the call we're making
ourselves, and one from within analytics directly.
/run C\_AddOns.GetAddOnMetadata("oops")Wrapping things up with a protected call barrier resolves this issue.