diff options
| author | Lukas Winkler <git@lw1.at> | 2020-04-08 13:30:16 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-08 13:30:16 +0300 |
| commit | 2c5c72e2da4c015efa78069c9c1b407fc55a6483 (patch) | |
| tree | fecec8638249689fb02b93a883517cc7c64f52d6 /plugins/SegmentEditor/tests | |
| parent | bb4cad6d756e119f92f397a8dd4574d0d1bf539c (diff) | |
many typo fixes in the code thanks to codespell (#15730)
* many typo fixes in the code thanks to codespell
* reset submodules
I really need to stop using `git commit -a`
* reset change in library
* rebuilt piwik.js
* fix test
* updates expected UI file
Co-authored-by: sgiehl <sgiehl@users.noreply.github.com>
Co-authored-by: Stefan Giehl <stefan@matomo.org>
Diffstat (limited to 'plugins/SegmentEditor/tests')
| -rw-r--r-- | plugins/SegmentEditor/tests/System/expected/test___VisitsSummary.get_customSegmentUnprocessed.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/plugins/SegmentEditor/tests/System/expected/test___VisitsSummary.get_customSegmentUnprocessed.xml b/plugins/SegmentEditor/tests/System/expected/test___VisitsSummary.get_customSegmentUnprocessed.xml index ed4fec1ebd..dcffffeaea 100644 --- a/plugins/SegmentEditor/tests/System/expected/test___VisitsSummary.get_customSegmentUnprocessed.xml +++ b/plugins/SegmentEditor/tests/System/expected/test___VisitsSummary.get_customSegmentUnprocessed.xml @@ -1,4 +1,4 @@ <?xml version="1.0" encoding="utf-8" ?> <result> - <error message="The Segment you requested has not yet been created in the Segment Editor and so the report data has not been pre-processed. To see data for this segment, you must go to Matomo and create this segment manually in the Segment Editor. (Alternatively, you can create a new segment programatically using the SegmentEditor.add API method). Once created the segment in the editor (or via API), this error message will disappear and within a few hours you will see your segmented report data, after the segment data has been pre-processed. (If it does not, there may be a problem.) Please note that you can test whether your segment will work without having to wait for it to be processed by using the Live.getLastVisitsDetails API. When using this API method, you will see which users and actions were matched by your &segment= parameter. This can help you confirm your Segment matches the users and actions you expect it to." /> + <error message="The Segment you requested has not yet been created in the Segment Editor and so the report data has not been pre-processed. To see data for this segment, you must go to Matomo and create this segment manually in the Segment Editor. (Alternatively, you can create a new segment programmatically using the SegmentEditor.add API method). Once created the segment in the editor (or via API), this error message will disappear and within a few hours you will see your segmented report data, after the segment data has been pre-processed. (If it does not, there may be a problem.) Please note that you can test whether your segment will work without having to wait for it to be processed by using the Live.getLastVisitsDetails API. When using this API method, you will see which users and actions were matched by your &segment= parameter. This can help you confirm your Segment matches the users and actions you expect it to." /> </result>
\ No newline at end of file |