Back issue's Table of Contents is stuck on loading

Software Support
1

When we open the Table of Contents in Issue Management it only says Loading. We’ve left it for hours and nothing has happened.

For clarity, we go to administration, select the desired journal, select Issues->Back Issues. We select a volume and click Edit. The other tabs of the Issue Management (Issue Data, Issue Galleys, Identifiers) load as expected. I checked the error logs and there wasn’t anything in there to indicate a problem.

Any ideas as to what is wrong? Thank you!

2

Hi @califer,

Check your PHP error log to see if there are any relevant details.

Regards,
Alec Smecher
Public Knowledge Project Team

3

Here’s a section of the log that looks relevant.

[Thu Aug 31 16:36:23.136395 2017] [:error] [pid 14735] [client 71.219.74.118:51839] PHP Notice: unserialize(): Error at offset 283 of 448 bytes in /home/sites/epubs.sandbox.lib.utah.edu/lib/pkp/classes/db/DAO.inc.php on line 347, referer: http://epubs.utah.edu/index.php/HJP/manageIssues
[Thu Aug 31 16:36:23.136698 2017] [:error] [pid 14735] [client 71.219.74.118:51839] PHP Notice: unserialize(): Error at offset 913 of 1186 bytes in /home/sites/epubs.sandbox.lib.utah.edu/lib/pkp/classes/db/DAO.inc.php on line 347, referer: http://epubs.utah.edu/index.php/HJP/manageIssues
[Thu Aug 31 16:36:23.148997 2017] [:error] [pid 14735] [client 71.219.74.118:51839] PHP Notice: unserialize(): Error at offset 758 of 2287 bytes in /home/sites/epubs.sandbox.lib.utah.edu/lib/pkp/classes/db/DAO.inc.php on line 347, referer: http://epubs.utah.edu/index.php/HJP/manageIssues
[Thu Aug 31 16:36:23.152722 2017] [:error] [pid 14735] [client 71.219.74.118:51839] PHP Notice: unserialize(): Error at offset 794 of 3418 bytes in /home/sites/epubs.sandbox.lib.utah.edu/lib/pkp/classes/db/DAO.inc.php on line 347, referer: http://epubs.utah.edu/index.php/HJP/manageIssues
[Thu Aug 31 16:36:23.158905 2017] [:error] [pid 14735] [client 71.219.74.118:51839] PHP Notice: unserialize(): Error at offset 2337 of 4795 bytes in /home/sites/epubs.sandbox.lib.utah.edu/lib/pkp/classes/db/DAO.inc.php on line 347, referer: http://epubs.utah.edu/index.php/HJP/manageIssues
[Thu Aug 31 16:36:23.160961 2017] [:error] [pid 14735] [client 71.219.74.118:51839] PHP Notice: unserialize(): Error at offset 2056 of 4921 bytes in /home/sites/epubs.sandbox.lib.utah.edu/lib/pkp/classes/db/DAO.inc.php on line 347, referer: http://epubs.utah.edu/index.php/HJP/manageIssues
[Thu Aug 31 16:36:36.855369 2017] [:error] [pid 14751] [client 71.219.74.118:51872] Malformed UTF-8 characters, possibly incorrectly encoded, referer: http://epubs.utah.edu/index.php/HJP/manageIssues

4

Hi @califer,

I suspect your encoding settings in config.inc.php don’t match the actual encoding of your database.

Regards,
Alec Smecher
Public Knowledge Project Team

5

Yeah, it looks like everything that got added in the update defaulted to a storage engine of InnoDB and a Collation of latin1_swedish_ci instead of what the database was before. I’ve updated all the collations to be utf8_unicode_ci to match with the config setting “client_charset = utf-8”.

I’m still getting the same error and the same log message. Is there a different encoding setting? Something I have to do aside from changing the collation of the tables?

6

Hi @califer,

What are your database_charset and connection_charset?

Regards,
Alec Smecher
Public Knowledge Project Team

7

They are both set to Off.

8

Hi @califer,

Your settings should probably be

client_charset = utf-8
connection_charset = utf8
database_charset = utf8
charset_normalization = Off

(Note that some of these are utf-8 and others are utf8 – that’s intentional and required.)

However, you won’t be able to simply change character set options without issue, if your data was created with a misconfiguration – you may have to run your database dump through iconv as it’s potentially double-encoded or mis-encoded.

Regards,
Alec Smecher
Public Knowledge Project Team

9

I think I’m a little confused. Are you saying that I should dump the database through iconv to clean the data, then use that to rebuild the database after changing the config as you’ve listed?

10

Hi @califer,

The settings should be as describe above in your config.inc.php. Any additional steps you might need to take will be determined by e.g. whether your data was entered into the database while the character set options weren’t set correctly – if that’s the case, then you can configure OJS to use the right settings, but existing data will be mis-encoded. If that happens then you’ll need to dump your database, run it through iconv or similar to correct the encodings to proper UTF8, then reload the converted dump into MySQL.

That’s more of a database administration task than an OJS-related question, and the details will depend heavily on your case – you might have a look at Stackoverflow for recommendations.

Regards,
Alec Smecher
Public Knowledge Project Team