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
add disable archiving segment for plugins #18279
Conversation
add disable archiving segment for plugins
add isset check
update disable_archiving_segment_for_plugins to right place
update tests
update wording
update wording and test
update tests
update wording
The last test runs fully passed https://app.travis-ci.com/github/matomo-org/matomo/builds/241828886. the Last update just one wording in global.config.php, I think no need to run the test again. |
@peterhashair changing the config changes one of the screenshots |
@justinvelluppillai right, let me run it again. |
update screen shot
If I see that right, the site specific config would then only work for that specific configuration value, right? Imho we should do it the same way like in tracker config. So it would be available for all values in General section. See matomo/core/Tracker/TrackerConfig.php Lines 28 to 47 in e041784
I'm not sure if it's easy to adjust the config class to support that. Maybe we need to introduce a new class |
@sgiehl right, that makes sense let me do the adjustment. |
move general config to a file
update screenshot
update en and check unsegmented reports
update lang
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@peterhashair Left a couple of comments for smaller improvements. Regarding a UI test: I guess it would be good to have one, as it would also be kind of an integration test, as it ensures that tracked data isn't archived and displayed. Besides that guess it should be ready to merge after the adjustments
# Conflicts: # plugins/CoreHome/CoreHome.php # plugins/Dashboard/tests/UI/expected-screenshots/Dashboard_removed.png # tests/UI/expected-screenshots/Theme_home.png # tests/UI/expected-screenshots/UIIntegrationTest_dashboard1.png
Co-authored-by: Stefan Giehl <stefan@matomo.org>
Co-authored-by: Stefan Giehl <stefan@matomo.org>
add screenshot tests
…rg/matomo into m-18134-archiving-configuration
set up site
update config
update to overwrite
update screen shot
update config
update screen
# Conflicts: # tests/UI/expected-screenshots/UIIntegrationTest_admin_diagnostics_configfile.png
update screenshots
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@peterhashair it seems you have updated a couple of screenshots that are unrelated to this issue. The updater screenshots are failing for a specific reason, and they should work again, once that issue is fixed. So the changes to them should be reverted. Also you added tests/UI/expected-screenshots/DisablePluginArchive.png
, which is not used.
public function setUp(): void | ||
{ | ||
$this->setUpWebsitesAndGoals(); | ||
$this->setUpConfig(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good to also track some visits in this fixture, maybe one or two with different referrers. That would ensure that no archiving is done. Otherwise the reports would show the data...
update unrelated screenshots and update tests
@sgiehl right, update below. I am not too sure the refer tracking is correct, copied from other fixtures.
|
@@ -11,6 +11,7 @@ | |||
"CloseWidgetDirections": "You can close this widget by clicking on the 'X' icon at the top of the widget.", | |||
"ChooseX": "Choose %1$s", | |||
"DataForThisReportHasBeenPurged": "The data for this report is more than %s months old and has been purged.", | |||
"DataForThisReportHasBeenDisabled": "Segmentation is currently disabled for this report. Please check %1$sthis FAQ%2$s for more details.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tsteur Not sure if this will be a feature we are going to use on cloud maybe. In that case I was wondering if linking an FAQ in the message would actually be helpful, as the user can't change that 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The remaining failing tests seem unrelated, so should be good to merge now. Left a comment regarding cloud, so might be good to wait for an answer.
@sgiehl linking to an FAQ be great, the FAQ could also mention specifically the cloud that if they are on the cloud, to reach out to our support. |
@peterhashair I have merged in the latest changes from |
Description:
Fixes: #18134
add disable archiving segment configuration for plugins
[General]
->disable_archiving_segment_for_plugins
accept string, sting with comma, array.[General_{siteId}]
can be enable by Site ID.I guess this will be 4.7
Review