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
Awesome, glad I could help. ๐
Customizing Leaflet Widget popup content and appearance.
Thanks! I managed it out with your help. Turns out I had the Leaflet widget allows for a title and description. This have a dropdown menu in the Leaflet settings within the view...
Customizing Leaflet Widget popup content and appearance.
Hi geoma, no need to excuse. I think, now I got it (more or less). Your problem doesn't actually have much to do with the Leaflet module, but you struggle with the combination of...
Parent items won't show on Leaflet Widget.