Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP 7.4 & 3.13 Visitors/actions bug #15257

Closed
BraveSauce opened this issue Dec 10, 2019 · 5 comments
Closed

PHP 7.4 & 3.13 Visitors/actions bug #15257

BraveSauce opened this issue Dec 10, 2019 · 5 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@BraveSauce
Copy link

BraveSauce commented Dec 10, 2019

After upgrading to php 7.4 from 7.3, each action recorded from the same visitor gets recorded as a separate visit with the same ID and other details, while the unique user count keeps rising up as the same one user navigates through more pages.

This is happening on a setup that is using image tracking method.

Matomo version latest beta 3.13.0

@tsteur
Copy link
Member

tsteur commented Dec 10, 2019

@BraveSauce any chance you are setting a userId in the image tracking method? As we changed there something in a recent release around that. It might not be PHP 7.4 related

@BraveSauce
Copy link
Author

BraveSauce commented Dec 10, 2019

@tsteur As a matter of fact, I do use uid in the tracking method. I tried to play with _id values paired with my uid to fix this issue but it breaks my c_n values if I use it.

Edit: Looking at my logs this might indeed not be php7.4 related, sorry for the wrong information. Looks like it started hapenning mid November. Any suggestions on how to get the old functionality back?

@tsteur
Copy link
Member

tsteur commented Dec 10, 2019

Do you know if you have maybe trust_visitors_cookies enabled in your config/config.ini.php file?

You mention the solution already basically ideally you would set _id to some 16 characters hexadecimal string. You could for example hash the userId to generate a visitorId for each user. I can't really think of any reasons this could break your c_n values unless you values are not properly URL escaped.

@mattab mattab closed this as completed Jan 21, 2020
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Jan 21, 2020
@BraveSauce
Copy link
Author

For closure, just wanted to report that this issue was fixed in later beta updates without any code changes on my end.

@tsteur
Copy link
Member

tsteur commented Feb 20, 2020

Awesome thanks for letting us know @BraveSauce

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Development

No branches or pull requests

3 participants