Viewing 8 replies - 1 through 8 (of 8 total)
  • Exactly, same here, I am stuck with 2.2.5 for now

    Plugin Contributor pewgeuges

    (@pewgeuges)

    @lukashuggenberg @klusik

    My apologies both for the bug and for overlooking this topic, found only now while checking the unresolved topics.

    Back then, the problem was reported and resolved in these threads:

    https://www.ads-software.com/support/topic/two-links-now-breaks-footnotes-with-blogtext/#post-13825479

    https://www.ads-software.com/support/topic/footnotes-dont-show-after-update-to-2-2-6/

    https://www.ads-software.com/support/topic/bugs-in-every-2nd-update/page/2/

    Thank you for reporting the bug and helping fix the Footnotes plugin.

    Thread Starter lukashuggenberg

    (@lukashuggenberg)

    Hi,
    thanks for your reply, it’s never too late for kind words!
    I updated to 2.3 and alas have a new issue: scrolling down to the footnote from a reference clicked scrolls too far, and scrolling up from a footnote to it’s reference doesn’t scroll to the reference but somewhere below it.
    I’m sorry not having better news.
    I wish you a Happy New Year anyway!
    Kind regards,
    Lukas
    PS: no problem to stick to 2.2.5 –?I never do automatic updates!

    Plugin Contributor pewgeuges

    (@pewgeuges)

    @lukashuggenberg

    I’m sorry that you are having this issue. It sounds like the scroll offset is inverted on your website or staging site. A negative scroll offset would cause this exact behavior. Still, in Footnotes, the scroll offset cannot be negative—in per cent from the uppper window edge—so it would be inverted somewhere. The involved template reference-container.html shipped with 2.3 is still okay, as we may check in the relevant snippet:

    
    jQuery('html, body').animate({
        scrollTop: l_obj_Target.offset().top - window.innerHeight * [[scroll-offset]]
    },
    [[scroll-duration]]);
    

    To have a closer look into this issue, I’ve created a new post with 186?footnotes, and run a new test cycle switching themes, JavaScript and hard links enabled status, as well as various scroll offset configurations, prevented from becoming negative per the numbox parameters. But I’m unable to create a situation where the scrolling behavior would deviate from normal and expected. That outcome is congruent with that of the pre-release tests completed before our current v2.3.0—that you’re reporting an issue with—was rolled out.

    Trying to track the issue down, we’d need some website configuration information and ideally a link to an online staging page where the bug happens.

    Happy and Safe 2021!

    Best regards,
    @pewgeuges

    Thread Starter lukashuggenberg

    (@lukashuggenberg)

    Hi,
    Unfortunately my staging tool doesn’t let me set the staging site online for not logged-in users. But if you send me an email address where I can send you the credentials for an admin user I’ll gladly do so. Find my email address on my website d-tales.xyz
    Best,
    Lukas

    Plugin Contributor pewgeuges

    (@pewgeuges)

    @lukashuggenberg

    Thank you. My email is my WordPress username at Gmail. I’d be happy to transit by your website too.

    We’ll probably need to post an update here after finding out about the problem, and hopefully there will be a fix benefitting to all users.

    Thread Starter lukashuggenberg

    (@lukashuggenberg)

    Hi,
    email sent.
    Glad to help benefitting all users.
    Kind regards,
    Lukas

    Plugin Contributor pewgeuges

    (@pewgeuges)

    @lukashuggenberg

    Thanks a lot. The scroll-offset related issue was site-specific but will be addressed globally by initializing its variable to a useful default rather than 0. Thankfully the setting works again, and the reference container label and collapse button also become more robust in the process.

    This issue confirms again how usability-critical scroll offset is, and that zero offset is a non-starter both for soft links and for hard links.

    Best regards,
    @pewgeuges

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘2.2.6 breaks all footnotes’ is closed to new replies.