Soy administrador y gestor de una revista con la versión OJS 2.4.0.0
Hace un par de semanas, estuve probando el plugin que permite la utilización de los DOI, vi como funciona, pude aprender a configurar, etc. Horas después, suspendí dicho plugin, porque no tenia sentido que apareciera en cada artículo un DOI inexistente o erróneo. Mi idea es empezar a utilizarlo en el 2019…
Dos semanas mas tarde, reconfigurando algunos detalles de la plataforma, intento acceder al menú “Gestión de revista / System Plugins” y me aparece la pantalla del navegador en blanco con una sola linea de texto que dice:
…/…/datacite/classes/DOIExportPlugin.inc.php
Me aparece también cuando accedo en “Gestión de la revista / Importar/exportar información”
¿Que ha sucedido? ¿Cómo puedo corregir ese error? Se me complica porque debo realizar tareas importantes en algunos plugins de la plataforma.
Saludos y muchas gracias…
Eduardo
I suspect you’re using a tool to extract the .tar.gz file that doesn’t support symbolic links. Try using a different tool, and you should find that this file (and others) contain legitimate PHP code rather than a pathname.
I’d also suggest using a newer release of OJS – version 2.4.0-0 is now very old.
Regards,
Alec Smecher
Public Knowledge Project Team
First, yes, in 2019 we will update to OJS version 3.1
Second, I do not know how to make your recommendations. I have not downloaded or installed anything since the first time we put the OJS on the server four years ago.
Can you recommend a task to enable the “Systems plugin” option again?
Sorry, I read your post too quickly – this isn’t about a fresh unpacking of the .tar.gz file. Nevertheless something seems to have turned your system’s symbolic links into flat files (I’ve seen this happen when running sed over symbolic links, for example).
I’d suggest unpacking a fresh copy of the OJS 2.4.0 code, and searching for symbolic links inside it (e.g. using find . -type l). Then make sure those files in your live installation are actually symbolic links.
Regards,
Alec Smecher
Public Knowledge Project Team
No, I can not find where is the bug. The file of the last backup (worked correctly) is the same as the one in the server.
I do not think I have the technical knowledge to fix this problem. When I was testing the plugin that manages the DOI, something was damaged in the database or in the server files.
I do not know who can help me…
Thanks for your help …