I have the same issue. When reloading the page, I can see the correct content for a very short time, so it is there, just not displayed.
Console shows this error:
index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41
TypeError: Cannot read properties of undefined (reading 'length')
at tagManagerHelper.truncateText (index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:2467:308)
at Proxy.truncateText (index.php?module=Proxy&action=getUmdJs&chunk=2&cb=37e17f08aed1fad5bb53fd683ea0ef26:100:8430)
at index.php?module=Proxy&action=getUmdJs&chunk=2&cb=37e17f08aed1fad5bb53fd683ea0ef26:100:3023
at e.renderList (index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41:121877)
at index.php?module=Proxy&action=getUmdJs&chunk=2&cb=37e17f08aed1fad5bb53fd683ea0ef26:100:2684
at o (index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41:14442)
at e.renderSlot (index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41:122378)
at Proxy.Qn (index.php?module=Proxy&action=getUmdJs&chunk=0&cb=37e17f08aed1fad5bb53fd683ea0ef26:275:966)
at Dt (index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41:14750)
at fe.fn (index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41:40794)
(“Variables” page works, but shows the same error in console.)
From the Dashboard page I can open the page to create a new trigger. But if I try to save a new trigger, it doesnt work. Instead thees is an error (on ppage):
× SQLSTATE[42S22]: Column not found: 1054 Unknown column 'description' in 'field list'
this error also pops up in console (in addition to above error):
Uncaught (in promise) Error: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'description' in 'field list'
at index.php?module=Proxy&action=getUmdJs&chunk=0&cb=37e17f08aed1fad5bb53fd683ea0ef26:104:8787
(anonym) @ index.php?module=Proxy&action=getUmdJs&chunk=0&cb=37e17f08aed1fad5bb53fd683ea0ef26:104
load (asynchron)
send @ index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:6
ajax @ index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:6
value @ index.php?module=Proxy&action=getUmdJs&chunk=0&cb=37e17f08aed1fad5bb53fd683ea0ef26:104
value @ index.php?module=Proxy&action=getUmdJs&chunk=0&cb=37e17f08aed1fad5bb53fd683ea0ef26:104
value @ index.php?module=Proxy&action=getUmdJs&chunk=0&cb=37e17f08aed1fad5bb53fd683ea0ef26:104
value @ index.php?module=Proxy&action=getUmdJs&chunk=0&cb=37e17f08aed1fad5bb53fd683ea0ef26:104
value @ index.php?module=Proxy&action=getUmdJs&chunk=2&cb=37e17f08aed1fad5bb53fd683ea0ef26:57
createTrigger @ index.php?module=Proxy&action=getUmdJs&chunk=2&cb=37e17f08aed1fad5bb53fd683ea0ef26:64
Wn.Object.default.Object.onConfirm.t.<computed>.t.<computed> @ index.php?module=Proxy&action=getUmdJs&chunk=2&cb=37e17f08aed1fad5bb53fd683ea0ef26:64
Rr @ index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41
Fr @ index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41
It @ index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41
onConfirm @ index.php?module=Proxy&action=getUmdJs&chunk=0&cb=37e17f08aed1fad5bb53fd683ea0ef26:629
Object.onClick.t.<computed>.t.<computed> @ index.php?module=Proxy&action=getUmdJs&chunk=0&cb=37e17f08aed1fad5bb53fd683ea0ef26:629
Rr @ index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41
Fr @ index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41
n @ index.php?module=Proxy&action=getCoreJs&cb=37e17f08aed1fad5bb53fd683ea0ef26:41
Edit: maybe it’s easier to read on a screenshot:
using:
Matomo-Version: 4.12.2
MySQL-Version: 10.3.36-MariaDB
PHP-Version: 8.0.24
Edit2:
- I dont know if it’s because my last update raised problems: I couldnt use my installation after update. I posted about it here: Upgrade 4.12.1 → 4.12.2 bricked our matomo - Support & Bugs - Matomo forums
re-copying the files solved that problem. but maybe it caused this here? - I ran
./console core:update
to make sure DB is ok, but it says “everything is up to date”.