Forum Replies Created

Viewing 15 replies - 1 through 15 (of 25 total)
  • Plugin Contributor Rumperuu

    (@rumperuu)

    Hi @happyches,

    I’ve just tested the page you provided on two different mobile devices (one running an Android variant and the other running an old proprietary OS), and both rendered correctly. Could you please provide more details on the mobile device that you are using? In particular, the operating system + version as well as any browser extensions you are using (if any).

    Plugin Contributor Rumperuu

    (@rumperuu)

    Glad to hear that you’ve got it sorted @morsagmon; thanks for the fix @pewgeuges!

    FYI the Plugin doesn’t currently have any options for per-page enabling/disabling (as you’ve seen), and a solution that involves editing the Plugin files directly will be overwritten the next time that the Plugin upgrades. You may find it safer to use another Plugin for disabling footnotes on a specific page; I can’t vouch for any personally, but this article provides some examples, and there is also this one.

    Plugin Contributor Rumperuu

    (@rumperuu)

    Correct, the footnotes refs will be untouched by the un- and re-installation of the Plugin.

    Plugin Contributor Rumperuu

    (@rumperuu)

    Hi @polaatx,

    Sorry to hear you are having issues with the Plugin. It looks like the Plugin may have upgraded incorrectly; please completely delete the footnotes/ directory in wp-content/plugins/ and re-install a fresh copy of the plugin.

    Plugin Contributor Rumperuu

    (@rumperuu)

    Hi @drjkiel

    Sorry for being unclear, the link to the code was just to highlight the description text for the ‘Combine Identical Footnotes’ setting, which reads (emphasis mine):

    Even when footnotes are combined, footnote numbers keep incrementing. This avoids suboptimal referrer and backlink disambiguation using a secondary numbering system. The Ibid. notation and the op. cit. abbreviation followed by the current page number avoid repeating the footnote content. For changing sources, shortened citations may be used. Repeating full citations is also an opportunity to add details.

    So there is no solution available at the moment, but we are working on updating the footnote parsing functionality and will hopefully be able to offer properly-numbered combined footnotes once that is finished (and you can track progress on the GitHub Issue).

    Plugin Contributor Rumperuu

    (@rumperuu)

    Hi @companydebt and @drjkiel,

    Thanks for the support request, sorry for the delay in replying to you.

    The continuation of footnote numbering even when combining identical footnotes is a workaround for the existing footnote parsing algorithm (as per the description on the Plugin settings page, see https://github.com/markcheret/footnotes/blob/main/src/class/dashboard/subpage-main.php#L498). Obviously this is not ideal.

    However, we are currently in the midst of a major revamp of the codebase, which will include re-doing the current the parsing algorithm. I’ve created an Issue to track this feature request, and we will try to include the option to properly combine identical footnotes in a future release.

    Thank you for using footnotes!

    • This reply was modified 4 years, 6 months ago by Rumperuu.
    Plugin Contributor Rumperuu

    (@rumperuu)

    No problem, glad to hear you’ve got it sorted!

    Plugin Contributor Rumperuu

    (@rumperuu)

    The first rule is the default set of values, and the values will only be overwritten by those in the second rule (i.e., the one wrapped in the @media query) if the user’s display is wider than 768 pixels.

    I’ve had a look at the coffee site you shared again, and it looks like both rules are being correctly applied — as I adjust the width of my display, I can see the second rule toggling on and off as expected.

    What Web browser are you using to view the site? If you are using a particularly old version, it may not support CSS media queries (see version information here), in which case the second rule will be ignored.

    Plugin Contributor Rumperuu

    (@rumperuu)

    @solu78 as a potential alternative temporary solution, the following may also be helpful — it seems to work on the coffee page you shared earlier, which I assume is still using the non-alternative tooltips setting?

    
    .footnote_tooltip {
      width: 80%;
      left: 10% !important;
    }
    
    @media screen and (min-width: 768px) {
      .footnote_tooltip {
        width: 75%;
        left: 50% !important;
      }
    }
    

    This should ensure that the footnote tooltips a) do not get squished at the side of the page and b) are always visible, regardless of the display width. The first rule means that tooltips will take up 80% of the text width and display center-aligned on mobile devices, whilst the second rule means that on wider displays the footnotes will take up 75% of the text width and display right-aligned. You can change the width & left values to suit your preference.

    It looks like I might have to wait until the new update — or perhaps I can hire a developer to custom-tweak this plugin?

    footnotes is an all-volunteer project, but if you were interested in helping to fund development then we do have a donation link here. This would not guarantee feature request precedence, but it would enable us to focus more resources on getting the 3.0 update out the door asap!

    Alternatively, if you wanted to fund a developer to specifically work on this feature, freelancer sites like Upwork and Fiverr may be helpful. footnotes is licensed under the GNU GPL 3.0, so there would be no obligation to share any work done back with us, but we would certainly appreciate it if you did! 😉

    Plugin Contributor Rumperuu

    (@rumperuu)

    Hi @solu78,

    FYI we are aware that the library we are using to render the tooltips (jQuery Tools) is very outdated, and we are working on replacing it in an upcoming major 3.0 update (you can see our discussion on this topic here).

    In the meantime, please let us know whether @pewgeuges’s suggested style rules help to alleviate the issue—as you’ve identified, just copy-paste this into the ‘Custom CSS’ tab within the Plugin settings area:

    
    .footnote_referrer_base {
        position: static;
    }
    
    .footnote_tooltip {
        position: relative;
        right: auto; /* or 0? */
        left: auto;
        top: auto;
        bottom: auto;
        width: fit-content;
    }
    
    Plugin Contributor Rumperuu

    (@rumperuu)

    Hi @nootropixcom,

    As @pewgeuges mentioned, the minimum supported version of PHP for this Plugin is 7.0 as of release 2.6.6.

    In the next major release of the Plugin (3.0), we will be raising this minimum to PHP 7.4 (in line with the minimum requirements of WordPress itself). We are exploring ways of automatically downgrading the Plugin source to support older PHP versions, but anything below the WordPress minimum will not be officially tested or supported by us.

    PHP 5.6 has been EOL since the end of 2018.

    Plugin Contributor Rumperuu

    (@rumperuu)

    Hi @msilvertant,

    I have just pushed an urgent 2.7.3 release to the server that fixes this issue. If you are not able to access the WordPress admin. dashboard for your site, please delete the wp-content/plugins/footnotes/ folder to remove the Plugin and it should work.

    I apologise for the inconvenience.

    Plugin Contributor Rumperuu

    (@rumperuu)

    Thanks for the information, I’ve fixed the issue and pushed an urgent 2.7.3 release. Please let me know if that solves the problem for you.

    Plugin Contributor Rumperuu

    (@rumperuu)

    Hi @ogbcashdown,

    Could you please provide more information on what error you are seeing, as well as your Plugin, WordPress and PHP versions?

    I’ve just double-checked both fresh installation and upgrading from a previous version on two different test sites and neither resulted in an error.

    • This reply was modified 4 years, 10 months ago by Rumperuu.
    Plugin Contributor Rumperuu

    (@rumperuu)

    Hi @zirafa,

    There appears to have been an issue with the latest release, resulting in outdated stylesheets being bundled with the Plugin. I have reverted the stable tag to 2.7.0 until we can resolve this; if you are not prompted to downgrade automatically, please download the 2.7.0 zip from here and replace the contents of wp-content/plugins/footnotes/ with the contents of the archive.

    • This reply was modified 4 years, 10 months ago by Rumperuu.
Viewing 15 replies - 1 through 15 (of 25 total)