OJS3.0.2 TypeError: $.pkp.controllers.grid.users.stageParticipant.form is undefined error

Software Support
1

In a multijournal installation one of our journals has this error:

TypeError: $.pkp.controllers.grid.users.stageParticipant.form is undefined[Learn More]  StageParticipantNotifyHandler.js:34:1

<anonymous> http://domainname.fi/lib/pkp/js/controllers/grid/users/stageParticipant/form/StageParticipantNotifyHandler.js:34:1
<anonymous> http://domainname.fi/lib/pkp/js/controllers/grid/users/stageParticipant/form/StageParticipantNotifyHandler.js:16:2

I can see that error in all pages in the dashboard and it basically prevents me from adding participants to submissions. The list of editors will not load.

There is nothing in the php error log. Also, as I said this is one journal in a multijournal installation and no other journal has this problem. I already tried turning of some plugins and enabling the default theme but no luck.

Any idea how to start debugging this?

2

Hi @ajnyga,

Are you using the minified version of the javascript? Check your config.inc.php. If you are, try disabling minification and see if the problem still occurs.

Regards,
Alec Smecher
Public Knowledge Project Team

3

Thanks, I will try this, but I can not see how this would only affect one journal out of 45 journals?

4

Hi @ajnyga,

I missed that aspect of your original post – you’re right. Have you compared the page markup with another journal to see if anything leaps out at you?

Regards,
Alec Smecher
Public Knowledge Project Team

5

This was a weird problem.

This morning I noticed that the same problem does not appear when using my other computer, even with the exact same browser.

So, after erasing my browser cache the problem is now gone! However, it would be nice to know what caused this and if it is potentially something that would happen again.

edit: and I did do a diff between the source code of a working journal dashboard and the broken journal dashboard but did not see any differences there. The only difference is that in the broken journal I have this “<meta name="generator" content="##common.openJournalSystems## 3.0.2.0">”. That is a string that does exist in the translations, but for some reason it is not getting translated for the journal with the problem – even now after clearing browser cache solved the javascript problem.

6

Hi @ajnyga,

Is there a particular page that’s showing ##common.openJournalSystems## as opposed to the correct translation? It’s possible that the appropriate locale file isn’t getting loaded during that request.

Regards,
Alec Smecher
Public Knowledge Project Team

7

It is not getting translated in the dashboard in these pages: Tools, Users & Roles, Settings and Submissions.

It does get translated in Issues and in the workflow of all submissions.

That string is basically the only string that does not get translated, all the other translations are working. I would had not noticed it without the earlier problem and the diff I did.

Edit: and the translation problem with this string is visible in some other journals as well. I have not had time to figure out what the similarity is between them.

8

Hi @ajnyga,

The difference is likely in the plugin set. I suspect most journals have plugins enabled that load the relevant locale file, but on this one, no such plugin is present and the system thus doesn’t load the file containing that locale key.

Regards,
Alec Smecher
Public Knowledge Project Team