[Error] OJS 3.1.2-4 upgrade to OJS 3.2.0.2 some tabs in ojs settings disappear

Software Support
1

Hi,
I have try upgraded to journal 3.2.0.2 from my previous journal version 3.1.2.4.
Screenshot%20from%202020-04-10%2014-43-34

I did not find an error message after upgrading
Screenshot%20from%202020-04-10%2014-43-49

Honestly on the tab settingg-journal-masthead, and TAB setting- website-setup does not appear anything :(.

Untitled

Then I tried to activate display_error to find out what was happening, but I also did not find any specific error messages regarding the error I was experiencing.
ss%20bug

And then I tried to see the error log contained by the web developer and then it appeared like this.
setup-posd

I hope there is a solution for my problem

Kind regards,
Ghazi Pradana

2

Hi @goodzy,

  1. Turn display_errors to Off; if there are warnings/errors sent to the browser during AJAX requests, they’ll interfere with the JSON message and break the site. Use the error log on the server to check for errors instead.

  2. Make sure you hard-refresh your browser; it’s possible that it’s still caching old Javascript from your previous version.

  3. Check your web browser’s error console to see if anything helpful appears there.

Regards,
Alec Smecher
Public Knowledge Project Team

3

I have same issue. On the tab settingg-journal-masthead , and TAB setting- website-setup does not appear anything. Still looking for to fix this problem.

7

i have the same problem in the website sitting after upgrading ojs 3.1.1-4 to ojs 3.2.1-2

Capture

the Error_log shows : [21-Jan-2021 17:55:41 UTC] PHP Notice: unserialize(): Error at offset 305 of 1030 bytes in /home/hkjr69wrd4uf/public_html/journal.qubahan.com/lib/pkp/classes/db/DAO.inc.php on line 357

and
[21-Jan-2021 17:55:41 UTC] PHP Notice: Deprecated call without request object. in /home/hkjr69wrd4uf/public_html/journal.qubahan.com/lib/pkp/classes/template/PKPTemplateManager.inc.php on line 973

8

the solution for this problem is by changing the Localization Settings in my config.in.php file.

from

from this setting:

;;;;;;;;;;;;;;;;;;;;;;;;;
; Localization Settings ;
;;;;;;;;;;;;;;;;;;;;;;;;;

[i18n]

; Default locale
locale = en_US

; Client output/input character set
client_charset = utf-8

; Database connection character set
; Must be set to “Off” if not supported by the database server
; If enabled, must be the same character set as “client_charset”
; (although the actual name may differ slightly depending on the server)
connection_charset = Off

; Database storage character set
; Must be set to “Off” if not supported by the database server
database_charset = Off

; Enable character normalization to utf-8 (recommended)
; If disabled, strings will be passed through in their native encoding
; Note that client_charset and database collation must be set
; to “utf-8” for this to work, as characters are stored in utf-8
charset_normalization = Off

to this setting:

;;;;;;;;;;;;;;;;;;;;;;;;;
; Localization Settings ;
;;;;;;;;;;;;;;;;;;;;;;;;;

[i18n]

; Default locale
locale = en_US

; Client output/input character set
client_charset = utf-8

; Database connection character set
; Must be set to “Off” if not supported by the database server
; If enabled, must be the same character set as “client_charset”
; (although the actual name may differ slightly depending on the server)
connection_charset = utf8

; Database storage character set
; Must be set to “Off” if not supported by the database server
database_charset = utf8

; Enable character normalization to utf-8 (recommended)
; If disabled, strings will be passed through in their native encoding
; Note that client_charset and database collation must be set
; to “utf-8” for this to work, as characters are stored in utf-8
charset_normalization = Off