Every `$conf['update_notify_check_period']` (default = 24 hours) Piwigo sends a requests to piwigo.org to list the versions of Piwigo currently available. If the current Piwigo is behind the latest version available on piwigo.org, Piwigo sends an email notification to the webmasters. To make sure Piwigo does not check piwigo.org too often (and sends an email to webmasters), it relies on the configuration parameter `update_notify_last_check` which is written by function `notify_piwigo_new_versions`:

```
conf_update_param('update_notify_last_check', date('c'));
```

If, for any reason, Piwigo fails to write this line in the database, Piwigo may not crash and continue to execute remaining code, thus notifiying webmasters... Even with a read-only database, I haven't been able to fully reproduce this bug, because my Piwigo stops as soon as the `insert/update` in the config table fails. Some users report that it does not crash for them and that they get dozens, or even thousands emails "a new version of Piwigo is available". Perfectly annoying!

https://fr.piwigo.org/forum/viewtopic.php?id=30404
https://piwigo.org/forum/viewtopic.php?id=33511
more than one email notification on new Piwigo version available
This is a GitHub Issue
repo:Piwigo
owner:Piwigo
Title : more than one email notification on new Piwigo version available
Issue date:

--- start body ---
Every `$conf['update_notify_check_period']` (default = 24 hours) Piwigo sends a requests to piwigo.org to list the versions of Piwigo currently available. If the current Piwigo is behind the latest version available on piwigo.org, Piwigo sends an email notification to the webmasters. To make sure Piwigo does not check piwigo.org too often (and sends an email to webmasters), it relies on the configuration parameter `update_notify_last_check` which is written by function `notify_piwigo_new_versions`:

```
conf_update_param('update_notify_last_check', date('c'));
```

If, for any reason, Piwigo fails to write this line in the database, Piwigo may not crash and continue to execute remaining code, thus notifiying webmasters... Even with a read-only database, I haven't been able to fully reproduce this bug, because my Piwigo stops as soon as the `insert/update` in the config table fails. Some users report that it does not crash for them and that they get dozens, or even thousands emails "a new version of Piwigo is available". Perfectly annoying!

https://fr.piwigo.org/forum/viewtopic.php?id=30404
https://piwigo.org/forum/viewtopic.php?id=33511
--- end body ---
