J4 Issue ? ?
avatar zero-24
zero-24
31 Aug 2019

Steps to reproduce the issue

Install 4.0 on a system running on systems that does not meat the database minimums for example mysql 5.5.*

Expected result

The installer aborts or we show some message indication that the system is runnung in an not supported configuration.

Actual result

Joomla still works for now but we don't tell our users this is a not supported setup.

Additional comments

I personally see these workarounds.

  1. let the installer stop working / showing an dedicated message
  2. postinstall message checking the minimum versions.
  3. system alert on any backend login to that site like we do with the php versions too.

Any other opinions?

The part why this is important is that starting with 4.0.0 we are stopping to allow updates for sites that don't meat that database requirements so such a site gets insecure by the first security realted release.

avatar zero-24 zero-24 - open - 31 Aug 2019
avatar joomla-cms-bot joomla-cms-bot - change - 31 Aug 2019
Labels Added: ? ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 31 Aug 2019
avatar joomla-cms-bot joomla-cms-bot - labeled - 31 Aug 2019
avatar franz-wohlkoenig franz-wohlkoenig - change - 1 Sep 2019
Status New Discussion
avatar franz-wohlkoenig franz-wohlkoenig - change - 1 Sep 2019
Labels Added: J4 Issue
avatar franz-wohlkoenig franz-wohlkoenig - labeled - 1 Sep 2019
avatar wilsonge
wilsonge - comment - 12 Sep 2019

postinstall is no good as it requires having an installation. installer should stop working and show a page similar to the php minimum requirements page i think

avatar richard67
richard67 - comment - 25 Feb 2020

@wilsonge This is not working or wrong. It is the same problem as I have with issue #27924 : The database connection validation of the setup model just checks if the user can connect with the provided credentials. If not, we come back to the form and can correct data. But the check of the database name (including try to install it) and check of db version are then done in the CreateDatabase function of the database model, and if somethign goes wrong there we end up as descibed in issue #27924 . The reason is that it seems to be missing a correct error handling in JS/Ajax for the final step, creating database if necessary and installing the cms. It seems the installation is unfinished work at this point, and it goes together with including the languages installation and default language selection, which requires some work at the same place. Unfortunately it is beyond my knowledge so I have no idea how to solve that.

avatar richard67
richard67 - comment - 29 Feb 2020

I'm just preparing a PR to solve this issue. Stay tuned.

avatar richard67
richard67 - comment - 29 Feb 2020

Please test PR #28135

avatar richard67 richard67 - change - 29 Feb 2020
Status Discussion Closed
Closed_Date 0000-00-00 00:00:00 2020-02-29 15:07:38
Closed_By richard67
avatar richard67
richard67 - comment - 29 Feb 2020

Closing as having PR. Feel free to re-open if you think my PR doesn't solve this issue or if it turns out to be wrong for some other reason

avatar richard67 richard67 - close - 29 Feb 2020

Add a Comment

Login with GitHub to post a comment