If a watchdog entry should be written during a different MySQL table is locked it will fail with MySQL error "Table 'watchdog' was not locked with LOCK TABLES". If a watchdog entry should be written during an open transaction and the transaction will be rolled back, the watchdog entry will be removed as well. Both cases could be avoided if we use a dedicated database connection for writing watchdog entries.
The solution is to declare a dedicated database connection which will not be established until required.
If a watchdog entry is written as part of a transaction it should probably be rolled back with that transaction. But for entries of severity WATCHDOG_ERROR or above we should assume that they should be always written. But his behavior has to be optionally configurable in settings.php.
Original issue: https://drupal.org/node/298768
Recent comments
What a coincidence, I opened the same question as an issue earlier today, https://github.com/backdrop-contrib/tinymce/issues/177
Tiny MCE - Sticky Toolbar
I read several times, I did not understand what you want to do. Perhaps this is my problem. But... Each Content type has own creation form - '/node/add/content_type' (see page '/node/add')....
Creating Submission Forms for Content Types
Thanks, laryn, I have that installed and can upload multiple images from my computer, but it's the "select from image library" (no uploading to the server) function that only allows me to...
Image Library (File) view - select multiple files?