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

system check complains about lack of UTF8mb4 support when using mysqli adapter #18049

Closed
dominikborkowski opened this issue Sep 22, 2021 · 3 comments
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@dominikborkowski
Copy link

After installing brand new 4.4.1 instance with MYSQLI adapter the system check widget complains about lack of UTF8mb4 support. There is no such warning when PDO adapter is used.

Expected Behavior

No warnings. Presumably MYSQLI is equally supported.

Current Behavior

MYSQL

Possible Solution

Steps to Reproduce (for Bugs)

  1. Perform a fresh new install of 4.4.
  2. select MYSQL adapter
  3. continue through interactive setup
  4. Observe the following warning

image

Your Environment

Using official docker approach:

  • Matomo version: 4.4.1
  • MySQL version: 10.6.4-MariaDB-1:10.6.4+maria~focal
  • PHP version: 7.4.23

I also repeated the same clean install with RDS Aurora (mysql 5.7 compatibility), and observed the same problem.

@dominikborkowski dominikborkowski added the Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. label Sep 22, 2021
@sgiehl
Copy link
Member

sgiehl commented Sep 23, 2021

@dominikborkowski Did you maybe have a look at the full system check and not only the widget. The widget tooltips might sometimes be misleading - see #18006

@dominikborkowski
Copy link
Author

dominikborkowski commented Sep 23, 2021

You're right, the tooltip is misleading, the full system check indicates the same exact problem as seen in the issue you linked:

image

Can we merge this issue with the one you linked? EDIT: On a second thought, I think there is an important distinction. The problem I describe here manifests itself right away after a simple install, not by changing an existing database afterwards.

Cheers!

@sgiehl
Copy link
Member

sgiehl commented Sep 23, 2021

@dominikborkowski I will close this one as duplicate of #18006. It doesn't make a difference if it's a fresh setup or changed database settings.

@sgiehl sgiehl closed this as completed Sep 23, 2021
@sgiehl sgiehl added duplicate For issues that already existed in our issue tracker and were reported previously. and removed Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. labels Sep 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Development

No branches or pull requests

2 participants