SEO is the easy path to attract shitloads of people to a meetup.
We still have issues finding people to speak, topics they are willing to talk about as well as other people are interested in. SEO always worked. Sigh.
@Rarst I wanted to register a shutdown function before the plugins loaded to catch anything that may go awry so I put it in a plugin assuming I could run the muplugins_loaded hook but now realize it's silly, because my plugin has to load to get to the hook and will be too late.
I think in the end ima package a MU file and just move it to the MU directory when my plugin updates / installs
As in, do_action( 'shutdown' ) or registering my own shutdown function is way late? I'm trying to catch plugins that may fail on install ( causing anything fatal ) so I figure I need to register my own shutdown function before any plugins are loaded - I.E. MU
Or maybe I misunderstand how the shutdown functionality works.
@MarkKaplun Yeah, we keep logs on for all our sites but the shutdown is just to get a devs attention that something went wrong. A file is created to act as a flag which must be removed upon inspection so they don't get spammed with tons of emails.
All in all it ties back into a monitoring system so we can manage / view it all in one location.
Granted, could have used a remote service for all that but then I wouldn't have learned anything :)
Well, I'm specifically looking for fatal errors with the register function
Even some fatal errors don't bring down a site though so I've seen false positives from time to time but usually get a chance to report them to the plugin dev.
It is but we don't get emails don't get generated from it - so we would have to manually go to each error log to even see if something went wrong ( or a call from a client ).
IMO you should get an email for each error. I am sure there are linux tools that do that. I don't see why critical error is more important after plugin upgrade then in any other time ;)
I feel like if we were to get emails for each error we would get flood with small potatoes. Especially things we don't necessarily have control over like a plugin not verifying an index exists before using it.
If there is a critical error with a plugin we can at least take measures at that point to debug / deactivate it and let the author know - keeps the website up and running ( assuming it's not a critical plugin like Woo or something ).