Ваші коментарі
All,
Thank you for your patience. We are glad to finally be able to announce HTTPS support!
You can start using it immediately by changing your bibbase URLs to https://.
Please use this thread to report any issues you may observe.
Thank you for using BibBase.
I downloaded the bibtex file that Zotero generates for your publications (from the dropdown menu on the bibbase page), but there are no entries with a field called "extra". How/where are you adding these fields? Given the level of customization you are seeking, it might be better for you to generate your bibbase page from a bibtex file rather from Zotero, if that's an option for you.
ok, I've cleared the cache manually. It probably refused to update the cache because the bibtex file hadn't changed (just the parsing of it had). It's working now.
That seems to be a caching issue. http://bibbase.org/show?bib=blog.lausdahl.com/wp-content/uploads/publications/lausdahl.bib&nocache=1 works. However it doesn't seem to update the cache, which is strange. I'll investigate further.
Hi Ken,
Thanks for reporting and fixing(!!) this issue. I've merged your pull request for the parser and updated bibbase with the new version. The bibtex URL you provide seems to work now.
The syntax is different (filter=field:value, rather than filter:field=value) and the field "date" does not exist. You probably meant year, right?
Try this:
Yes, try this:
.bibbase_paper_title {
display: block;
}
span.bibbase_paper_author {
display: block;
}
br.bibbase_paper_content {
display: block;
}
Hi Markus,
Thanks for pointing us to Let's encrypt/certbot. I just saw it being announced by EFF as well. Seems like a good option. We'll investigate this.
Best,
Christian
I'm not sure I understand the issue. Why do you need a number to access the PDF files? Why not just use the `url` field in your bibtex to link to the PDF directly.
Служба підтримки клієнтів працює на UserEcho
Hi Gianluca,
Sorry to hear that. Could you tell me how you are embedding? (php?) The page is completely empty, which tells me that your web server is probably having trouble fetching the bibbase html. I suspect that is due to the release of HTTPs support which will redirect from http to https now.
I'm not sure why your web server is not following the redirect he is receiving on the http:// address, but one way or another you can fix this by changing your bibbase url to the new one, i.e., simply replace http:// with https:// in your embedding code.
Please do let us know though how you are embedding (and ideally also what web server you are running, if you know that), so we can investigate further and save other users from the same troubles.
Thanks!