Question New releases of webtrees

> Would/should I not be initiating contact and directly interrogating the update server by looking at that page in Control Panel?

I think, webtrees is not such a "hot" application, that we have to upgrade after minutes.

But a new function / button in control panel "check for new update" would be nice in case of incorrect release.

@Otmar: Wenn ich mich recht erinnere, wurde die Mail-Benachrichtigung mit 2.1 eingeführt - habe gerade meine Benachrichtigung für 2.13 bekommen.

Warius wrote:

I think, webtrees is not such a "hot" application, that we have to upgrade after minutes.

That is correct. But why wait a day after an announcement when a small button can reset the timestamp and initiate a new check?
With every new release, the same questions are asked here on the forum: Why do I still see the old version when the new version is already available?

otmar.mayr wrote:

Automatisches Update funktioniert bei mir schon lange nicht mehr. I habe diese Eintragungen:

LATEST_WT_VERSION 2.0.16|2.0.0|https://github.com/fisharebest/webtre...
LATEST_WT_VERSION_TIMESTAMP 1632847453
...
Hängt das mit meiner alten PHP-Version zusammen?

siehe www.webtrees.net/index.php/en/ :
> webtrees version 2.0.26 was released 27 November 2022. It runs on PHP 7.1 - 7.4. It only receives security updates.
> webtrees version 2.1.13 released 15 December 2022. This supports PHP versions 7.4 - 8.2. This is the latest version of webtrees, and is actively developed and supported.

was heist "alte" PHP version?

otmar.mayr wrote:

Automatisches Update funktioniert bei mir schon lange nicht mehr. I habe diese Eintragungen:

LATEST_WT_VERSION 2.0.16|2.0.0|https://github.com/fisharebest/webtre...
LATEST_WT_VERSION_TIMESTAMP 1632847453

LATEST_WT_VERSION_EMAIL - gibt es bei mir nicht.

Hängt das mit meiner alten PHP-Version zusammen?

1632847453 = 2021-09-28 16:44:13

Your server has not checked for updates for over one year.

Most likely, your server cannot make an out-going HTTP connection.

In your error logs, do you see any messages "Cannot fetch latest webtrees version: ..."

otmar.mayr wrote:

Automatisches Update funktioniert bei mir schon lange nicht mehr. I habe diese Eintragungen:

LATEST_WT_VERSION 2.0.16|2.0.0|https://github.com/fisharebest/webtre...
LATEST_WT_VERSION_TIMESTAMP 1632847453

LATEST_WT_VERSION_EMAIL - gibt es bei mir nicht.

Hängt das mit meiner alten PHP-Version zusammen?

1632847453 = 2021-09-28 17:44:13

In your logs, do you have any errors "Cannot fetch latest webtrees version: ..."

Ja, die Logfiles der webtrees-Installationen sind übervoll.

Ich kann weder mit Joomla noch mit meinen webtrees-Installationen automatische Updates durchführen.

Ich verwende am gleichen Server auch Piwigo, wo die Updates problemlos funktionieren. Wieso funktioniert es bei Piwigo und nicht bei Joomla und webtrees?

otmar.mayr wrote:

Ja, die Logfiles der webtrees-Installationen sind übervoll.

Ich kann weder mit Joomla noch mit meinen webtrees-Installationen automatische Updates durchführen.

Ich verwende am gleichen Server auch Piwigo, wo die Updates problemlos funktionieren. Wieso funktioniert es bei Piwigo und nicht bei Joomla und webtrees?

here is webtrees, not joomla and not piwigo: update for the one will never be equal to the other. So find the reason for webtrees and if it does not work auto, do it manual.!

wie ist die vollständige Fehlermeldung?

Hast du ein "Cannot fetch latest webtrees version. cURL error 60: SSL certificate problem: unable to get local issuer certificate Problem? Aber ich glaube bei 2.0 war die Fehlermeldung noch nicht detailliert; der Fix kam erst vor ca. 3 Monaten in 2.1.

Für das cURL Problem ist hier die Lösung github.com/fisharebest/webtrees/issues/4565 .

Peter_S wrote:

Warius wrote:

I think, webtrees is not such a "hot" application, that we have to upgrade after minutes.

That is correct. But why wait a day after an announcement when a small button can reset the timestamp and initiate a new check?
With every new release, the same questions are asked here on the forum: Why do I still see the old version when the new version is already available?

I would personally like to see such a capability. However, there is a downside: if a release turns out to have a serious bug not found until just after release, the one-day delay might reduce the number of people that get bit by it.

WGroleau wrote:

I would personally like to see such a capability. However, there is a downside: if a release turns out to have a serious bug not found until just after release, the one-day delay might reduce the number of people that get bit by it.

Arguably the autogenerated email notification to site owners that an update exists could safely be delayed for a day or two to address that issue, unless there is some kind of urgency flag associated with the update (serious security vulnerability) - but someone who has made their way to Control Panel to search for updates is likely an 'early adopter' type, who thus has some tolerance for the risks/inconveniences that go with the territory.

ArchPrime wrote:

WGroleau wrote:

I would personally like to see such a capability. However, there is a downside: if a release turns out to have a serious bug not found until just after release, the one-day delay might reduce the number of people that get bit by it.

Arguably the autogenerated email notification to site owners that an update exists could safely be delayed for a day or two to address that issue, unless there is some kind of urgency flag associated with the update (serious security vulnerability) - but someone who has made their way to Control Panel to search for updates is likely an 'early adopter' type, who thus has some tolerance for the risks/inconveniences that go with the territory.

I go to my control panel almost every day, but for other reasons. There's lot more there than the version notice.

Alle fünf Sekunden wird diese Fehlermeldung in die Logfiles meiner webtrees-Installationen geschrieben:

*****************
2022-12-19 09:03:14 error Cannot fetch latest webtrees version. cURL error 60: SSL certificate problem: certificate has expired (see curl.haxx.se/libcurl/c/libcurl-errors.html ) for dev.webtrees.net/build/latest-version.tx...8723a8942a9e&d=mysql

*****************

Mein Provider hat mir geschrieben, dass "alle Funktionen soweit freigegeben" sind. Zu den Fehlermeldungen kam die Antwort: "das liegt an curl und deren cert das Sie nutzen. Leider bieten wir keine Möglichkeit an Fremdzertifikate via php.ini zu 'whitelisten'."

Dein PHP nutzt kein Zertifikat.

Es fehlt in der PHP.Ini

curl.cainfo = “[pathtofile]cacert.pem”

and You have to download cacert.perm and link the file in php.ini siehe github.com/fisharebest/webtrees/issues/4565

if your provider doesn't want to do that - which I don't understand, since it's described that way at PHP.net - a solution should be found in webtrees (download cert.perm, add curl.cainfo = ...) if possible

Mein Provider hat nun in der php.ini den Pfad zum Root eingetragen und mir den File cacert.pem zugesandt. Diesen habe ich ins Root hochladen.

Leider habe ich trotzdem im webtrees-Logfile diese Eintragungen:

2022-12-20 13:47:55 error Cannot fetch latest webtrees version. cURL error 60: SSL certificate problem: certificate has expired (see curl.haxx.se/libcurl/c/libcurl-errors.html ) for dev.webtrees.net/build/latest-version.tx...8723a8942a9e&d=mysql

Was könnte hier falsch sein?

was steht in php info (Verwaltung\Server Information) unter curl

bei mir:
cURL support enabled
cURL Information 7.77.0
...
curl.cainfo <path>\cacert.pem

webtrees 2.1.14 is now available.

See webtrees.net/blog/ for details.

The most important fix is for the bug in "Change family members".
github.com/fisharebest/webtrees/issues/4674

Peter_S wrote:

ArchPrime wrote:

If not, if control panel is going to make an assertion about the existence of updates, should it at least advise the time this was last checked, and the next scheduled check, so as to avoid providing apparently conflicting advice, as I experienced?

I would also welcome this requirement.

Similar to the Windows update in the Windows settings:
Installed version: 2.1.12 - you are up to date
Last check: Today, 00:14

Button: Check for updates

+1

webtrees 2.1.16 is now available. For a list of changes, see webtrees.net/blog/

There is one significant bug fix - if two editors create records with different types at exactly the same time, then they could sometimes be created with the same XREF.



I quite literally fixed this bug in my sleep!

I had spent all evening looking at the code - but could not see the problem, and so went to bed.

At 02:00, I woke suddenly, and in my head was a full and clear understanding of how the code worked, and how it failed under certain conditions - a combination of caching and concurrent access.

I had to write it down quickly, so that I would remember it in the morning

Nice!
I wish I had productive dreams too

Great thanks for the energy you gave to fix that really annoying bug, make it's bad troubles when many concurrent users where updating at the same time, which is my case.
Will need one more last step forward to make me able to identify the damage done - !