I created a report to be sent via email weekly. Tried to adjust it by choosing more fields but the changes are not saved. I do even notice that some of the options with pull-down menu are not available. Once in a while, i do notice that it states “loading data” once I tried to save the changes.
Anyone experiencing similar problems and how can i resolve it ?
It is working fine for me. Do you by chance use some adblocker that is maybe blocking resources needed? Or a server module like mod_security that blocks requests based on some rules?
Can you open your browsers developer tools (F12) and check for errors in the console?
when i press Save after editing on an existing email report , F12 says:
Uncaught TypeError: Cannot read property ‘classList’ of null
at Object.init (dec73.default.include.e52d06.js:19)
at dec73.default.include.e52d06.js:19
asset_manager_core_js.js?v=3.14.0?cb=8675acaa52c59fd34e02c9b0d0b4b445:230 TypeError: jQuery.easing[jQuery.easing.def] is not a function
at Object.swing (asset_manager_core_js.js?v=3.14.0?cb=8675acaa52c59fd34e02c9b0d0b4b445:29)
at init.run (jquery.js:4)
at i (jquery.js:4)
at Function.n.fx.timer (jquery.js:4)
at pb (jquery.js:4)
at HTMLHtmlElement.g (jquery.js:4)
at Function.dequeue (jquery.js:3)
at HTMLHtmlElement. (jquery.js:3)
at Function.each (jquery.js:2)
at n.fn.init.each (jquery.js:2)
(anonymous) @ asset_manager_core_js.js?v=3.14.0?cb=8675acaa52c59fd34e02c9b0d0b4b445:230
asset_manager_core_js.js?v=3.14.0?cb=8675acaa52c59fd34e02c9b0d0b4b445:230 TypeError: jQuery.easing[jQuery.easing.def] is not a function
at Object.swing (asset_manager_core_js.js?v=3.14.0?cb=8675acaa52c59fd34e02c9b0d0b4b445:29)
at init.run (jquery.js:4)
at i (jquery.js:4)
at Function.n.fx.timer (jquery.js:4)
at pb (jquery.js:4)
at HTMLDivElement.g (jquery.![matomo|623x499]js:4)
at Function.dequeue (jquery.js:3)
at HTMLDivElement. (jquery.js:3)
at Function.each (jquery.js:2)
at n.fn.init.each (jquery.js:2)
Any chance you are familiar with editing files in your WordPress? If so, could you edit wp-content/plugins/matomo/plugins/WordPress/WpAssetManager.php and apply the patch as shown in https://github.com/matomo-org/wp-matomo/pull/386/files ?
Be great if you could check if this fixes the issue maybe.