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] Wrong URL in Matomo after moving site to subdomain #22710

Open
4 tasks done
diginote opened this issue Oct 23, 2024 · 1 comment
Open
4 tasks done

[Bug] Wrong URL in Matomo after moving site to subdomain #22710

diginote opened this issue Oct 23, 2024 · 1 comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. triaged

Comments

@diginote
Copy link

What happened?

Hello,

we started tracking in matomo tag manager for sites on a domain without a ‘www.’ subdomain (e.g. example.com). Later, all pages had to move to the subdomain ‘www.’ (e.g. www.example.com). Unfortunately, the ‘www.’ is still not listed in the visits in Matomo.

What should happen?

Matomo should not try to hide any subdomains because on every subdomain there could be another website.

How can this be reproduced?

you can read the description here: matomo-org/tag-manager#802

Matomo version

5.1.2

PHP version

8.3.13

Server operating system

debian

What browsers are you seeing the problem on?

Firefox, Chrome

Computer operating system

Windows

Relevant log output

No response

Validations

@diginote diginote 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 Oct 23, 2024
@randy-innocraft randy-innocraft added Bug For errors / faults / flaws / inconsistencies etc. triaged and removed 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 Oct 24, 2024
@randy-innocraft
Copy link

Hi @diginote. 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
Bug For errors / faults / flaws / inconsistencies etc. triaged
Projects
None yet
Development

No branches or pull requests

3 participants
@diginote @randy-innocraft and others