UTF-8 warning when upgrading Tiki18 to Tiki19
- Status
- Closed
- Subject
- UTF-8 warning when upgrading Tiki18 to Tiki19
- Version
- 19.x
- Category
- Error
- Consistency
- Feature
- Installer (profiles, upgrades and server-related issues)
- Resolution status
- New
- Submitted by
- Bernard Sfez / Tiki Specialist
- Volunteered to solve
- rjsmelo
- Lastmod by
- Bernard Sfez / Tiki Specialist, Marc Laporte
- Rating
- Related-to
- Description
I switch a Tiki18 to a Tiki19.
During the install on the database step, I had a warning about "UTF-8 encoding" while my tables were properly upgraded to utf8mb4_unicode_ci.
Following the links to the doc doesn’t really help
On a second attempt (local) I didn’t upgrade previously the table and applied the database upgrade. After upgrading the database I checked my database (phpmyadmin) most of the tables were utf8mb4_unicode_ci while a few (see the list below) were still UTF-8 unicode;
tiki_acct_journal
tiki_acct_stack
tiki_banningThe database upgrade process ended successfully but with error report:
Upgrade operations executed successfully: 668 SQL queries. Operations failed: 6 SQL queries. Display details. During an upgrade, it is normal to have SQL failures resulting with Table already exists messages. ALTER TABLE `sessions` convert to character set DEFAULT COLLATE DEFAULT Table 'tsaharoniki_tiki19.sessions' doesn't exist ALTER TABLE `tiki_banning` convert to character set DEFAULT COLLATE DEFAULT Invalid default value for 'date_to' ALTER TABLE `tiki_acct_journal` convert to character set DEFAULT COLLATE DEFAULT Invalid default value for 'journalDate' ALTER TABLE `tiki_acct_stack` convert to character set DEFAULT COLLATE DEFAULT Invalid default value for 'stackDate' ALTER TABLE `tiki_banning` CHANGE `message` `message` text COLLATE utf8mb4_unicode_ci Invalid default value for 'date_to' ALTER TABLE `sessions` CHANGE `data` `data` text COLLATE utf8mb4_unicode_ci NOT NULL Table 'tsaharoniki_tiki19.sessions' doesn't exist If you think that the errors of a patch can be ignored, please check the checkbox associated to it before clicking on continue.
I refreshed and they were no more errors.- Solution
- Fixed by Ricardo several commits
- Importance
- 5
- Easy to solve?
- 5
- Priority
- 25
- Demonstrate Bug (Tiki 19+)
-
This bug has been demonstrated on show2.tiki.org
Please demonstrate your bug on show2.tiki.org
Version: Create show2.tiki.org instanceAbout show2.tiki.orgTo 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.
- Ticket ID
- 6870
- Created
- Thursday 18 October, 2018 08:59:13 GMT-0000
by Bernard Sfez / Tiki Specialist - LastModif
- Thursday 08 November, 2018 14:47:42 GMT-0000
Attachments
| filename | created | hits | comment | version | filetype | ||
|---|---|---|---|---|---|---|---|
| No attachments for this item | |||||||
;){kind=link}
;){kind=link}
;){kind=link}
;){kind=link}