@PeteTrombone
Since we upgraded to version 4.3.1 last July, all new segments are pre-processed. We have
no entry “enable_create_realtime_segments = 0” in config.ini.php.
According to the description the default should be processed in real time. But it is not.
An entry “enable_create_realtime_segments = 1” unfortunately changes nothing.
Our current version is 4.9.0
@sgiehl
Hi @PeteTrombone
Would you mind to explain what exactly your expected behavior would be?
Is it that the preselected value when creating a new segment is pre-processed even if real time segments are enabled?
Before the upgrade, the default setting in the segment menu was "SEGMENTED REPORTS ARE PROCESSED IN REAL TIME".
After upgrade: "SEGMENTED REPORTS ARE PRE-PROCESSED".
Although we did'nt change anything in the settings as described above.
An entry in config.ini.php “enable_create_realtime_segments = 1” unfortunately changes nothing.
We don't want the default "SEGMENTED REPORTS ARE PRE-PROCESSED". However, it cannot be changed.
@PeteTrombone do you have browser archiving enabled?
@sgiehl we have the following settings:
[General]
enable_segments_cache = 0
datatable_row_limits = "5,10,25,50,100,250,500,1000"
minimum_memory_limit_when_archiving = 9500
force_ssl = 1
scheduled_reports_truncate = 500
datatable_archiving_maximum_rows_actions = 1000
datatable_archiving_maximum_rows_subtable_actions = 500
assume_secure_protocol = 1
proxy_uri_header = 1
Ok. Looking at the code that seems clear now:
https://github.com/matomo-org/matomo/blob/d671dcd8771eaaaf22e1432da348967f8d033179/plugins/SegmentEditor/templates/_segmentSelector.twig#L62
The option is not pre-selected if browser archiving is disabled. I guess the reason for that is, that pre-processed segments should be preferred if an archiving cron is running.
The option to chose a real time segment should still be available, right?
What exactly is your problem with having segments preprocessed?