After upgrade only some files can be viewed/downloaded

airton · September 15, 2016, 5:41pm

Hi.

I’ve read the topic Can't download or view pdf files - #12 by kalel and my problem is a bit different: after upgrading the system some of the files can be viewed/downloaded and most of them don’t.

I’ve checked file_dir, permissions, slashes, database and find nothing wrong.

Follow example of two links from the older installation (version 2.2) where everything is ok:
http://periodicos.unitau.br/ojs-2.2/index.php/clipeodonto/article/view/2380/1610
http://periodicos.unitau.br/ojs-2.2/index.php/clipeodonto/article/view/2196/1601

The same links of the new installation (version 2.4.5) where:
It’s ok:
http://dspace-teste.unitau.br/ojs-2.4.5/index.php/clipeodonto/article/view/2380/1610
It isn’t ok:
http://dspace-teste.unitau.br/ojs-2.4.5/index.php/clipeodonto/article/view/2196/1601

The upgrade script output ended without any kind of error:
“Successfully upgraded to version 2.4.5.0”

The version 2.4.5 was used as a step to 2.4.8-1 that presented the same problem, after a successfull upgrade.

Thanks a lot.

ctgraham · September 16, 2016, 12:23pm

The file is accessible via the Download link in the upper right:

The default PDFObject viewer is fairly obsolete, so this is probably why it is not displaying inline. Try enabling the “pdfJsViewer” instead from under the Generic plugins category.

airton · September 16, 2016, 8:02pm

Thanks for your answer.

The image you show is about a link that is “ok” and the file appears inline when using Firefox or Chrome.
But when you click on, e.g.,
http://dspace-teste.unitau.br/ojs-2.4.5/index.php/clipeodonto/article/view/2196/16011
nothing happens. No one page with link to download the file is shown.

Please see the image: The link (1) is ok; the link (2) when clicked stay on the same page:

caiomelow · September 16, 2016, 8:19pm

I have a similar problem. No files can be viewed/downloaded. Nobody can download any of the PDFs or DOCs hosted at the journal system (and I know they’re there because they are all available in my university’s ftp - ftp://ftp.uff.br).

The journal’s link is http://www.uff.br/engevista/seer/

Please, tell me how can I solve this asap

Thank you

ctgraham · September 16, 2016, 8:27pm

For these articles that are redirecting back to the journal index, take a look at the article metadata to see if there is some kind of inconsistency, or a visible difference from the metadata of the article that works. This could be something like a missing publication status.

If you’re good with code, you’re almost certainly failing the Article::validate() handler at line 452, with a redirect at line 530:

github.com

pkp/ojs/blob/ojs-stable-2_4_8/pages/article/ArticleHandler.inc.php#L405-L536


		}
	}

	/**
	 * Validation
	 * @see lib/pkp/classes/handler/PKPHandler#validate()
	 * @param $request Request
	 * @param $articleId string
	 * @param $galleyId int or string
	 */
	function validate(&$request, $articleId, $galleyId = null) {
		parent::validate(null, $request);

		import('classes.issue.IssueAction');

		$router =& $request->getRouter();
		$journal =& $router->getContext($request);
		$journalId = $journal->getId();
		$article = $publishedArticle = $issue = null;
		$user =& $request->getUser();

This file has been truncated. show original

airton · September 19, 2016, 2:49pm

That’s it, Clinton.

The table articles (new on v2.4.5) has a column named status. If status=3 the article is shown. If status=1 it is redirected back to the journal index. I don’t know why upgrade execution setted this value to 1 or 3. Is it safe to replace everything to 3?

Thanks a lot.

ctgraham · September 19, 2016, 2:55pm

This would indicate that in the earlier version or in the upgrade process there was a data error where some articles were being treated as published despite not technically having a published status. The article statuses can be found here:

github.com

pkp/ojs/blob/ojs-stable-2_4_8/classes/article/Article.inc.php#L22-L27


// Submission status constants
define('STATUS_ARCHIVED', 0);
define('STATUS_QUEUED', 1);
// define('STATUS_SCHEDULED', 2); // #2187: Scheduling queue removed.
define('STATUS_PUBLISHED', 3);
define('STATUS_DECLINED', 4);

You will want to be careful to check that articles which you expect to be published have both a published status in the articles table, and have an entry in the published_articles table. The best way to ensure this is by setting the status in the web interface, as an editor.

airton · September 19, 2016, 5:47pm

I choosed to update all the status on table articles to 3 (when they were equals to 1) where those articles exist on table published_articles.
After that I upgraded from version 2.4.5 to 3.0.0 and it’s working fine, too.
Thank you very much, Clinton.
Best regards,
Airton