Your comments
OK, yes, my previous selection was a little too sloppy. Could you try this one instead?
#group_article div.bibbase_group i+span { display: none; } #group_inproceedings div.bibbase_group i+span { display: none; } #group_article div.bibbase_group i:after { content: " Journal Articles" } #group_inproceedings div.bibbase_group i:after { content: " Conference Publications" }
Good point. Yes, it would probably be better to only selectively remove titles. You can use
Yes and no. There is such a list, on every bibbase page out there, but there is no explicit documentation. CSS is sort of self-documenting, you just go into the page source and inspect the elements you care to change. On Chrome just right-click on the part of a page you want to change and select "Inspect Element".
#group_article div span { display: none; }and similarly for all other titles you'd like to replace.
Yes and no. There is such a list, on every bibbase page out there, but there is no explicit documentation. CSS is sort of self-documenting, you just go into the page source and inspect the elements you care to change. On Chrome just right-click on the part of a page you want to change and select "Inspect Element".
Yes, this can be accomplished using CSS. Just drop the following into the CSS file on your page:
.bibbase_group span {Similarly you would need to set new titles for the other groups (incollection, book, etc.).
display: none;
}
#group_article div i:after {
content: " Journal Articles"
} #group_inproceedings div i:after {
content: " Conference Publications"
}
Confirmed, and very strange. Not sure what was happening there, but after restarting the process it seems to now be working again.
Thanks for reporting this. This issue should now be resolved. Please try again and let me know if the issue persists.
Looks very nice.
Hi David,
Good catch. The order in which the css links are added to the header were indeed wrong. The one specified with the css parameter should indeed go last. This is fixed now. If you are extending the side theme then just make sure you use that as a theme, so that in your custom css you don't need to overwrite (respecify) too many things. Please let me know if that doesn't work for some reason.
Good catch. The order in which the css links are added to the header were indeed wrong. The one specified with the css parameter should indeed go last. This is fixed now. If you are extending the side theme then just make sure you use that as a theme, so that in your custom css you don't need to overwrite (respecify) too many things. Please let me know if that doesn't work for some reason.
I just restarted the server and the problem went away. I haven't yet dug deeper into the logs to see what may have caused it. I haven't seen a slow down like this in at least six month. But keeping it under control is not challenging. I might just restart the server automatically once a day, which is somewhat common practice. Another solution for this would be load balancers, which we'll probably put in place soon if bibbase keeps growing at the current pace.
Customer support service by UserEcho
1) Not directly, but you could add an additional bibtex field to each of your publications where you provide a group name you would like to use and sort by and prefix that with a number (for sorting), e.g., "1 - Conference Papers", "2 - Journal Articles". If you then want to just use the number for sorting but not display it, then you can do that too using CSS. Let me know if this is an option for you and I can walk you through it. It would involve having some more maintenance on your part to add those group names.
2) Yes, you can easily accomplish this by adding the following to your CSS:
3) No, no, that is not necessary. It is just that *someone* needs to load the page twice. Not everyone. The caching happens on the server side at bibbase.org not on the client. So after updating your .bib file, just reload the page once (or twice to see the update), and the next time some one comes to your page, he or she will get the latest and greatest.