Install Joomla 3.5 RC3 on environment described in "system information".
I'm running Joomla 3.4.8 perfectly on the same environment without any issues. Since this is a one-click upgrade I would expect there was no need for changing server configuration.
I've found that increasing the "sort_buffer_size" to 256k resolves the issue, but should that be necessary? Again, this is a one-click upgrade.
Sorry if this "issue" is mentioned elsewhere.
The sort_buffer_size is very low -way below the default mysql value
Ok, so this is not going to be an issue with any hosts?
Shouldnt be - they would at least be using the defaults and most likely even higher
Should I set the sort_buffer_size to 256k, or what would you recommend?
The default on my MAMP install is sort_buffer_size = 512K
|Closed_Date||0000-00-00 00:00:00||⇒||2016-03-15 11:27:51|
I've encountered this same issue with OpenShift with their sort_buffer_size = 128K.
The OP dropped a hint that pointed me to the change that is causing this impact.
Version 3.4.8 uses the following parameters when creating most tables:
ENGINE=InnoDB DEFAULT CHARSET=utf8
Version 3.5.1 changed it to the following:
ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 DEFAULT COLLATE=utf8mb4_unicode_ci
I do not know if it was intentional but that's the cause of it. My fresh, completely empty, install of Joomla 3.5.1 would not open the extensions > modules page. After re-creating the DB with the original parameters, it opens it just fine.
I am not sure if there are any other underlying effects by changing it but this is definitely the culprit.