Hi @micdt,
Thank you for reporting this bug. I’m very sorry and concerned, and I can’t figure out where it comes from.
I just worked on a similar problem with a part showing up where it doesn’t belong in: https://wordpress.org/support/topic/change-the-position-5/#post-13615862
Would you please share all the base URLs where you are observing the disorder? That will enable us to look into it.
Regards,
@pewgeuges
-
This reply was modified 3 years, 10 months ago by
pewgeuges.
Thread Starter
micdt
(@micdt)
Hi,
well, as mentioned reverting to 2.0.3 was the remedy. So you won’t see the bug on my pages right now.
https://nebenbei.mchlksr.de/
https://fotoblog.mchlksr.de/
The footnotes appeared in post which actually had no footnotes at all. So the database was messed up somehow.
mic
I have a similar problem. Footnotes on old, established posts seem to be stable.
But I detected two issues:
First: On old posts with no footnotes that link to a post that has them, the plugin will pull the footnotes from the last linked one into the post and slam it into the first text widget on a sidebar it can find.
Second: On posts that are being written, it will display the same behavior above if no footnotes are present. If footnotes are present, it will sometimes show the correct ones at the end of the page or random one. On top of that, you still find the headline on the widget, only it cannot be opened.
Up to the last version, the plugin worked fine. Rolling back does not fix it, though.
@micdt, @rockmusicraider,
I’m devastated. Seeing all your blogs messed up makes me sick. The only possible reason was the working fix for priority conflicts by setting the priority of add_filter() from PHP_INT_MAX to 10. Others always edited task.php to do that.
I was unable to anticipate the unexpected behavior, because with me it only fixed things and broke nothing.
The current stable tag 2.0.4 does not feature those edits. @micdt, you needed to roll back to 2.0.3, and 2.0.4 is bad already? That seems impossible to me because v2.0.4 doesn’t have critical changes. It restored the setting to customize the (now) prepended symbol, fixed minor bugs and updated all language files both in content and in references for future translators.
Above all, v2.0.4 fixed a GDPR issue by switching to the recommended enqueuing of jQuery UI. We strongly recommend that you discard v2.0.3 and upgrade to the current stable v2.0.4.
@rockmusicraider: I’m devastated about this mess. I tried hard to fix pre-existing bugs, and the blog engine turned it into the exact opposite, only because a plugin adding footnotes is executed before other ones so that the reference container displays close to the content, not below related articles and social icons.
I didn’t know that the sandbox where I tested this change is unable to produce what you are experiencing.
I apologize. On project side we’ve decided to set up a more performative test environment. There will also be changes in the development process. From now on, any bugfix will first be available in the developer version for download under the advanced tab until all changes are assessed as safe. Most bugfixes were so urgent and obvious that I went on to release stage because I couldn’t wait seeing everybody get their websites fixed.
That has now backfired. I’m so sorry I could wish I never joined the project. But that wasn’t a correct solution neither.
My Apologies!
@pewgeuges
Thread Starter
micdt
(@micdt)
@pewgeuges
Could be the issue came with 2.0.5. Not sure. The updates followed so very close to each other. But definitely rolling back from 2.0.5 to 2.0.4 did not fix it.
I could try to go from 2.0.3 to 2.0.4 now, but … °|°
mic
@micdt
I’m sorry that footnotes lost credit with you and apologize for the v2.0.5 rolled back due to an unseen bug reported by yourself and others and project-internal. The problematic bugfix was discussed on this forum beforehand.
Turned out the other plugins e.g. displaying related posts over and above the footnotes list can be fixed appropriately so as to display related posts below the footnotes list; it only takes replacing an internal variable with the PHP reserved constant used in Footnotes.
Sadly I didn’t find any page with footnotes on nebenbei.mchlksr.de/ using v2.0.3, nor on fotoblog.mchlksr.de/ using v2.0.4.
A GDPR issue has been fixed in v2.0.4, see https://wordpress.org/support/topic/gdpr-issue-with-jquery/ We recommend upgrading to v2.0.4.
v2.0.5 contained other urgent bugfixes than the one wrongly fixed on footnotes side (while today we know that it is other plugins’ responsibility), and as trunk was ready I needed to roll it back because of that issue. I’m sorry for flawing the process. For that never to happen again, we now have an up-to-date developer version featuring the latest fixes so we can respond to user requests immediately instead of pointing our users to the next release.
Current stable v2.0.4 will be superseded soon by the next bugfix releases. It’s a matter of minutes for our release candidate v2.0.5rc2 to be available at the bottom of https://wordpress.org/plugins/footnotes/advanced/
When normalcy is back for everyone, we’ll go on fixing bugs, start asking other plugins to become more interoperable, and eventually add missing features if some time is left.
My apologies, again.
Best regards,
@pewgeuges
Thread Starter
micdt
(@micdt)
Well,
actually I did not loose credit on your plugon. It is still the best of its kind.
On
https://fotoblog.mchlksr.de/fotografie/lightroom-mit-der-fotogalerie-x3-verheiraten/
you can see 2.0.4 at work without problems.
Same here:
https://nebenbei.mchlksr.de/gimmicks/distro-hopping-leichtgemacht/
But: When I installed 2.0.6 on nebenbei.mchlksr.de everything was messed up again.
mic
@micdt,
Thank you for your feedback. Following your alert I’ve stopped distributing v2.0.6 and set back to 2.0.4 since that works for you and conforms to GDPR.
2.0.6 is fine on my WordPress. We’re rolling out a more performative test program to be able to extrapolate from.
Best regards.
Alright, quick feedback:
Just updated to 2.0.8 and did some extended testing. The plugin now seems to return the correct results, as long as the hook “the_post” remains unchecked in the ‘Expert Mode’ tab. Well done and thanks for fixing this.
I apologize again (https://wordpress.org/support/topic/change-the-position-5/page/2/#post-13630114).
Thanks a lot for your feedback, and for the lenient handling of the big mistake I made. I’m so happy that everything returns to normal.
The post hook shall be removed from the plugin.
Best regards.
@pewgeuges
