Hi Jeremy,
It looks like GoDaddy already includes (not clear if they are using it or not) the Sentry SDK.
Unfortunately there is not much I can do about this… I don’t know what the GoDaddy plugin does or how needed it is but the two plugins cannot be installed together.
Alex – thanks for the quick reply, and thanks for the plugin. Love it!
seems like this plugin would need to use something like these to get around the “redefinition”.
https://github.com/Interfacelab/namespacer
https://github.com/humbug/php-scoper
https://github.com/TypistTech/imposter
Are you open to trying one of these? I’m happy to make the PR.
Sorry. No. We already are actually using one of those for our own dependencies. The problem is that this is the Sentry plugin, namespacing our own SDK makes no sense and is also hard to explain to people why they can’t use the PHP docs because every function is called differently because they are namespaced and/or scoped. And that is even besides the point that having multiple Sentry SDKs has some unknown interactions when handling errors.
Unfortunately this needs to be fixed on the GoDaddy side or you need to use the SDK they include and supply your own DSN which might work if you really wanted too 😅
In all the years maintaining this plugin you are the first with this issue and I don’t think there will be any effort in this plugin to allow this to function any time soon if ever. Hope you’ll be able to work around it!
Horray for me being the first. Honestly, I just want the customer off godaddy. It’s a pain to deal with. Cheers.
I’d of course would never recommend anything so drastic… but yeah.
I guess in a managed environment it might make sense but they could also (by accident) collect a lot of sensitive data from the context Sentry collects if they are actively tracking errors on the site which might or might not be clear.