When doing a fresh install of branches/19.x via tiki-install.php UI: if the user selects MyISAM as the database engine of his choice instead of the default InnoDB, then after the last step where user chooses to lock the installer there is a system error instead of the screen to change the admin login on the tiki-change_password.php?user=admin&oldpass=admin&newuser=y
(which is really a shame):
An error occurred while performing the request. Things to check: Did you complete the Tiki Installer? Is your database corrupt? Please see how to repair your database Are your database settings accurate? (username, schema name, etc in db/local.php) Please see the documentation for more information.
See https://screenshots.firefox.com/AZAjqNbyHSzadvdJ/demo.luciash.eu
With InnoDB the same process works nicely and the user is welcomed with the admin login password change.
Did anybody test this? How come the unit tests did not catch it?
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |