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
[UI]update invalid archive notification #19126
Conversation
update archive notification
update condition
update condition on message
update error
update unprocessed
update screenshot
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.
Had a look through the code and left some comments. Did not yet do any functional testing
plugins/SegmentEditor/templates/_unprocessedSegmentMessage.twig
Outdated
Show resolved
Hide resolved
update tests and some parts
update phpcs
update tests
update phpcs
I believe the doc is here, https://matomo.org/wp-admin/post.php?post=775&action=edit&lang=en. Adding when PR merged
|
update screen shots
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 message shown can still be improved. Also the linked FAQ is missing. I've added a couple suggestions to improve it. The UI test will need an update as well. And I was wondering if we can't add another UI test that covers the other case.
plugins/SegmentEditor/templates/_unprocessedSegmentMessage.twig
Outdated
Show resolved
Hide resolved
Co-authored-by: Stefan Giehl <stefan@matomo.org>
Co-authored-by: Stefan Giehl <stefan@matomo.org>
update tests ui screenshot
update tests
update ui tests
update tests
update tests
update tests
update tests
update tests
set full config
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.
I've done some functional testing, looks good 👍
There are two failing UI tests related to the segment editor, since this PR makes changes to the segment editor I've pushed an empty commit to rerun the tests in case it's a random failure, if not then we should find out why these tests are failing.
@bx80 that's wired one, will investigate |
@bx80 I believe the UI test's failure is random. |
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 UI test fails are unrelated, so this should be good to merge 👍
(Don't forget to update the FAQ 🙂)
Description:
Fixes: #19011
update invade archive notification caused by config
rearchive_reports_in_past_last_n_months
limitationReview