Lessc compiler interferes with matomo for wordpress
-
One way or the other, both matomo and wp_optimize didn’t correctly shield their less compilers from each other.
I thought we did all the namespacing and composer stuff just to get rid of those errors. Please use your own prefixes (the old fashioned way) for the lessc modules. Now you are interfering with each other!
-
First, thank you for answering, and I noticed my comment was somewhat rude. Appologies!
The matomo plugin (the all in one solution. Maybe I should install a separate piwik and use wp-piwik instead)
The compiled css for the matomo plugin is wrong. When I delete the cache on the server (with sftp), and disable the wp optimize the css will be recompiled again, this time it will be OK. The css is used in the backend, and it does not matter if the caching in wp optimize is enabled or not. I suspect the Matomo will use the lessc compiler from wp optimize. There is a difference in versions (I suppose yours is older). Autoload hell… I really don’t know who is messing this up. I see no error message, but on top of the wrongly compiled css there are selectors like:
/* compile_me_once=9e0c7ad7ece032e70f5f2ff6b64d410d */
/* Matomo CSS file is compiled with Less. You may be interested in writing a custom Theme for Matomo! */
.nonExistingSelectorOnlyForReplacementOfCssFiles { display:”/var/www/html/wp-content/plugins/matomo/app/plugins/Morpheus/stylesheets/base/bootstrap.css”; }
.nonExistingSelectorOnlyForReplacementOfCssFiles { display:”/var/www/html/wp-content/plugins/matomo/app/plugins/Morpheus/stylesheets/base/icons.css”; }
The topic ‘Lessc compiler interferes with matomo for wordpress’ is closed to new replies.
