Thanks for the reply.
Tried that, but it tells me “Everything is up to date”
Noticed that there was another update for Matomo to 5.3.1, so I ran that. Will see if that clears out the errors.
where the error message is "The string General_NewUpdatePiwikX was not loaded in javascript. Make sure it is added in the Translate.getClientSideTranslationKeys hook. "
I didn’t update anything, but I got the same error today. Everything is exactly as shown in the screenshot. Strangely, it only happens with Firefox, and not even in private mode. Deleting cookies didn’t help.
Update: Figurerd out that the problem was caused by MetaMask Addon. It causes problems like this on several websites.
Same problem here, or nearly the same. All, or nearly all, strings that require translation are replaced by “The string (name of string here) was not loaded in javascript. Make sure it is added in the Translate.getClientSideTranslationKeys hook.” The main dashboard page shows the blue header at the top but below that just a “Loading data…” throbber that runs forever. As a result Matomo is unusable.
This started shortly after the 5.3.0 update, but not immediately upon the 5.3.0 update. The 5.3.1 update (which I was barely able to do, navigating through the error messages) had no effect on this problem. Running console core:update from the command line gives a message that everything is already up to date.
It happens only in LibreWolf (a Firefox fork) and only on one computer. Firefox on another machine does not show the problem. Much as Toru reported, for me it doesn’t even happen in a private window on the same browser where it happens in non-private mode, and clearing cookies has no effect. Storage Inspector claims that the Web site is storing nothing locally except cookies. Logging out and back in, and starting a new session of the same browser, have no effect. I have ad blocking disabled for the Matomo installation, and at least one of the browsers where it still works has ad blocking enabled. I’ve made no known configuration change at client or server end between when it worked and when it stopped working, although as I mentioned, it did stop working shortly after, not immediately upon, the 5.3.0 update.
After dig into the source code of matomo on Github, I found this file: https://github.com/matomo-org/matomo/blob/f13f61faec48d2cf6151b62822259d6261064f8d/core/Db/Schema/Mysql.php#L335
Then I’m going to compare the table schema in matomo MySQL database, table name matomo_ archive_invalidations (the “matomo_” is the prefix of my table). I learned that the table lost 2 fields: processing_host and process_id.
I don’t know why the Matomo upgrade didn’t upgrade the schema of this table correctlly, and the php <path_of_matomo_dir>/console core:update not detected any issues, instead report everything is up to date.
Here’s my solution to resolve this problem.
USE <YOUR MATOMO DB NAME IN MYSQL>;
ALTER TABLE matomo_archive_invalidations RENAME matomo_archive_invalidations_bak;
CREATE TABLE matomo_archive_invalidations (
idinvalidation BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
idarchive INTEGER UNSIGNED NULL,
name VARCHAR(255) NOT NULL,
idsite INTEGER UNSIGNED NOT NULL,
date1 DATE NOT NULL,
date2 DATE NOT NULL,
period TINYINT UNSIGNED NOT NULL,
ts_invalidated DATETIME NULL,
ts_started DATETIME NULL,
status TINYINT(1) UNSIGNED DEFAULT 0,
`report` VARCHAR(255) NULL,
processing_host VARCHAR(100) NULL DEFAULT NULL,
process_id VARCHAR(15) NULL DEFAULT NULL,
PRIMARY KEY(idinvalidation),
INDEX index_idsite_dates_period_name(idsite, date1, period)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3;
