By the way, if you are using one of Weebly's paid plans, then you might be interested in considering one of our new premium plans, which include a hosted web site as well (starting at $4/month). It goes without saying that setting up a BibBase-rendered publication list on our sites is well supported and even easier than embedding it on a page hosted elsewhere.

Thanks for doing that test. Hm, then it indeed somehow seems to be related to the presence of BibBase on the page, or the library it loads (perhaps jquery). I've taken another look at your page. I noticed that you are using a very old version of jquery (1.8.3, current version is 3.6.0). BibBase uses it's own version of jquery and knows how to avoid conflicts with any existing version already on the page, but since that version is so old, I cannot say for sure that we have ever tested that combination. Any chance you could try using a newer version instead? (>= 3.0.0)

Hi Nir,

I see the problem, but I don't think this has anything to do with the Bibbase elements on the page. To test this, just replace the script tag of bibbase with a large div, e.g.:

<div style="height: 200vh; background-color: yellow">This is a test</div>

and then try scrolling again. I think it will be the same issue.

When I scroll on your page with the developer console open, I see that something is changing the class and/or size of the body tag. This causes some flickering. I would look more in that direction.

Hi Till,

I moved it to bugs. And sorry for the delay. Yes, this feature is in flux right now and needs some attention. However we really need to focus on our premium features and our paying customers right now in order to become sustainable. On that note, let me know if KBSG or the i5 (or any other department in Aachen that you know of) might be interested in some of our premium features described in our recent blog post. It would be much easier to justify prioritizing this right now if the group signed up for one of our premium plans.

Please say hi to Gerhard!

Christian

Gustavo,

You are using an https:// URL but your web server doesn't have a valid SSL certificate:

> curl https://www.gustavocevolani.it/Cevolani-Publications.bib
curl: (60) SSL: no alternative certificate subject name matches target host name 'www.gustavocevolani.it'
More details here: <a href="https://curl.haxx.se/docs/sslcerts.html" class="redactor-autoparser-object">https://curl.haxx.se/docs/sslcerts.html</a>

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

Please either use http://www.gustavocevolani.it/Cevolani-Publications.bib or get a valid SSL certificate for your webserver.

Hi Gustavo,

The "fix" actually does work in your case as well, but it seems that there was a caching issue. I've loaded your publications with nocache=1 using this link. And now the links on your page seem fine again. Please make sure to change the bibbase url in your page source (it still has http://bibbase.org/show?bib=www.gustavocevolani.it/Cevolani-Publications.bib&jsonp=1 right now), to make sure this doesn't break again.

Best,

Christian

Hi,

When adding more than one parameter to a URL you need to separate them by "&", not "?". The question mark is only used as the beginning of the parameter list.

Try this in your page:

<script src="https://bibbase.org/service/mendeley/7a51828e-9782-3fa4-8bdb-357443954bfc/group/b49ab5c8-edb7-3544-9fc1-ebbc7f3ac750?jsonp=1&filter=keywords:Cross"></script>

Christian

Got it thanks. Yeah, that won't work. We will not be able to support alternative automation pipelines. Unless you want to add some transformations into your synchronization scripts such that these special, non-standard bibtex features we've added to BibBase will be handled the same way, then the result will not look the same.

I'm confused about the data flow you want. You seem to be manually exporting bibtex from Zotero. Is that the plan going forward? If so then you can directly change it to @thesis and use type = {bathesis}. If you let BibBase fetch it from Zotero then you should be getting the same result as me.

We are making good progress narrowing this down. The reason why you are seeing different results than me is actually for another reason: Your four publications all have the same bibbaseid (generated from title, year, and author names). What you are seeing is actually just the last one rendered four times. This is a known issue but almost never happens in practice because, well, most people don't publish different papers with the same title in the same year and with the same authors.

And yes, bibbase will not recognize Bathesis, only bathesis. But my test with Zotero shows that setting the type field to 'bathesis' in zotero, results in the same 'bathesis' in the exported bibtex.