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
Matomo falsely says a segment will be preprocessed when browser archiving is disabled & enforced #13000
Comments
Or alternatively, Matomo needs to actually pre-process all segments. |
Good find!
For now I would just fix the bug itself. Maybe we could also actually pre-process all segments eventually (but let's create another issue). |
We'll implement that when |
Just looked through the code and if I see that correctly that was already implemented I think with #15499 |
@sgiehl I don't think so, if a segment is set to processed in real time and |
Isn't that what this code should do: matomo/core/CronArchive/SegmentArchiving.php Lines 318 to 321 in 85e665e
|
Yes, which means this has been implemented for quite a while. Tested locally and it works as @tsteur describes, so I'll close this for now. |
When you configure segments with "real time archiving" and only later enable "enforce disable browser archiving" so that segments are only processed during cli archiving, then it still shows "AND 1 RESULT IS AVAILABLE, USE UP AND DOWN ARROW KEYS TO NAVIGATE.SEGMENTED REPORTS ARE PRE-PROCESSED (FASTER, REQUIRES CRON)" for these segments even though they are not being pre-processed.
You can reproduce this by creating a regular segment "processed in real time". Then add the following config settings:
This is not only problematic when people enable this setting later, but it could be also problematic when moving / migrating a DB to another Matomo where this setting is disabled.
The text was updated successfully, but these errors were encountered: