Question New releases of webtrees

> It would also be helpful if all 3rd-party modules were marked in the module overview in the control panel

They are.



Dependency management is a difficult problem.

> Also a simplification would be the possibility to update customer modules automatically

At present, webtrees only has write permission to the /data folder. So, we'd need to store the modules there.

I think the main difficulty is that each module author would need to maintain a compatibility table, showing which versions of which module are compatible with which versions of webtrees.

ric2015 wrote:

In general, module compatibility should be handled better in webtrees. Unfortunately this doesn't seem to be a priority though, until more users ask for it.

I think this is already an issue. I think that the Vesta modules are widly used and these modules go (from my point of view) very deep so every change in core code cann bring up "problems".

Is there a statistics how many instalations use Vesta modules? According to the statistics there are 577 webtrees instalations in Germany (out of 2269) and I think that Vesta modules are very popular in Germany becouse of GEDCOM-L and GOV.

fisharebest wrote:

I think the main difficulty is that each module author would need to maintain a compatibility table, showing which versions of which module are compatible with which versions of webtrees.

That's the idea. Incompatible modules could then be disabled automatically, or at least produce warnings. This could be optional: The handling of custom modules that do not support this wouldn't be worse than before.

Vesta modules already provide such a compatibility table ( see this example ), in order to show a warning when webtrees is upgraded via the control panel.

Edit: See also this open issue in general and the comment here .

fisharebest wrote:

At present, webtrees only has write permission to the /data folder. So, we'd need to store the modules there.

An academic question - I do not understand this answer. How works the automatic upgrade of webtrees? The code for it is not only in /data folder - so there is a way to copy files also outside the /data folder. Or am I wrong?

@ric2015 and Peter_S
Sorry for making trouble!
With earlier automatic updates there was an info when I started the update concerning not compatible modules. Then I deactivated them. This Time there wasn't this warning so I went on, (to "safe" time - no good idea ...) Sorry!
On the control panel at "others" some of the 3rd party modules are shown, but not all. And its neither possible to activate/deactivate them there nor to update them directly. For those under "others" there at least is the link to find the update, which makes it a little easier.

So a more comfortable method would be great, if possible.
Thx!
Andreas

anjop wrote:

This Time there wasn't this warning so I went on

I'll check whether there is a problem with this functionality - The warning should have shown up in this case as well!

anjop wrote:

jprause wrote:

anjop wrote:

The display of the main page is ok, but the on the individual pages the right column get so narrow. I tried standard theme and others.

You are probably using a custom module vesta_classic_laf.
Please try to disable it.

You are right!
I disabled the "compact mode" in the vesta_classic_laf and now it's ok.

I disabled compact mode on my site, went to an INDI page, and refreshed. Still too narrow. I have "clouds" theme, if that matters.

I have just released webtrees 2.1.3

Details can be found here: webtrees.net/blog/

Hello Greg,
anything you can do to improve the automatic updates?
On a shared hosting env. you can not tweak certain timeouts.
During the update as we discovered last time, we seem to run into one.
...
Download github.com/fisharebest/webtrees/releases.../webtrees-2.1.3.zip…
31,434 KB were downloaded in 39.01 seconds.
Unzip webtrees-2.1.3.zip to a temporary folder…
SQLSTATE[HY000]: General error: 2006 MySQL server has gone away …/vendor/illuminate/database/Concerns/ManagesTransactions.php:45
#0 …/vendor/illuminate/database/Concerns/ManagesTransactions.php(45): PDO->commit()
#1 …/app/Http/Middleware/UseTransaction.php(46): Illuminate\Database\Connection->transaction()
...
#40 {main}
I am upgrading manually again
Maybe a Delta release V2.1.x, it seams the 31M is a full release?

First of all thank you for the continued improvements in webtrees.

I am also unable to use the automatic update, similar "MySQL server has gone away" error.

A bit surprised, however, that this error occurs, I would expect that the MySQL database is not need for downloading the zip and/or updating webtrees. Or is this an incorrect assumption?

fisharebest wrote:

I have just released webtrees 2.1.3

Thank you for your permanent good work and continuous improvements.
I've just installed 2.1.4.

THX Greg for new release!
Update worked fine!!!

FransW wrote:

A bit surprised, however, that this error occurs, I would expect that the MySQL database is not need for downloading the zip and/or updating webtrees. Or is this an incorrect assumption?

All database connections use a transaction. This ensures that we can read and write a consistent set of data.

Therefore your database timeout should be longer than your HTTP request timeout / PHP execution timeout.

It is not clear from your post whether the timeout error was in the "download" action or the "unzip" action.

If the latter, then I guess the upgrade was complete - as we only close the database connection after we have unzipped all the files.
So, you probably just need to delete the file data/offline.txt.

fisharebest wrote:

It is not clear from your post whether the timeout error was in the "download" action or the "unzip" action.

I am not sure anymore, I think during the unzip action. Will check with the next version and let you know

I've also the problem with Joomla, because it makes no automatic update.

My provider informed me that the "communication with the server is not blocked".

Because of the problem with WT I checked this:
LATEST_WT_VERSION_TIMESTAMP" shows this result: 1632847453
It was therefore last accessed on Tuesday September 28, 2021
6:44 PM.

I've no idea how I can solve this problem.

Something has to be with the server, because if both, Joomla and webtrees, can't update automatically, the problem must be with the server. In the past it has worked.

What else could I check?

> What else could I check?

webtrees only checks every 24 hours.

Edit the file app/Services/UpgradeService.php, and change the interval from 24 * 60 * 60 seconds to 1 second.
github.com/fisharebest/webtrees/blob/2.1...gradeService.php#L75

If there is an error fetching the file, webtrees ignores it. You can make webtrees fail with an error message by replacing these two comment lines with a new line:

github.com/fisharebest/webtrees/blob/2.1...ervice.php#L335-L336

fisharebest wrote:

If there is an error fetching the file, webtrees ignores it. You can make webtrees fail with an error message by replacing these two comment lines with a new line:

Is it feasible for the catch to (1) change the output HTML to say that it was unable to check for updates and (2) change the time for next attempt to only two hours in the future?

> Is it feasible for the catch to (1) change the output HTML to say that it was unable to check for updates

Most likely, this would be shown to a search engine. We wouldn't want this message to appear in the search results.

Tried again the automatic update to 2.1.14. Had the 40 errors in the unzipping of the files.
Did all the 9286 files change? If not why not have have different upgrade options? 2.1.x to 2.1.14 and just have those files in the automatic update.
Ftp took about 45min to upload with 5 threads the 9286 files.
Just wondering if there are any other options.
Its not a perfect example but nevertheless I think it shows what I mean.
Example:
Joomla! 4.1.4 Upgrade Package (.zip) 24MB
This package is for performing updates from Joomla! 3.10 and previous 4.x releases to 4.1.4.
versus
Joomla! 4.1.4 Full Package (.zip) 26MB
This is the full download package for Joomla! 4.1.4

> Did all the 9286 files change?

All the language files will change - approx 12.5MB
All the CSS/JS files will change - approx 2.5MB
Many of the third-party library files will change.
At the start of the year, all files will change to update the copyright date.

> If not why not have have different upgrade options?

The auto-upgrade has a "cleanup" option. Any files on the disk that are not part of the new release get deleted.

So, as well as creating a difference between two ZIPs, I'd also need to create a manifest file.

So, all this is all possible, but I have finite time and other priorities.

I would also need to consider the time I would spend on support-requests from people who
used the wrong installer, etc.

> Ftp took about 45min to upload

Many FTP clients (e.g. FileZilla) have an option to only upload files that have changed.
So, you can easily upload just the files that have changed.

However, 45 minutes!

My server downloads the .ZIP file in 1-2 seconds, and unzips it in 2-3 seconds.

If your server's speed/bandwidth is that low, I wonder how well it can run your site?

> Example:
> Joomla! 4.1.4 Upgrade Package (.zip) 24MB
> Joomla! 4.1.4 Full Package (.zip) 26MB

24MB / 26MB?

IMHO, the difference is too small for all the effort of creating and maintaining two upgrades.