[#9510] - Correct issue 9509 missing index and column changes in utf8mb4 conversion
- Closed
- 23 Mar 2016
- Medium
- Build: staging
- Easy Test
- # 9510
- Diff
- richard67:correct-utf8-conversion-2016-03-21
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Pending JTracker/HumanTestResults Human Test Results: 1 Successful 0 Failed. Details
User tests: Successful: Unsuccessful:
Pull Request for Issue #9509
.
Summary of Changes
Add changing of columns and indexes to utf8(mb4) conversion scripts which have been forgotten before.
Column
user_idof table#__user_keysdownsized to length of 150 so it fits to columnusernameof table#__users.Changed column length of column
namein table#__usersto 400.-
Changed follwoing indexes (keys) to include column only with 1st 100 chars:
- TABLE
#__menu, KEYidx_path - TABLE
#__users, KEYidx_name
- TABLE
Column path of table #__menu has already 1024 and was not enlarged in 3.5.0's joomla.sql, and so it is also not enlarged with this PR.
Note: This PR does not solve the problem that the utf8mb4 or utf8 combersion has to be executed again after an update e.g. from 3.5.0 to the 3.5.x in which this PR will be included. This can be manually done by the SQL statement provided in testing instructions below.
A solution for that has to be developed with another PR.
Testing Instructions
Step 1: Apply this patch on latest staging or a 3.5.0 final release, e.g. using the patchtester.
Step 2: In phpMyAdmin, execute the SQL statement from the new schema update script included in this PR:
UPDATE
#__utf8_conversionSETconverted= 0;
The reason for this step is that this PR does not solve the problem that the utf8mb4 or utf8 combersion has to be executed again after an update e.g. from 3.5.0 to the 3.5.x in which this PR will be included, see description above.
Step 3: Go to "Extensions -> Manage -> Database".
Result: Database is not up to date, utf8mb4 (or utf8) conversion is shown as to be done.
Click the "Fix" button.
Result: Database up to date.
Check with phpMyadmin if the changes mentioned in the Summary of Changes above have been applied.
Result: Changes have been applied.
| Status | New | ⇒ | Pending |
| Labels |
Added:
?
|
||
| Title |
|
||||||
| Category | ⇒ | SQL |
| Title |
|
||||||
| Easy | No | ⇒ | Yes | ||||
| Title |
|
||||||
| Title |
|
||||||
| Title |
|
||||||
When I am clicking Fix in Joomla Upgrade after some waiting I am getting an error
405 Not Allowed
nginx/1.8.1
I increased in my php.ihi default_socket_timeout from 90 to 360
and in mysql.connect_timeout from 90 to 360
But it doesn't help. Please help me....
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.
The problem still exists:
The Joomla! Core database tables have not been converted yet to UTF-8 Multibyte (utf8mb4).
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.
So this is definitely the fix we need - the problem is that if people upgrade via the file upload approach then we are in trouble cause the schema update (obviously) doesn't check upgrade or insert statements. meaning they won't run this query :(
I mean it fixed the forum post issue that started all these problems :P
I have tested this item 
successfully on d2bb748
used Method 1: For lazy testers for tests
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.
This PR has received new commits.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.
This PR has received new commits.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.
Removed reset of the conversion status from the schema update because this is 1. not helping in case of update method with file copy and database fix used, and 2. will be disturbing a soon to be developed solution for forcing conversion after an update.
So the former 2nd test method it not requred anymore, and so I have removed it from testing instructions. The remaining test which was former test method 1 is sufficient.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.
Ready for re-test.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.
I have tested this item successfully on b914f7d
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.
I have tested this item successfully on b914f7d
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.
Thanks for testing, @andrepereiradasilva
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-03-23 18:27:09 |
| Closed_By | ⇒ | richard67 |
I've made update as you u said using custom url the update wasn't finished and at the and i've got a message like that:
ERROR 504 - GATEWAY TIMEOUT
Why am I seeing this page?
The server that your request has reached is acting as a gateway or proxy to fulfil the request made by your client.
Web Browser => Web Front-End => Web Back-End
This server (Web Front-End) received an invalid response from an upstream (Web Back-End) server it accessed to fulfil the request.
In most cases this will not mean that the upstream server is down, but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data.
This problem is most commonly caused when there is a problem with IP communications between the Web Front and Back-Ends. Before you attempt to resolve this problem you should clear your browser cache completely.
Our support staff will be happy to assist you in resolving this issue. Please contact our Live Support or reply to any Tickets you may have received from our technicians for further assistance.
So then I go to Joomla update again and the problem
The Joomla! Core database tables have not been converted yet to UTF-8 Multibyte (utf8mb4).
Still exists and actually I do not know how to fix it...
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9510.