Rahmat,

I think the cause in your case is different than in Cedric's. I have not been able to see/reproduce the issue on Cedric's page, but on your's I see it. The issue on your page is that the style sheet is never loaded, which is also why the buttons don't show up, and the embedding message is shown at the bottom (should be a modal).

Looking at the console it shows the error:

Uncaught TypeError: Cannot read properties of null (reading 'noConflict') at (index):289

This refers to jQuery. When I looked at your page source, to find out which version of jQuery you are loading, I noticed that jQuery seems to be copied into your page in full!

let jqueryParams=[], jQuery=function(r){return jqueryParams=[. ....

There are several reasons not to do this, one of them being that it is *much* faster to load them from a CDN, because most people will already have jQuery cached, and the version you have seems to be missing some compatibility features.

Can you try replacing that script tag where jQuery is included with

<script src="https://code.jquery.com/jquery-3.6.0.min.js"></script>

or just remove it completely? BibBase will load jQuery when it doesn't find it on the page.

No, the issue is that for some reason your page is explicitly enforcing ascii encoding. This is at the top of your html file:

<?xml version="1.0" encoding="US-ASCII"?>

These xml headers are no longer recommended. I would remove it and to be safe also add

<meta charset="UTF-8">

to your html head.

Could you point me to your page? Then I can have a look.

Hi Nir,

This is because the site that is hosting the paper refuses to run in an iframe. This is becoming more and more common. We strong recommend not embedding BibBase via an iframe. In your case, it seems that you are actually just embedding one of your own pages, hosted elsewhere, in this site, and that other html page contains nothing but the script tag for embedding BibBase. Does Wix now allow you to use the script tag directly? If it id, that would make for a much better solution for several reasons: you wouldn't have a scrolling page within a scrolling page (confusing to your users), and the issue at hand of opening links would be resolved.

Let me know if there was anything not working with that direct use of the script tag that I may be able to help with. Otherwise, if you want to stick with the iframe, then I think this is a solution: https://stackoverflow.com/questions/1037839/how-to-force-link-from-iframe-to-be-opened-in-the-parent-window

Christian

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.