
comments are shown when expanding bibtex code
Hey there!
Not sure whether that's an idea or a bug, I guess it's in the middle of both, maybe an "issue", i.e., something to "optimize"?
Anyway, assume you have a bibtex file that uses "comments" between the bibtex entries, maybe one line before each entry to explain what it is/shows. Note that bibtex doesn't formally have a designated comment symbol; as far as I am aware everything will simply be ignored that's outside of a bibtex entry. But since it looks odd to simply write some text somewhere into the file, I usually place a "%" or ";;" in the beginning of said line. Note that this is only *outside* of bibtex entries.
Now, what happens if one does this with files that are displayed using your (amazing! :)) service?
All the information is displayed correctly, so it does not lead to any errors. *However*, when dispaying the bibtex code on an individual item, it will not just show its bibtex code, but also all comments in the file until the next bibtex entry starts. Here a screenshot to illustrate:
In this example, showing "% submission 1" makes sense because no bibtex follows for it (so that comment should maybe not even have been included as the respective paper entry doesn't exist. The next comment, "% submission 2" is the "headline" above the respective next bibtex entry that's (correctly) not shown.
Instead, simply no "comments" should be shown at all, or in other words: the rule what to show should be changed to stop after the current entry has been displayed.
For reference, the following might be useful for debugging:
- File this is taken from: https://icaps24.icaps-conference.org/program/workshops/hplan/hplan.bib
- Webpage where it is displayed: https://icaps24.icaps-conference.org/program/workshops/hplan/ (note that multiple bibtex files are shown on that page, but that should not influence this behavior)

entries appear duplicated when searching
(I've posted that already as a follow-up on a closely related thread, but I didn't receive a reply yet and I can't reply to it further, so I re-post it here in its own thread.)
First, where to find the data that proves the bug:
- bibfile: https://bercher.net/bibtex/bibliography.bib
- page with search field: https://bercher.net/my-publications/all-publications
Bug description:
When
some works have the same title and authors (but different venues, e.g.,
first a workshop and then they turn into a conference, or they are
first a conference and then there's an extended tech-report), then:
- they first appear *correct* in the publication list, *but*
- once *any* search was used, they become duplicated.
How to verify that bug?
- Open the webpage above and *without using the search* navigate down to 2008. You will see two different entries:
- Now use the search. Type anything, doesn't matter! Then delete it again
-
To have a second example, you can also check out the papers with
keys Johnson2022aSATPruning and Johnson2022bSATPruning; this gives the
same behaviour.

entries appear duplicated when searching
(I've posted that already as a follow-up on a closely related thread, but I didn't receive a reply yet and I can't reply to it further, so I re-post it here in its own thread.)
First, where to find the data that proves the bug:
- bibfile: https://bercher.net/bibtex/bibliography.bib
- page with search field: https://bercher.net/my-publications/all-publications
Bug description:
When some works have the same title and authors (but different venues, e.g., first a workshop and then they turn into a conference, or they are first a conference and then there's an extended tech-report), then:
- they first appear *correct* in the publication list, *but*
- once *any* search was used, they become duplicated.
How to verify that bug?
- Open the webpage above and *without using the search* navigate down to 2008. You will see two different entries:
- Now use the search. Type anything, doesn't matter! Then delete it again
- To have a second example, you can also check out the papers with keys Johnson2022aSATPruning and Johnson2022bSATPruning; this gives the same behaviour.

undefined
https://wujastyk.net/bibtex/bibbase.html
At the top of my bibliography, BBase says "Undefined (6192)" where 6192 is the number of entries in my bib. What is "undefined"? Is it because I use biblatex format and "date" instead of "year"?

I added new publications to mendeley, however the same is not reflected on BibBase
I recently uploaded new publications to my mendeley library, however they are not reflected on BiBBase.
What do I do?

Group by breaks LaTeX formatting
To reproduce, for example with my file (https://bibbase.org/show?bib=https://florentfo.rest/files/publications.bib)
1. Last paper of 2023: "Selecting the Number of Clusters K ..."
2. Click on Group by > Year (or any other option)
3. It becomes "Selecting the Number of Clusters $K$ ..."

Download count is "undefined"
When clicking on "group by > downloads", the resulting download count is always "undefined".
This happens for every bibbase I have tested so far, on every website.
I remember it working several years ago. Did something break?

Sort by year range
Hi there,
I'd like to sort my BibBase in terms of year ranges (1950-2000, 2000-2010, 2010-2020, 2020-today/2030). Not sure how to do this, or even it is possible. I tried working with group0, group1, etc but that didnt make it.
The script I am running on my webpage is:
<script src="https://bibbase.org/show?bib=https://bibbase.org/f/Te2uYJttNXZTTEPJt/Website.bib&jsonp=1&folding=1&theme=side&commas=true&hidemenu=true">
Thanks for the help. Love the tool by the way!!

HandlebarsJS and Underscore.js
Hello,
We recently started using BibBase for embedding our publication list on our website, but the IT support in our department noted a vulnerability issue related to this implementation. Specifically, we identified that the issue comes from the following line of the code on our webpage:
The vulnerability diagnostics indicated that the solution is to upgrade the HandlebarJS and Underscore.js on the remote server.
I have limited knowledge on IT and security so my request might be irrelevant, but I am wondering if the issue could be resolved by upgrading those two JS versions on your server?
Thanks in advance,
Hakase
Kundesupport af UserEcho