Your comments
OK. Let me know what you find. I've also just pushed a small update that makes sure you get a proper error message now in the case you are encountering.
11 ár síðan
When bibbase tries to receive that bib file, it received the following message instead:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>419 unused</title>
</head><body>
<h1>unused</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
webmaster@seas.upenn.edu and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>
</body></html>
I can't quite tell you why at this point. I can manually retrieve your bib file using curl or wget just fine. But it isn't an error that I've ever seen before, so I do suspect that the message is true and that there might be something misconfigured with your web-server. Your admin should check the logs.
Sorry for displaying a more descriptive error message in this case. It just doesn't happen more than once in a blue moon.
-- Christian
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>419 unused</title>
</head><body>
<h1>unused</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
webmaster@seas.upenn.edu and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>
</body></html>
I can't quite tell you why at this point. I can manually retrieve your bib file using curl or wget just fine. But it isn't an error that I've ever seen before, so I do suspect that the message is true and that there might be something misconfigured with your web-server. Your admin should check the logs.
Sorry for displaying a more descriptive error message in this case. It just doesn't happen more than once in a blue moon.
-- Christian
Yes, of course :-)
You can do that with CSS. Just put the following into your style definition.
You can do that with CSS. Just put the following into your style definition.
.bibbase_stats_paper { display: none; }
Sorry, there was a technical glitch. It's fixed now.
No, this does not happen frequently and I'm working on reducing outages like this to zero.
No, this does not happen frequently and I'm working on reducing outages like this to zero.
OK, done. You can now use the new special field "bibbase_note" for this purpose.
Thanks for reporting. This is fixed now. You may need to update your cache for it to show up (using the &nocache=1 link you got when creating your bibbase page, or by making a small change to your library and then reloading your bibbase page).
Sorry for the delayed response. Yes, a very similar idea crossed my mind, too. I haven't seen much demand for it yet, so I may not be able to get to this very soon. But I'll keep it on my list.
I was also wondering whether people would like to have the ability to mark a small set of papers as "recommended". Often, when someone we know wants to read some of our work, the first thing they ask is: which of your papers on topic X should I read first? For that it might be good to add a start or something to the papers we personally think are the best ones to read.
What do you think of that?
I was also wondering whether people would like to have the ability to mark a small set of papers as "recommended". Often, when someone we know wants to read some of our work, the first thing they ask is: which of your papers on topic X should I read first? For that it might be good to add a start or something to the papers we personally think are the best ones to read.
What do you think of that?
Hi Maximilian,
Thanks for these links. The second one didn't work for me (I couldn't get the .bib), but the first one was very helpful for hardening BibBase. It turns out that the file had some issues, e.g., the use of invalid bibtex entry types (e.g., @conference and @url). While that is a problem with the input, I still want BibBase to be robust enough to handle that, and debugging with this file helped me accomplish that.
So now your file renders just fine---after a while ;-), it is pretty big.
http://bibbase.org/show?bib=https://raw.githubus...
Thanks for these links. The second one didn't work for me (I couldn't get the .bib), but the first one was very helpful for hardening BibBase. It turns out that the file had some issues, e.g., the use of invalid bibtex entry types (e.g., @conference and @url). While that is a problem with the input, I still want BibBase to be robust enough to handle that, and debugging with this file helped me accomplish that.
So now your file renders just fine---after a while ;-), it is pretty big.
http://bibbase.org/show?bib=https://raw.githubus...
Customer support service by UserEcho
