Article galley links not working in some cases

Having made a copy of my live site, which is and upgraded that to OJS I have noticed that some of the galley links (full text and PDF) no longer work. Some crash the server (500 internal server error) and some simply return a 404. Some still work.

The URLs that the galley links point to are identical (apart from having a different subdomain).

To reproduce the issue is simple, just display an article and attempt to download the PDF galley, or to view the full text of the article.

I am using OJS on an AWS Ubuntu instance.

The last two entries in the error log show the server crash as well as the 404:-

[Tue Aug 09 09:47:47.702792 2022] [php7:error] [pid 36454] [client] PHP Fatal error:  Uncaught League\\Flysystem\\FileNotFoundException: File not found at path: journals/1/articles/573/submission/proof/573-1-5066-2-10-20220629.html in /var/www/html/lib/pkp/lib/vendor/league/flysystem/src/Filesystem.php:389\nStack trace:\n#0 /var/www/html/lib/pkp/lib/vendor/league/flysystem/src/Filesystem.php(179): League\\Flysystem\\Filesystem->assertPresent()\n#1 /var/www/html/plugins/generic/htmlArticleGalley/ League\\Flysystem\\Filesystem->read()\n#2 /var/www/html/plugins/generic/htmlArticleGalley/ HtmlArticleGalleyPlugin->_getHTMLContents()\n#3 /var/www/html/lib/pkp/classes/plugins/ HtmlArticleGalleyPlugin->articleDownloadCallback()\n#4 /var/www/html/pages/article/ HookRegistry::call()\n#5 /var/www/html/lib/pkp/classes/core/ ArticleHandler->download()\n#6 /var/www/html/lib/pkp/classes/core/ PKPRouter->_authorizeInitializeAndCallRequest()\n#7 /var in /var/www/html/lib/pkp/lib/vendor/league/flysystem/src/Filesystem.php on line 389, referer:
[Tue Aug 09 09:47:53.612003 2022] [php7:notice] [pid 32217] [client] ojs2: 404 Not Found, referer: https://<mywebsite>.org/index.php/ve/article/view/573

Looking at the error, is there a plugin that I may need to upgrade too?

Many thanks in advance.

I’m still having a problem with this that is preventing my project from going live.

Looking at the error logs, the 404 errors are because there are files that are expected to exist, that don’t.

One example is:


How would these files originally be created? Are they generated from the underlying article or are they uploaded manually by the editor creating the article?

Many thanks in advance.

Hi @Ant_Forshaw,

I’d double-check if all files from your files folder were copied to the newly created one.

1 Like

Thanks @Vitaliy - I was aware of the folder outside of the webroot but I didn’t realise it was based in the actual disk root! I found that one and have been able to copy it across to the new server.

Thanks again.


1 Like