Known Issue: DOIs are not loading in rich text #3128
Replies: 2 comments
-
|
This is an interesting discussion that highlights important ideas around publishing, knowledge sharing, and digital collaboration. Platforms that encourage open conversations help communities exchange insights and improve access to information. Clear resources, like a Sonic Menu With Prices, also show how organized content can make finding details much easier. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for sharing this valuable topic. Discussions like this help readers understand the importance of open knowledge and collaborative platforms. Well-structured guides, such as a detailed منيو البيك, demonstrate how presenting information clearly can improve the overall user experience. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Multiple communities have reported issues with references, where DOIs are not loading as rich text.
Last month, Crossref reported degraded performance of its Public REST API, which we used for loading citations on Pubs. During this incident, it took too long for Pubs to load citations properly, leading Pubs to crash.
We committed a fix to this to reduce crashing. As part of this fix, if a Pub is unable to get information from Crossref quickly, it will default to displaying the DOI or URL as the reference. This allows the reference information to be retained and the pub to load successfully. Additionally, per Crossref’s recommendation, we have switched to the Polite REST API to improve troubleshooting measures.
Crossref is still making updates to its API, particularly in rate limiting and load balancing. As noted in the title & seen in the screenshot above, you may see that certain citations do not fully load, and instead only display the DOI. We will make updates as Crossref moves to a long-term solution.
What you can do in the interim:
Beta Was this translation helpful? Give feedback.
All reactions