I disabled ini_set as a preliminary measure due to security concerns, but to my surprise my b2 (4.x) install broke down with several errors connected to /_db.class.php.
Is ini_set required to run b2 at all versions ?
I didnt check the lines but It doesnt make any sense to require ini_set for a blog software to function
Besides some warnings (when display_errors = true), my tests sites appear to work quite well after having disabled ini_set. Is your site completly broken, or just a few views are? Can you send some screenshots or give us more details? Specially to try to reproduce those errors in the current version and avoid them.
The ini_set, as is also widely used in other open source packages, is not supposed to be a blocker, so the most part of the features of your site should work.
Thanks.