I'm looking into integrating something that can help me capture aggregate, and anonymous error monitoring using Sentry for a distributed WordPress plugin. Obviously this would be opt-in.
Is there someone out there who has actually done this who I can chat with? Looking for some insight on things to look out for, how to approach it, etc.
I point to this post also for the #WordPress community who should also have been asking the same question for a number of years even before COVID.
The last couple of months I’ve had numerous discussions on this topic with longtime developers in the community. Those leaving the community for whatever reason or one thing, but not focus on whose entering.
I just noticed that stuff on my blog (which was hosted on URLold and now is hosted on URLnew) still points to URLold.
A quick inspection has shown that this is not a cache issue. When I look into the database, I can see that Wordpress introduced hard links for images like URLold/path/to/whatever/foto.jpg and similar stuff for other content.
The probably dumbest solution would be to replace all appearances of URLold with URLnew using sed or just an editor but ... there must be a better way? They cannot make their users edit the data base when the site migrates from URLold to URLnew. Right?
I need to think a bit about onboarding with Siren. Right now, it kinda just installs the plugin without any context. I don't want to do a full-blown wizard before launch, but maybe a single "getting started" screen would be useful. Hmm.