naturligtvismedia

Thanks a lot, that worked!

So instead of changing the “position:sticky” to the top level block in the header I have to put the hole header in a group and add the position to that group.

I guess this is me not having fully emerged in to the block theme thinking yet, while I have been working with Gutenberg block builder for years now.

I am only testing it locally at this moment, so no link to share unfortunately. But it is a basic installation of twentytwentyfour and I triend it on the top level block of the header (group).

Ok, d? f?r jag leta efter en annan l?sning, tack f?r snabb ?terkoppling!

Det ?r en sp?rnings-cookie, s? den m?ste ju g? att neka till via en cookie-banner enligt lagen? Den ?r ju verkligen inte n?dv?ndig.

Hi @emermatomo
The issue still persists in version 4.15.2

This update you are talking about was released beginning of october and in my last messade from october 13 I already confirmed that the issue persisted after update to the latest version.

• This reply was modified 1 year, 1 month ago by naturligtvismedia.

Hi @emermatomo or anyone else at Matomo,

As suspected, the last update reintroduced the errors again and removed the code I added.

Do you have any plans to solve this problem or a feasible solution for this?

Hi @emermatomo! I still need some more information on this issue.

Best, Anna

Hi @emermatomo!

This seems to work, the errors do not appear anymore.

Uponupdate of Matomo, might this file change and do I then have to add this line again?

What causes these errors in Matomo? I haven’t checked all installations, but all those I have checked do have this issue. It doesn’t seem like a good solution having to add this line to the config file for every installation.

Hi?@emermatomo! I still need some more information on this issue.

Best, Anna

Hi @emermatomo!

Could you please be a bit more specific on where to add this line? I have tried both wp-config.php and /wp-content/plugins/matomo/config/config.php and the first option crashed the whole site, the latter crashed the backend of the site.

Hi! I will have a look at this tomorrow and get back to you with the result.

/Anna

Hi! I still need some more information on this. @emermatomo

I just want to confirm that this issue was fixed in WP 6.2!

Yes, I understand that, and I wrote it worked in incognito mode (= without cache). I have sent a ticket.

Well, it was not confusing that it was the same account (I know very well that it’s both Automattic), but a little confusing that you tell me I might have to create an account, when writing in this thread requires an account ??

Most confusing was that logging in didn’t work and I just got redirected away without being logged in… However it worked in incognito mode now. Thanks!