@mmallett,
I’m so sorry about the priority fix that unexpectedly broke other things, and I heavily apologized and we rolled back and now have a trustworthy developer version, currently our release candidate 1 for upcoming definitive v2.0.5. That is also something that in the hassle I got wrong: No live testing, by no means. I’m only striving hard to fix all and everything.
I’m releaved to see that you are using v2.0.4 and the footnotes container is at the bottom of markmallet.com/blog/ according to the post you shared above.
I’ll head over to the other, new bug report! Sorry for being late.
Best regards,
@pewgeuges
-
This reply was modified 5 years, 6 months ago by
pewgeuges.
@mmallett,
Hopefully v2.0.6 released a few minutes ago will fix it. It reverts to the development line followed for v2.0.0 and newer except v2.0.5 where additionally, priority level has been changed to meet user expectations: one user regularly edited that file to do the exact same. But that is now history, the current stable version does only HTML, CSS and related to improve user experience on the served web pages.
Please let us know if your bug goes away by itself or if we need to figure out another way to fix it.
Best regards,
@pewgeuges
No, this has put all footnotes on the main page at the bottom but when you open the articles, there are no longer footnotes.
https://www.markmallett.com/blog/category/daily-journal/
I’ll have to revert to 2.02 quickly as this is really messed up.
Mark,
I seem unable to comprehend the problems you are pointing out on markmallett.com/blog/ The home page has no footnotes, and pages are having footnotes balanced:
With currently used 2.0.4, the page https://www.markmallett.com/blog/fr-dolinos-incredible-prophecy/ is served to me in an almost perfect state. The missing superscripting of the footnote referrers is fixed in current 2.0.6 by discarding these rules:
vertical-align: top !important;
position: relative !important;
top: 0.6em !important;
The predelay of the mouse-over box is dropped, too (I’d doubled it from 400ms to 800ms to leave time clicking, in case), but these parameters should make it into the dashboard.
If I may go on giving a piece of advice, I’d suggest to set a maximum width for the tooltip infobox to avoid too long lines, contrasting with your website’s theme layout, and to better fit markmallett.com/blog/ subject and tone, as shape conveys solemnity.
Please help us understand the issues that make you consider reverting to 2.0.2.
Best regards,
@pewgeuges
I don’t know what happened. I had to go back to 2.04 because all the footnotes were appearing in the summary on the home page, but not at the bottom of the article once opened up. I reverted back to 2.02, which is probably what you saw just now.
Please don’t revert to 2.0.2 given 2.0.4 works for your website as I saw a couple hours ago. From 2.0.0 to 2.0.3, jQuery UI was fetched from a third party as I’ve been advised (and I’m fine with it), but after an alert, still on this forum, 2.0.4 switched to the WordPress way (that I’ve looked up at that point for that purpose). That’s why we are advising to use 2.0.4 (at least).
Since currently https://www.markmallett.com/blog/a-gospel-for-all/ is using 2.0.4, the footnote referrer styling is suboptimal because it wasn’t before these days that I understood how detrimental these three legacy style rules really are. They cannot be kept. You may wish to delete them yourself in 2.0.4 to get the superscript footnote referrers right.
Beside that, here is the full list of what we could have if we all could use 2.0.6:
= 2.0.6 =
– Update: Autoload / infinite scroll support thanks to @docteurfitness
– Bugfix: Layout: Footnote referrers: deleted vertical align tweaks for cross-theme and user agent compatibility
– Bugfix: Layout: Reference container: fixed line break behavior in footnote # clusters
– Bugfix: Layout: Reference container: auto-extending column to fit widest, to fix display with short note texts
– Bugfix: Layout: Reference container: IDs: slightly increased left padding
– Bugfix: Translations: fixed spelling error and erroneously changed word in en_GB and en_US
– Update: Typesetting: discarded the dot after footnote numbers as not localizable (should be optional)
– Bugfix: UI: Reference container: Collapse button fully clickable, not sign only
– Bugfix: UI: Reference container: Collapse button ‘collapse’ with minus sign not hyphen-minus
– Update: UX: Tooltip: set display predelay to 0 for responsiveness (was 800 since 2.0.0, 400 before)
– BUGFIX: Priority level back to PHP_INT_MAX (ref container positioning not this plugin’s responsibility)
= 2.0.5 =
– Bugfix: Get references container close to content, not below all other features, by priority level 10
– Bugfix: Public style sheet: Reference container: unset width of text column to fix site issues
– Update: Enable all hooks by default to prevent footnotes from seeming broken in post titles
– Bugfix: Restore cursor shape pointer over ‘Continue reading’ button after hyperlink removal
– Bugfix: Settings style sheet unenqueued to fix input boxes on public pages (enqueued for 2.0.4)
Hopefully we’ll end up finding out.
Best regards.
Awesome, will look for the update. And my apologies, I meant 2.04, not 2.02.
@mmallett
I beg everybody’s pardon and, in this thread of yours, your pardon in particular.
I inadvertantly introduced a bug in v2.0.5. It lasted in 2.0.6. 3½ days after, it was found and fixed immediately v2.0.7 see https://ww.wp.xz.cn/support/topic/change-the-position-5/page/2/#post-13630114
Timing of delays and fade speeds should become fully customizable. I can be hand-edited in wp-content/plugins/footnotes/templates/public/tooltip.html:
predelay: 0,
fadeInSpeed: 200,
delay: 400,
fadeOutSpeed: 200,
Scroll speed and offset in turn are accessible at the bottom of wp-content/plugins/footnotes/templates/public/reference-container.html:
if (l_obj_Target.length) {
jQuery('html, body').animate({
scrollTop: l_obj_Target.offset().top - window.innerHeight * 0.20
},
380);/*speed*/
}
These shall also become fully customizable.
Best regards,
@pewgeuges
-
This reply was modified 5 years, 6 months ago by pewgeuges.
@mmallett
Sorry for trying to reach out eventually without your consent.
As a support follow-up service I just checked your website whether footnotes are okay, because other websites reported a tooltip settings problem after upgrading to v2.1.1: The setting Customize > Mouse-over box > Use alternative tooltip implementation needs to be set to No, but it automatically turned to Yes because I only noticed for 2.1.2 that boolean select boxes need an explicit ‘no’ instead of an empty string like checkboxes use for ‘false’.
After being relieved that the footnotes tooltips on your website are okay, I noticed that in the reference container’s left column and over the backlinks, the mouse pointer has now default shape instead of pointer shape.
The 2.1.0 table row template needs the 2.1.0 style sheet, whereas the 2.1.2 style sheet when applied to the default table row template needs the ‘pointer’ class for the mouse cursor to take the pointer shape, for backwards compatibility with the three-column layout (arrow in column 2) that support has been added for in 2.1.1 with respect to its staying in use.
I do appply semantic versioning, but my understanding of a bug is larger than usual: everything that is fixed without deliberately adding a new feature. I see that this may be confusing, and therefore I’ll revert to a more classic definition of a bug as something that is broken and can be fixed without interfering with other things. I’m aware that CSS class names should not be changed, as they are used in customization. On the other hand, all files of a given version being used together is a usual assumption.
I’m sad that I’ve inadvertently broken your website, seemingly by making a false assumption. I just can’t apologize while not understanding the origin and rationale of the mix. I’d be thankful for any related information and am committed to do my best to deliver the best possible user experience, both for website owners and website visitors.
Best regards,
@pewgeuges
Hi there,
Yes, something is indeed broken. On countdowntothekingdom.com, the footnotes are no longer appearing at the bottom but visible in the body of the text. What do I do?
The website is mess. I’ve had to revert to another plugin for now. Essentially, the footnotes on this site no longer appear at the bottom but in brackets within the body of the text as if footnotes was deactivated.
@mmallett
@nikelaos had a similar issue and solved it as reported in https://ww.wp.xz.cn/support/topic/doesnt-work-any-more-11/#post-13676705
It may be necessary to check plugin conflicts and to change the priority setting of the_content hook under the Expert mode tab in Footnotes’ dashboard. Footnotes 2.1.2 shows information about priorities, namely:
The priority level determines whether Footnotes is executed timely before other plugins, and how the reference container is positioned relative to other features.
Default 9223372036854775807 is lowest priority, 0 is highest.
To restore default priority, set to -1, interpreted as 9223372036854775807, the constant PHP_INT_MAX.
For the reference container to sit above related posts, the priority level of the_content hook may need to be at most 1200.
For Footnotes to work when a glossary plugin is active, a higher priority of 1000 may be needed.
For the_content, another good pick with proven efficiency is priority level 10.
Footnotes is run with lowest priority by default, and that was hard-coded in class/task.php. That caused a number of issues, from wrong positioning to total disabling.
Priority level is now a setting next to the relevant hook checkbox, but only since 2.1.2 (2.1.1 for the_content).
May you please check this out and let us know if it solves the issue?
Thank you.
-
This reply was modified 5 years, 6 months ago by pewgeuges.
