Your comments

Have you already tried adding a field url_Code in your bibtex? See https://bibbase.org/help.

I haven't been able to reproduce this in Chrome yet, but will try Safari as well.

That would be helpful, yes. What are the symptoms of that? Does the publication list not load at all?

BibBase does not support sorting within groups. You can only group publications and those groups will be sorted. However you can have nested groups if you want. In your case, e.g., you could group by year first, and then by month next:

https://bibbase.org/show?bib=https%3A%2F%2Fapi.zotero.org%2Fusers%2F3649949%2Fcollections%2FE8UNN9WZ%2Fitems%3Fkey%3DbHPKkSJPRkAm4hCOP7l6ghDj%26format%3Dbibtex%26limit%3D100&groupby=year,month


Note however that BibBase sorts months as strings, i.e., lexicographical, not chronological. So this is probably not what you want either.


If you want more control over the order publications appear, then using a bibtex file as source will probably work better for you. In that case you can control the order by the order of appearance in the file.


BibBase doesn't belong to any company, no. It's an independent entity. Are you interested in sponsoring it?

Thanks for reporting! This was caused by our switch to HTTPs. It required a change in the Google login settings that had not yet happened. This is fixed now, please try again.

This is fixed now. It may take up to a day for everyone's browser cache to invalidate, but at that point, everything should work again. Of course, for those who know a hard-refresh of the page also works.


Thanks again for reporting!

Thanks for reporting! This seems to affect all BibBase pages, so this must be a regression that was introduced recently. We should be able to get this fixed by the end of the day today. Thanks again.


Hi Michael,


BibBase tries to detect whether bootstrap is already loaded and if so, it doesn't load it again and everything should work. In your case however, the detection mechanism didn't work because of the way the bootstrap you are including is named. You seem to be loading bootstrap locally from https://mikepsn.github.io/docs/js/bootstrap-3.3.7.min.js, which is not very common. Most people use the bootstrap CDN (which is faster), and that one names the file bootstrap.min.js, e.g.: 

<script src="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/js/bootstrap.min.js" integrity="sha384-JZR6Spejh4U02d8jOt6vLEHfe/JQGiRRSQQxSfFWpi1MquVdAyjUar5+76PVCmYl" crossorigin="anonymous"></script>
If you either use the file from the CDN or just rename your file (and change the URL) to bootstrap.min.js then it should start working.