After updating to Matomo 4.12.2, we are no longer shown tags and triggers, only in the overview. But again, we can no longer make changes to the tags. How can we fix this problem?
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”.
@User12, did you try to run the core:update
command? did you also try the solution given in the last message by Stefan (try to re-install Matomo and dependencies from a new downloaded ZIP via SSH instead of FTP)?
@soardiac, I don’t understand, in your other post, you wrote you solved your problem…?
Try maybe the solution provided here:
(Manually update backward the version to 12.0 in the database, then run again core:update
)
I found some ticket in the Matomo GitHub:
I solved the problem that I couldnt access matomo because of an error. now I can access matomo, but i found that in tag manager tags and triggers aren’t being displayed and that I can’t edit them. that could however be totally unrelated to my earlier solved issue. (I didnt use tag manager for weeks, so this issue could exist longer than my update to 4.12.2.)
@heurteph-ei ok, I checked those two github posts (one leads to the other), thx for that!
the proposed solution there is:
- Check the version via this query
SELECT * FROM matomo_option where option_name='version_tagmanager'
- Update the
option_value
to4.11.0
if the above query returns4.12.0
or4.12.1
- Manually run the migration by executing
./console core:update
, this should create the missing columns.
So I did step 1, but my DB shows option_value=4.12.2
:
(phpMyAdmin is in german, but you get it I guess)so, what should I do? Should I still try to set
option_value
to 4.11.0 and do core:update
again?
Yes, it seems the update updated the version in DB, but did not apply the migration scripts…
ok, I tried this, works like a charm:
- on DB server (in my case using phpMyAdmin), check the version via this query
SELECT * FROM option where option_name='version_tagmanager'
- Update the
option_value
to4.11.0
. I used this command:
UPDATEoption
SEToption_value
= ‘4.11.0’ WHEREoption
.option_value
= ‘4.12.2’ ANDoption
.option_name
= ‘version_TagManager’ LIMIT 1;
(messy here with the pre-format and the SQL syntax… ) - in matomo command line (ssh), run
./console core:update
and confirm with ‘y’
for me, it is solved. thx @heurteph-ei