Web app to manage all related data within any Research Unit(s). It allows to describe researchers, projects, publications, funding programs, etc. in order to display them in a clear way and create interactive graphs which analyse the unit(s) performance.
Running the Zotero synchronize method from the maintenance web page with a new attachment didn't work. Calling the same method from console worked. Later, a minor change (tag), when calling with maintenance mode also worked.
a) Consider showing the results of the script with <pre></pre> in the maintenance task, to provide more info (after all, whoever is executing it is already admin, right?)
b) Check if there is any issue with attachments from the web interface. We checked that the MEDIA_ROOT variable is correctly set (absolute path).
Additionally, a potentiallly related minor bug: a minor change (e.g., a note attached) doesn't update the current version number, since no ZoteroExtractorLog is added. So, the script works, but it always says "you're in version 2159 and the repo in 2161". Whenever you add a change that is saved (e.g., a tag), it increases the number.
Running the Zotero synchronize method from the maintenance web page with a new attachment didn't work. Calling the same method from console worked. Later, a minor change (tag), when calling with maintenance mode also worked.
a) Consider showing the results of the script with
<pre></pre>in the maintenance task, to provide more info (after all, whoever is executing it is already admin, right?)b) Check if there is any issue with attachments from the web interface. We checked that the MEDIA_ROOT variable is correctly set (absolute path).
Additionally, a potentiallly related minor bug: a minor change (e.g., a note attached) doesn't update the current version number, since no ZoteroExtractorLog is added. So, the script works, but it always says "you're in version 2159 and the repo in 2161". Whenever you add a change that is saved (e.g., a tag), it increases the number.