Hello,
We released it an hour ago:https://github.com/ONLYOFFICE/DocumentServer/blob/master/CHANGELOG.md
Please re-check the situation and let us know the result.
We are now focused on the desktop version, which will probably take a few more days.
Hi again. I updated only office and zotero plug-in. Unfortunately The problem persists. The bibliography are still being pasted together as a whole.
Thank you @mustifanci
Weâre checking the situation. I will contact you shortly.
Hi All,
As posted by other users, the bibliography created by Zotero is a single paragraph. and the indentation is only present at the first line of the block.
The field that is written in the document to create the bibliography is:
ADDIN ZOTERO_BIBL CSL_BIBLIOGRAPHY \&
my assumption is that it is missing which bibliography to choose from. So I tested it:
I searched my drive for the csl files and found one with a short name (apa.csl)
ADDIN ZOTERO_BIBL CSL_BIBLIOGRAPHY \& APA
ADDIN ZOTERO_BIBL CSL_BIBLIOGRAPHY \& apa
ADDIN ZOTERO_BIBL CSL_BIBLIOGRAPHY \& âAPAâ
ADDIN ZOTERO_BIBL CSL_BIBLIOGRAPHY \& âapaâ
after all confirmation of the field edit, I update the field. Nothing changes. Then I took a different spin and went creative:
ADDIN ZOTERO_BIBL APA_BIBLIOGRAPHY
nothing, no changes, still the same text⌠though this was supposed to be a almost wrong field⌠so I mess it up a bit more:
ADDIN ZOTERO_BIBL
nothing, no changes, still the same text⌠though this was supposed to be a almost wrong field⌠so I mess it up a bit more:
ADDIN
nothing, no changes, still the same text⌠The same text? now the field shouldnât even know which plugin to takeâŚ
This makes me wonder if the field generated by zotero is editable at all. This might be the issue, Onlyoffice might not be able to answer any formatting request. I donât know, just a hunch.
Dear @mustifanci
Thank you for pointing us to this situation. We have found a bug and weâre going to fix it in the next plugin version (1.0.9).
@ReferOnly Thank you for detailed description. As far as I understand youâre referring to the same issue described above. If so, it will be fixed in v.1.0.9