matomo-org / matomo-org/matomo-for-wordpress
Can we avoid Matomo Standalone UI being blocked by Microsoft Defender SmartScreen [Please leave a comment if you experience this issue]
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 145
- Forks
- 35
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
Please leave a comment below if you experience this issue
refs https://github.com/matomo-org/matomo-for-wordpress/issues/339
see comment in https://github.com/matomo-org/matomo-for-wordpress/issues/339#issuecomment-1029342598
A user told us that removing the query string "?module=CoreHome&action=index&idSite=1&period=range&date=last30" in the link from the wordpress menu still lead to a warning but it is not blocking anymore.
Goal of this issue is to confirm that by removing those parameters the UI is not fully blocked and people can still navigate to it. We can test this eg using Browserstack.
This would be a small workaround for https://github.com/matomo-org/matomo-for-wordpress/issues/339 which we would still aim to fix completely.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked matomo-for-wordpress issue and the WordPress menu link that adds the CoreHome query parameters. Use BrowserStack or an equivalent browser test to compare the parameterized and parameter-free links. Done means confirming whether removing the parameters avoids a blocking SmartScreen warning while the Matomo UI remains navigable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100