Software spbu1/4/2023 ![]() ![]() I repeat that after upgrading, the api error appears in all the journals and only in the submissions section. ![]() Here are the corresponding sections in and. Thus we use redirects to “isolate” journals in their own domains. Upgrade - done, api errors - exactly the same… data - just our and cli command for upgrade. But only now and only in submissions section the problem get out… I tried the latest 3.1.1.2 several hours ago, absolutely clean, even without public, etc. Well, the main question is why does this problem come up right now? We use OJS for a year and a half, changed three versions, changing nothing in the settings of the journals. I should say that when i changed client_charset = utf-8 to client_charset = utf8 all persian translations not working and OJS return just key of message not translate message ![]() to “utf-8” for this to work, as characters are stored in utf-8 Note that client_charset and database collation must be set If disabled, strings will be passed through in their native encoding Enable character normalization to utf-8 (recommended) (although the actual name may differ slightly depending on the server) If enabled, must be the same character set as “client_charset” Must be set to “Off” if not supported by the database server ![]() N.Callbacks/j n.Callbacks/k.fireWith /lib/pkp/lib/components/jquery/:2:27949 TypeError: b is undefined :315:449Ī.prototype.modalOpen /js/:315:449Į.a.methods.aja圎rrorCallback bound self-hostedĮ.a.methods.get/<.error /js/build.js:1:46188 When i got this error in my console browser show this errors too: I checked many topic due to this problem so i send more information for detals: Then this information “#” displayed on my screen. I try to manage the submission of my journal but it looks like something trouble and difficult to access the article. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |