vesta-webtrees-2-custom-modules / vesta_common

⚶ Vesta Common (Webtrees 2 Custom Module)
https://cissee.de/
GNU General Public License v3.0
8 stars 3 forks source link

ERROR: Only webtrees versions before 2.1.7 are supported #89

Closed JesseWebDotCom closed 2 years ago

JesseWebDotCom commented 2 years ago

Updated to webtrees 2.1.7 and now all vesta modules are disabled with the following error message: This version of the module is incompatible with your current webtrees version. Only webtrees versions before 2.1.7 are supported. All functionality of the module is therefore disabled.

ric2016 commented 2 years ago

Why do you think this is an error? Is the explanation not clear enough? This is not a rhetorical question - I do not get why people are reporting this when it obviously (to me anyway) works as designed.

JesseWebDotCom commented 2 years ago

No prob :)

From a user perspective, when something stops working (in this case the "expected outcome" is not working because the module is disabled), mentally you think of something is broken. Then when you see a message discussing the break, this is mentally associated with "error". That association is compounded with terms like "incompatible".

From a developer perspective, I understand this is "works as designed by ensuring the module only runs in a supported environment".

My suggestion to prevent numerous github issue submissions would be to update the message with set expectations/guidance and different terminology: This module and its functionality have been disabled since the module requires webtrees 2.1.6 or earlier but your installed webtrees version is 2.1.7. To restore functionality, please either download and install an updated version of this module that is compatible with your installed webtrees version (when available) or downgrade your installed webtrees version to 2.1.6 (if possible).

Outside of terminology, this "issue" was just me asking for 2.1.7 compatibility (either officially through a module update or by other users sharing their "fixes" - like safely downgrading to 2.1.6 which I just discovered and which worked for me.

ric2016 commented 2 years ago

Thank you for the feedback - I will expand the message as suggested to make it clearer that this is not an actual error.

ric2016 commented 2 years ago

Expanded message in release 2.1.7.0.0