Skip to content
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

[Bug] API.php(811): Warning - Undefined array key "value" - Matomo 5.2.0 #22881

Open
4 tasks done
mikkeschiren opened this issue Dec 18, 2024 · 2 comments
Open
4 tasks done
Labels
Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. triaged

Comments

@mikkeschiren
Copy link
Contributor

mikkeschiren commented Dec 18, 2024

What happened?

When adding a new measurable of type website, and do not add any urls, you get a warning in the log:

plugins/SitesManager/API.php(811): Warning - Undefined array key "value" - Matomo 5.2.0

What should happen?

No warnings should be in the log when you add a new website

How can this be reproduced?

Install Matomo, activate LogViewer, add a new website, go to to the log, and you would see the log.

Matomo version

5.2.0

PHP version

8.2.26

Server operating system

No response

What browsers are you seeing the problem on?

No response

Computer operating system

No response

Relevant log output

plugins/SitesManager/API.php(811): Warning - Undefined array key "value" - Matomo 5.2.0

Validations

@mikkeschiren mikkeschiren added Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. To Triage An issue awaiting triage by a Matomo core team member labels Dec 18, 2024
@mikkeschiren
Copy link
Contributor Author

Suggested fix: #22882

@randy-innocraft randy-innocraft added triaged and removed To Triage An issue awaiting triage by a Matomo core team member labels Jan 20, 2025
@randy-innocraft
Copy link

Hi @mikkeschiren. Thank you for creating the issue and bringing this to our attention, that's very appreciated. We have reviewed and triaged the problem internally, and we have confirmed it is an issue. Our team will prioritise this, and we will update you on the progress here when we have an update to share. If you have any further information or questions, please feel free to add them here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. triaged
Projects
None yet
Development

No branches or pull requests

2 participants