[OJS 3.2.1.4] Failed to update OJS

Software Support
1

Hi,

I updated my OJS installation from version 3.1.2.0 to version 3.2.1.4, and in one of my journals I have cover images which are entered into the publications, but when updating, I cannot see them as shown in the following images :

image

image

And in the log it shows me the following error:

[image]

[core:error] [pid 23521] (36)File name too long: [client 186.84.91.50:1124] AH00036: access to /public/journals/48/a:3:....

and in the url of the image it shows me the following:

[image]

https://xxxxxxxxx/public/journals/48/a:3:{s:10:"uploadName";s:1651:"a:3:{s:10:"uploadName";s:1549:"a:3:{s:10:"uploadName";s:1447:"a:3:{s:10:"uploadName";s:1345:"a:3:{s:10:"uploadName";s:1243:"a:3:{s:10:"uploadName";s:1141:"a:3:{s:10:"uploadName";s:1039:"a:3:{s:10:"uploadName";s:938:"a:3:{s:10:"uploadName";s:837:"a:3:{s:10:"uploadName";s:736:"a:3:{s:10:"uploadName";s:635:"a:3:{s:10:"uploadName";s:534:"a:3:{s:10:"uploadName";s:433:"a:3:{s:10:"uploadName";s:332:"a:3:{s:10:"uploadName";s:231:"a:3:{s:10:"uploadName";s:130:"a:3:{s:10:"uploadName";s:30:"article_347512_cover_en_US.png";s:12:"dateUploaded";s:19:"2021-10-25 01:11:15";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:15:11";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:19:34";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:19:43";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:27:37";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:34:16";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:34:48";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:41:26";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:44:35";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:45:03";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:45:11";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:45:23";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:46:28";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:46:47";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:48:22";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:48:35";s:7:"altText";s:0:"";}";s:12:"dateUploaded";s:19:"2021-10-24 20:49:42";s:7:"altText";s:0:"";}
2

In addition, it is showing the following error in the logs that has to do with the database:

PHP Fatal error:  Uncaught Exception: DB Error: Illegal mix of collations (utf8_spanish_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=' Query: SELECT a.*, ug.show_title, p.locale,\n\t\t\t\tCOALESCE(agl.setting_value, agpl.setting_value) AS author_given,\n\t\t\t\tCASE WHEN agl.setting_value <> '' THEN afl.setting_value ELSE afpl.setting_value END AS author_family\n\t\t\tFROM\tauthors a\n\t\t\t\tJOIN user_groups ug ON (a.user_group_id = ug.user_group_id)\n\t\t\t\tJOIN publications p ON (p.publication_id = a.publication_id)\n\t\t\t\tJOIN submissions s ON (s.current_publication_id = p.publication_id)\n\t\t\t\tLEFT JOIN author_settings agl ON (a.author_id = agl.author_id AND agl.setting_name = ? AND agl.locale = ?)\n\t\t\t\tLEFT JOIN author_settings agpl ON (a.author_id = agpl.author_id AND agpl.setting_name = ? AND agpl.locale = p.locale)\n\t\t\t\tLEFT JOIN author_settings afl ON (a.author_id = afl.author_id AND afl.setting_name = ? AND afl.locale = ?)\n\t\t\t\tLEFT JOIN author_settings afpl ON (a.author_id = afpl.author_id AND afpl.setting_name = ? AND afpl.locale  in /var/www/html/site.revistas.udea.edu.co/lib/pkp/classes/db/DAO.inc.php on line 703
3

Hola Diego,

If you manage to fix the mixed collations error, you’ll probably have the other issue fixed as a side effect.

OJS requires the database to use the same collation for all tables in the database, and for all columns in each table.

The recommended collation is utf8_general_ci.

Converting from other utf8_* to utf8_general_ci should not be a big deal, but it has potential to cause data losses. I suggest you to take backups of everything before making adjustments to the database (better safe than sorry).

How does it sound to you?

Best,
Janio