Hi @byukusenge,
Thanks for reaching out. I’m sorry for the trouble here.
I noticed you commented on the post https://wordpress.org/support/topic/call-to-undefined-function-monsterinsights_get_ua_to_output/ and it sounds like the issue you’re experiencing is an error coming from the WooCommerce Google Analytics Pro plugin, is that correct?
As mentioned in that thread, since Universal Analytics is going away very soon, we at MonsterInsights have taken proactive measures to prepare for this transition, such as removing certain UA events that are no longer necessary. Any third-party plugin relying on those events will need to be updated by their respective developers to ensure compatibility.
Since the error you’re experiencing is being generated by another plugin on your WordPress site, please reach out to the support team or the developer of the specific plugin causing the error. They will be in the best position to assist you further and provide the necessary updates to resolve the compatibility issue.
If you have any additional questions or need further assistance, please feel free to let us know.
Thanks!
Michelle D.
(@devmich), yes, that’s very logical and understandable but please, why didn’t u warn us before making any update??now, my sites are down cause, i did not know about this vulnerability and i’ve got a very big day today to work on it again.
Hi there,
The issue is the other plugin you have is calling one of our plugin’s functions — it’s not our code that’s causing the site issue.
There’s no way for us as a plugin developer to know if another plugin is calling one of our functions.
That being said, we’ve supported the new V4 version of Google Analytics since Sep 14, 2021, and Google’s deprecation and removal of v3 support was announced on Mar 16, 2022 with the date it was going to be sunset on so that particular plugin has had a ton of time now that they could have and should have switched to our V4 Google Tag function — almost 2 full years now.
It looks like based on the reviews of the WooCommerce plugin that they waited until very very recently to try to make their plugin work with GAv4 and they simply overlooked this aspect of their plugin when they rewrote their plugin recently for this.
We’ve sent them an email so they are aware of the issue in their plugin’s code so that they can push out an update to fix it.
chriscct7
(@chriscct7), thanks alot. so, as an expert developper, what do u suggest we do now?i mean, for the people who have not updated your plugin yet and for those who have pressed the “update”button already and their sites down now.
If the site is currently down:
I would recommend deactivating the WooCommerce GA plugin until it is updated by their team to fix the issue.
If you are comfortable and familiar with WP CLI, you can use the normal plugin deactivation command to deactivate the WooCommerce Google Analytics plugin.
If you are comfortable and familiar with FTP, renaming the wp-content/plugins/woocommerce-google-analytics-pro folder will deactivate it automatically.
If you have never heard of FTP or WP CLI or if you are not comfortable with using them, what you can do is ask your website hosting provider’s support to rename the folder wp-content/plugins/woocommerce-google-analytics-pro to a different name, they can do that for you and it will deactivate the plugin, solving the immediate issue. They can also deactivate the plugin using WP CLI.
If the site is not currently down:
In order:
- Deactivate the WooCommerce GA plugin
- Update MonsterInsights to the latest version
- Keep the WooCommerce GA plugin disabled until it is updated by their team to fix the issue.
-
This reply was modified 2 months, 3 weeks ago by
chriscct7.
-
This reply was modified 2 months, 3 weeks ago by chriscct7.
-
This reply was modified 2 months, 3 weeks ago by chriscct7.
