I’ve installed the newest OJS-Version on my local system which workted quite well. But now I’ve encountered a problem. I checked all languages in the install process, but if I try to create a new journal, nothing happens and in the browser console I get this error: TypeError: “e.availableLocales is null”
I guess something didn’t work with the Locales, but because I don’t have access to the site settings yet (as long as I don’t create at least two journals), I cannot disable them or check if they are there. What can I do?
Do you mean the collation? It’s utf8mb4_general_ci.
I’m sorry if this isn’t the right information. I only have a bit experience with creating databases.
When I’m trying to install all locales, I receive:
PHP Fatal error: Uncaught Exception: DB Error: Data too long for column 'installed_locales' at row 1 Query: UPDATE site SET redirect = ?,primary_locale = ?,min_password_length = ?,installed_locales = ?,supported_locales = ? in /var/www/ojs-3.2.0-1/lib/pkp/classes/db/DAO.inc.php:703
That column length tops out at 255 characters; maybe it needs to be transformed to another type of column – but it’s not really a common case, installing all locales, I don’t think!
For your information: I’ve installed OJS a second time, now without enabling any languages aside from English. Now I don’t have the error anymore.
Therefor I think the two problems are connected. Do you think it might be a problem upgrading a system with so many languages? We use almost all of them.
OK, this does help. It looks like the storage format for the locale list changed from a colon-separated list to a serialized PHP array, which consumes a little more space. That would explain why a list that wasn’t previously too long has now become so.