Hello!
In some submisssion when the editor try to see the Editorial History in the popup windows no display nothing and the message Loadind appears like in this image:
The error is not for all submissions, the editor needs see them to make decisions .
Thanks!
Hi @cridum,
See Fix editorial history for emails with sender_id=0 · Issue #4655 · pkp/pkp-lib · GitHub for details and a patch.
Regards,
Alec Smecher
Public Knowledge Project Team
Hi Alec,
Thak you, I will do it.
Hi @asmecher
I can confirm that I’m seeing the same error described here by @cridum (stuck on Loading when I click on Editorial History) on my OJS v3.1.2 installation. The Fix editorial history for emails with sender_id=0 · Issue #4655 · pkp/pkp-lib · GitHub patch you mentioned above does not seem to resolve it.
As mentioned by @Zetsaika in DB: Unknow column 'Array' - OJS 2.4.8-2 to 3.0.2 Upgrade - #16 by Zetsaika, I’m not seeing any errors in my PHP error log either.
Any suggestions would be welcome.
Regards
Reagan
Hi @reagan,
Check your browser console to see what response your browser gets to the request for the log.
Regards,
Alec Smecher
Public Knowledge Project Team
I hope this is what you asked for:
Hi @asmecher
Just wanted to check if the posted screenshot contained the information you needed.
Regards
Reagan
Hi @reagan,
I see the bottom request/response loads the spinner, but that should be followed by a request that displays the results. Is that the last request you see? Is there anything on the JS error console?
Regards,
Alec Smecher
Public Knowledge Project Team
Hi @asmecher
That is most definitely the last request I see in the Firefox console. Not completely sure what you mean by the JS error console, but I hit Ctrl-Shift-J on Firefox and saw no errors show up on the console that was presented. Would appreciate your advise on how I may go about finding this JS error console if this isn’t where I was supposed to be looking.
Regards
Reagan
Hi @reagan,
What you should be seeing is 3 requests in sequence when you open the Information Center:
That’s one for the tabset, one for the general contents of the history tab, and the last to fetch the actual list of events.
I don’t see the final one in your list – and the one before it (view-history) looks fine. So that would suggest to me that you hit a Javascript error after view-history returned but before fetch-grid was requested. Do you have Chrome’s inspector handy? I tend to use that one.
Regards,
Alec Smecher
Public Knowledge Project Team
Hi @asmecher,
I’m also having problem with this. Patch applied but it’s the same - spinner just spins. OJS 3.1.2.
EDIT:
Hm, this is strange. I was testing in FF where it doesn’t work and in Chrome it works.
regards.
Hi @orcalator,
Try flushing your browser’s cache and hard-refresh.
Regards,
Alec Smecher
Public Knowledge Project Team
Hi @asmecher
Apologies for the delayed response to this. I can confirm that fetch-grid request is never made, or at least doesn’t show up in the Firefox console upon clicking on Editorial History.
I can also confirm the observation made by @orcalator that the editorial history shows up just fine on Chrome. It’s just in Firefox that this issue occurs, even after clearing the cache and hard-refreshing.
Regards
Reagan
Hi @reagan,
Hmm; have you checked your browser’s error console to see whether there’s a Javascript error that might explain why the log wasn’t fetched?
Regards,
Alec Smecher
Public Knowledge Project Team
Again, not quite sure what you mean by Firefox’s error console, since I couldn’t find it in the browser menus. I could only find a “Web Console”, which I shared a screenshot of in OJS-3.1.2 Editorial History Problem in some submissions - #6 by reagan. Since the “Errors” option is enabled in this console, I’d assume it’d show any errors if they occurred.
I’ve stumbled across this issue today, and found out my ad stopper was responsible for that. To sort this out just try to run your browser without any extensions and add-ons. E.g. for Chrome it would be
chrome.exe --disable-extensions --disable-plugins
Yikes! @Ph_We - You’re absolutely right. It was my adblocker that was tripping me up. Disabling it resolved this issue. Thanks a lot for pointing this out.
Hi all,
Well spotted, @Ph_We! Glad it’s working again.
Thanks,
Alec Smecher
Public Knowledge Project Team