![]() net 4.5 (I have never had to do this before) and disabling the logging module (all suggestions found here ). Thanks for helping me learn about webtrees. I have been at this for a few days already, as I have read others have had similar issues, tried most things I have read including changing the managedruntimeversion from 'v4.0' to 'v9' for. This test system mirrors the live one closely enough that it can be completely migrated without issue which is why it is a good idea to have it in the first place. It does look like I'm lucky that my XAMPP has remained a bit out of date and I should be able to accomplish the migration to Version 2 using it. My live system has now been reverted to what worked before upgrading. If they are catastrophic and known ahead of time then it ought to be possible to state the problem in the accompanying error message or log. Unless they are catastrophic go ahead and display a warning and let the user with deal with them. I suppose the difference here is that bugs are normally thought of as unanticipated whereas this situation involves known problems. There is always going to be a chance that something might not work correctly. What doesn't make sense is preventing the quote "upgraded" code from being used to do anything just because there is a chance that something might not work correctly. Please Log in or Create an account to join the conversation. This upgrade worked fine when done on my test system but it was quite a surprise to see this result on my hosting service. My own testing system which runs on XAMPP is presently at 7.2.17. It looks like I did make a mistake when I took the version of PHP that phpMyAdmin on my hosting service uses (7.3.27) to be same as what supports my application software which I now see is 7.4.16. When using hosting services which seems like the expected environment for running webtrees downgrading the underlying software infrastructure is likely NOT going to be possible. What I thought would happen by upgrading 1.7.18 is that the database would be brought up to a level that made it ready to migrate to one of the Version 2 options. the specified object property achieves the specified value or exceeds the specified timeout before continuing to the next step. ![]() I would like to avoid starting over with a new installation. However, the migration scenario is beginning to look more complicated than I originally thought. The good news is that I think I can put it back the way it was. ![]() If NOT it was at least doing a pretty good job of pretending to function properly. Message on Webtrees default web address - 'Composer detected issues in your platform: Your Composer dependencies require the following PHP extensions to. The pretty old version (1.7.9) of webtrees I was using seems to work fine on PHP 7.4.16. Did an upgrade via yunohost 'system update'. However, it is NOT so common to find that upgrading applications requires downgrading the underlying software upon which it is dependent. I do understand that it is very common for new code to need features only available in new versions of underlying software upon which it is dependent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |