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
Illegal length modifier specified 'f' in s[np]printf call in FilesystemCache.php #16613
Comments
@mattab I'll close this for now as we upgraded to a new major twig version in Matomo 4 so this might be fixed. Also we can't fix this ourselves anyway and be best to otherwise create an issue in the twig repository if this happens again in Matomo 4. The sprintf calls look actually good/standard to me. |
fyi got another report from a different user Illegal length modifier specified 'f' in s[np]printf call in /home/public_html/vendor/twig/twig/src/Cache/FilesystemCache.php 65 using PHP 7.2.33 |
see https://stackoverflow.com/questions/61861990/illegal-length-modifier-specified eg switching to PHP 7.4 seems to make the error go away. Same in https://www.drupal.org/project/drupal/issues/3152749 |
I talked a bit about this issue here: It might be some weird PHP bug where |
I'm using Matomo v4.3.1. I absolutely still get this error message constantly, and it renders most of the analytics unusable. |
@thinkhuman I would strongly recommend you to update your PHP version to newer version that doesn't contain this weird bug. |
@Findus23 Thanks Lukas. I'd already tried that--running 7.4. No change in error messages. Bug still exists, as far as i can tell. |
@thinkhuman Maybe the comments from https://stackoverflow.com/questions/66281360/error-illegal-length-modifier-specified-f-in-snpprintf-laravel and https://chat.stackoverflow.com/rooms/228965/discussion-between-muresan-andrei-and-gerardo-marroquin help you (that's one of the few places on the internet where I can find information about this bug) |
@Findus23 I'm running Matomo at my hosting provider--not hosted/onsite. Here's the diagnostics dump:
|
@thinkhuman Seems you are using Matomo for Wordpress. In this case it might be some incompatibility with another wordpress plugin maybe. Might be good to create a new issue here: https://github.com/matomo-org/matomo-for-wordpress/issues |
Got this error reported by email:
in Matomo 3.13.6
The text was updated successfully, but these errors were encountered: