Understood.
I refer to #41156 where this problem is apparently solved within J4.3 with the note that the problem may appear only once. In my case the problem persists with subsequent updates.
It is unfortunate that one.com does not change the database server settings.
However I cannot consider changing provider.
I look for a workable solution in the current context.
I have the following questions:
1. Is it safe to disregard the error message as the site seems to work as expected after a Joomla update?
2. If it is safe it would be best to give a warning instead of an error message. Certainly the advice to restore from backup is wrong: this way any future Joomla update becomes impossible.
3. Does the MysqliDriver.php patch fully guarantee that the following J5 update is safe?
Please pardon my confusion.
I refer to #41156 where this problem is apparently solved within J4.3 with the note that the problem may appear only once. In my case the problem persists with subsequent updates.
It is unfortunate that one.com does not change the database server settings.
However I cannot consider changing provider.
I look for a workable solution in the current context.
I have the following questions:
1. Is it safe to disregard the error message as the site seems to work as expected after a Joomla update?
2. If it is safe it would be best to give a warning instead of an error message. Certainly the advice to restore from backup is wrong: this way any future Joomla update becomes impossible.
3. Does the MysqliDriver.php patch fully guarantee that the following J5 update is safe?
Please pardon my confusion.
Statistics: Posted by straetch — Thu Nov 28, 2024 9:51 am