[ticket/14257] Reparse after update
* Elsensee/ticket/14257:
[ticket/14257] Add tests for reparser manager
[ticket/14257] Fix CLI reparser and set cron interval
[ticket/14257] Fix CLI error message
[ticket/14257] Fix phpdoc in CLI command
[ticket/14257] Add text_reparser manager
[ticket/14257] Use migrations instead of cron job for some reparsers
[ticket/14257] Fix lock acquire in CLI command
[ticket/14257] Fix if condition
[ticket/14257] Add reparse_lock to CLI command
[ticket/14257] Add cron tasks for reparsing text
* prep-release-3.2.0-a1:
[prep-release-3.2.0-a1] Add changelog for 3.2.0-a1
[prep-release-3.2.0-a1] Add migration for 3.2.0-a1
[prep-release-3.2.0-a1] Update version to 3.2.0-a1
[ticket/14044] Deduplicate the installers
* CHItA/ticket/14044:
[ticket/14044] Add config as global in notify user
[ticket/14044] Fix language selection data loss
[ticket/14044] Patch language::set_fallback_array()
[ticket/14044] Fix tests
[ticket/14044] Fix wrong descriptions in install
[ticket/14044] Solve missing email template error
[ticket/14044] global $table_prefix in constants.php
[ticket/14044] Try to fix missing table prefix
[ticket/14044] Use the correct language file version
[ticket/14044] Automatically trigger rollback on insert in transaction
[ticket/14044] Use empty instead of !count
[ticket/14044] Fix Sqlite error in tests
[ticket/14044] Deduplicate the installers
Currently, the unique way to disable the update of session_page is to pass
"false" to the parameter of session_begin(). This method is directly
called in app.php, so pages served from the routing system can't disable
the update of session informations.
By moving the update to page_footer, we can allow controllers to tell to
the session manager that we don't want to update the session infos.
PHPBB3-14261
This will cause the sqlite3 driver to automatically rollback transactions
if an insert fails during a transaction. Other dbms trigger a rollback
inside the sql_error() function with a rollback command. However,
this manual rollback command might fail on sqlite3 due to ongoing queries.
With this change, sqlite3 itself will abort any ongoing queries and
initiate the rollback automatically. Since manually triggered rollbacks
will fail after the rollback was started automatically, we catch
exceptions output by the exec() command during rollback and any exception
that might be thrown by fetchArray() due to aborted queries.
PHPBB3-14044
