I figured this out while writing my SQLite3 Cache system for SMF. This actually
seems to be a PHP bug and not related to any code issues but may cause issues
to scripts that request a SQLite database connection in SMF's ob_sessrewrite().
This function is a callback function for ob_start(). It seems like the bug is
in the callback system, which again is related to PHP.
However if a SQLite database connection is requested in the callback function
then the script dies without any output, no error and database never accessed.
This isn't a issue with all SMF sites, just SMF sites with SQLite set as the
database. I don't think there is much of them though.
But as you know your script makes a database connection from within the
callback function. The database layer has access to any numerous databases, but
if the database is SQLite then there is a chance when a user activates Pretty
URL's with a SQLite database the site will become inaccessible and the only fix
is a manual edit to SMF's ob_sessrewrite() function commenting out the Pretty
URLs code.
Original issue reported on code.google.com by sicommn...@gmail.com on 11 May 2012 at 4:52
Original issue reported on code.google.com by
sicommn...@gmail.comon 11 May 2012 at 4:52