That is not good. Looking at the code that ended up in the release it looks good: https://plugins.trac.wordpress.org/browser/wp-sentry-integration/tags/8.11.0/build/vendor/sentry/sentry/src/EventType.php
So I’m guessing you have other plugins installed that bring their own Sentry installation possibly?
Thread Starter
morvy
(@morvy)
Of course you are correct … sorry for stressing about it. It was my own plugin, which I haven’t updated for a while. At least I was forced to change the behavior of vendor loading.
I mentioned it somewhere here in threads, using the Log functionality of Sentry by replacing Woo logger. Not sure if this is already covered by your plugin and I believe it’s not the scope of your plugin, so I kept it separate.. https://github.com/morvy/woocommerce-sentry-logger
No worries, it happens. Unfortunately a easy conflict to happen with WordPress.
We are starting to add a few small plugin integrations where it makes sense: https://github.com/stayallive/wp-sentry/tree/master/src/plugins
However, these are usually pretty tiny and just hook in very minimally. So it’s probably better to keep it separate considering the amount of functionality your WooCommerce plugin is providing. Although we could look into small hooks but that won’t cover everything you have today.
You should be able to remove the direct reliance on the Sentry SDK and running \Sentry\init yourself but instead re-using the client from this plugin instead to prevent conflicts. But hey, if it works today there might not be much benefit in switching anything. Just watch out for plugin updates that bump the PHP SDK and ensure your plugin is updated with it to prevent weird issues.
