I am newbie to pkp (OJS 188.8.131.52). I am moving a science journal to ojs and have run into this problem.
The html markup shows an inconsistent display in article titles. Italics, superindex or subindex are correctly shown in article titles in the issue TOC, but the html markup appears in the title in the individual article page, and the same appears in the citation box.
For the transfer I have created an xml exporter in my old site that works perfect. The journal has many titles with HTML formats. The exporter protects problem characters appropriately and moves them smoothly to OJS using the imported. Everything is fine, but in the titles the problem reported here appears.
For my work, the entry of the html markup is not a problem, since the importer enters them correctly through xml.
The problem is the output, and there is something clearly inconsistent here. In the table of contents the formatting is interpreted correctly, therefore it is perfectly possible. However, in the independent articles, in the title and in the citation, the html markup appears.
I think the code could at least be revised to make it consistent across TOC and individual items.
In sciences, formats like italics, superindex and subindex are relevant.
The introduction of the formatings in the title is another subject, but fixing the output would at least solve (more than) half the problem, I think.
In the issue TOC the html formats are correctly applied.
Pay attention to the words Candida and in vitro, correctly displayed in italics in the title of the first article:
Now in the article, the same words display the html markup:
Here is a detail of the title:
And here is a detail of the citeation:
The formatting was introduced in the import process through a generated xml document form the old site (this is the original article: http://www3.uah.es/dianas/journal/dianas-2013-2-1-e20130301 ). The xml exporter was custom made for this site, but the xml generated is now fully compatible with the OJS importer.
I see that you have commented on this issue: Inconsistent HTML display in article titles · Issue #2564 · pkp/pkp-lib · GitHub (at least I think this is you). This issue is still open, and as you’ve likely seen, there’s considerable discussion on the merits and issues associated with storing HTML in title fields (e.g. implications for sharing with third-party services). So, presently, it is not possible to do this, but given that the issue is still open and is on the radar of many of our developers it will likely be addressed in a future version of OJS.
Thanks Roger @rcgillis,
Yes, it’s me on GitHub. I’ve been reading most of the comments.
I had to face the same problem when developing the software for my sites.
My solution was to keep two fields for the title (and two also for the summary), one without formats and the other with html formats, the latter used only when needed. With this trick I can show the reader the title and summary correctly formatted but keeping the full functionality for text searches or other actions.
In my sites, articles are saved as plain text with tag-delimited fields, using a superset of medline tags. Content can be exported (and imported) directly in medline format. When necessary, I have made translators to (and from) other formats, such as the last one for OJS xml.
I already have in mind a way to solve the problem of the formats in the title in OJS. I will comment on the forums when it is operational.
About this point, I think that the approach should not be if it is convenient or not, but if it is necessary, and in a general jounal manager, in my opinion and experience in Sciences, this characteristic is essential. It is not an aesthetic whim but the correct way to write certain things.
In my opinion as a totally novice OJS user, this is a fundamental shortcoming, not a minor inconvenience.
I don’t doubt that this would be a valuable option to have, nor do I doubt its utility for the sciences (and other disciplines too). But, the fact of the matter is that it may not be a simple fix - our developers have to assess the implications of storing HTML in a metadata field (whether an additional field or the same one) in a way that does not have significant implications for the rest of the software. Our developers will see your comment in the Github issue and take it into account. I’m hopeful that such a feature will get implemented in a future version of OJS.
Hi Roger @rcgillis,
The script is loaded, I can find it in the page source, but it is not executed.
I reduced the code to a simple alert(‘hello!’); and still it is not executed.
Could you help me with this!
I consulted both sources to learn about the Custom Header Plugin. The second actually shows two cases of inclusion of an external script. I am able to reproduce this without problems, so everything is OK up to this point.