As a brief follow-up, I need to report that both the issue about widgets and the issue about margins are stuck:
0. Footnotes in widgets
Elementor advised to move the issue to GitHub: https://wordpress.org/support/topic/accordion-headings-declared-as-widgets-clash-with-other-plugins/
It turns out that we need to fix another bug in Footnotes to begin with. Footnotes inserts a reference container at the bottom of each widget that has footnotes, yet it is unable to make them functional, as every reference container in the same page is given the same function names and arguments. No matter if the widgets are added inline by Elementor when making an accordion, or in the widget area, footnotes in widgets are a non-starter.
As the only quick fix, the widget_text hook is now disabled by default, and a warning has been added in the dashboard not to enable it. That will be in our upcoming bugfix release 2.1.4.
Depending on the content, declaring accordion headings as widgets and getting Footnotes to append individual reference containers may even be good design, as it may be preferred, see https://wordpress.org/support/topic/reset-footnotes-to-1/#post-13662830
Post authors should be enabled to control the number of reference containers: one per page vs one per toggle section. These should then have widget status, as they are having in Elementor, and it’s up to Footnotes to provide shortcodes and to enable/disable hooks on a per-post basis, not globally only. And, as mentioned, it’s up to Footnotes to disambiguate multiple reference containers within a page.
More specifically, reference containers should enable to read on at whatever footnote referrer, so if the container is at the bottom of a page featuring an accordion, each backlink click should also expand the relevant heading.
(1. has been fixed as previously reported.)
2. Margins around the reference container
This has been reported too, on the Hello Elementor theme forum: https://wordpress.org/support/topic/appended-features-out-of-layout-when-page-created-with-elementor/ but has not received any answer so far, while it does not link to open issues on the Footnotes forum either; and since it is code-related too, the same response applies: move it to GitHub. This one will probably be a better fit for opening an issue over there at this point. I didn’t proceed yet because the problem can be fixed on a per-case basis (using custom CSS or an up-coming style setting in Footnotes), and because we’re still busy with fixing bugs and meeting basic expectations and requirements.
-
This reply was modified 3 months ago by
pewgeuges.
-
This reply was modified 3 months ago by
pewgeuges.