We have reports that our plugin did result in a blank page after installation, and we've got also bad and unfair ratings just for that. Those users don't seem to be able to read install instructions or requirements and prefer blame us maximum as possible for that. I am somehow quite pissed that this can happen at all on this platform. However, this is what we did:
Follow best practices for wp plugins:
- prefix everything
- make PHP & WP version checks
- test that required PHP extensions are there
- put critical parts in try/catch clauses
- test against at least 10 popular plugins and another 10 crap plugins
- provide a visual requirements checker
- updated: use a virtual PHP renderer as through ob_start
This alone doesn't seem to be enough since there could be still a name collision or other trouble with plugins which load client side resources regardless they are needed (AMD/Require-JS).
I am aware that safe developing for any hosting/wp-setup is impossible due to the nature of PHP and the hoster's own practices in regard of HTTP/PHP setups but I wanted to make sure that I didn't miss anything. For instance, are there more APIs provided by the WP platform to make sure that a plugin can't cause a blank page? I know that fatal PHP errors are difficult to catch or even to avoid, except you bloat your code with endless measures.