Question Migrating custom modules beyond webtrees 2.2.6: GuzzleHttp replaced

In the next webtrees version (2.2.7 or 2.3), GuzzleHttp will be replaced by symfony/http-client, see commit 49cbec6

From my test environment with the latest webtrees code, I can see that many custom modules will need to be adjusted:

• German Chancellors Presidents
• Wars and Battles Worldwide
• Gramps Historical Facts
• Sosa-Stradonitz
• Topola
• Watermark module
• Descendants chart
• Fan chart
• Pedigree chart
• FaviconUpdater
• Statistics
• ...
• All my own Jefferson49 modules

This list might not be complete, because it only contains the modules, which I observed directly creating errors at boot time or if being used within Custom Module Manager.

The code in the updated  ModuleCustomTrait.php , shows a blueprint how a HTTP client, request, and response can be used in the upcoming webtrees releases.

It is also possible to keep custom modules compatible to GuzzleHttp until webtrees 2.2.6 and use the new code beyond 2.2.6. I have already tested this in the code of my own custom modules, which can be found here .



 

The kind thing to do, is open an isssue (or make a PR) at the github repos of the affected modules. It's better fixed now, before the next release of webtrees.

I have seen modules fetching latest versions themselves. Must all be based in an old bad example.
If you "use ModuleCustomTrait" then it suffices to supply a url for your latest version, and webtrees core will take care of the rest.
See github.com/BertKoor/wt-module-custom-vie...mViewsModule.php#L81

webtrees 2.3.0 will have LOTS of breaking changes

I guess that most third party modules will be affected.

In most cases, things are just being done differently, rather than removing functionality.

I have written some documentation covering the main points webtrees.net/develop/2.3-changes
I can expand this to cover any specific questions.

Expect APIs to keep changing for the next few weeks...

At that point, I'll publish 2.3.0-beta1, and continue working on non-breaking changes for another month or so. This will give third-party developers a chance to test/update their modules before the actual 2.3.0 release.

Nice tech speak, Greg. Just give us some implementation of the UK 1921 Census after all this time ...

Bootes wrote:

Nice tech speak, Greg. Just give us some implementation of the UK 1921 Census after all this time ...
 

Hey there

There is a small zip package available to 'implement' something for the 1921 Census. Please DM me or email. I can send it to you..
The main issue with inclusion of this is that it does NOT cover ALL columns etc for the Census.. 
 

fisharebest wrote:

webtrees 2.3.0 will have LOTS of breaking changes

I guess that most third party modules will be affected.
 

I just did a complete analysis of my modules, and I can say: yes, all my modules are affected in several ways. Up to now, no serious problem has shown up. I will be able to offer all my modules in a way that they are compatible with webtrees 2.2 and 2.3, but it will need some time.