Footnote Display Truncated

@erickson18,

Thank you for reaching out. I didn’t see the topic when you opened it, until one hour later, and I see that meanwhile you marked it as resolved, yet you are still having issue #1.

I’ve tried to reproduce issue #1 in my sandbox but failed and can’t get to understand it. Looking at the code I can only confirm that a behavior close to what you are encountering is produced if and only if the [‌[/tooltip]‌] shortcode is present in the footnote text, and then there is no Read-on button.

(More options are upcoming, and this shortcode shall become configurable too.)

So we need to investigate this issue. I understand that the problem page is not published yet and I can’t get an easy chance to look at the page source. But you may test how longer footnotes look after turning tooltip truncation off, in Footnotes’ dashboard under the “Referrers and tooltips” tab > Tooltip truncation > Truncate the note in the tooltip ➜ No.

Issue #2 seems to be caused by an interference between parentheses and footnote delimiter shortcodes. E.g. when a footnote ends with a closing parenthesis, and the footnote end tag shortcode is )), you need to type a space or something else invisible between the parenthesis belonging to the footnote and those making up the shortcode. Avoiding that sort of issues is easy by switching to another shortcode. Personally I prefer triple braces, but double parentheses are widespread industry standard as they are used to delimit footnotes in other systems too, so they need to remain default configuration, the more as while the dashboard tab has not been saved once in a given instance, this instance uses the default settings and would be disrupted if we changed the defaults, so we need to be very cautious.

Please help us understand why you are having issue #1. E.g. you may wish to share some information such as the active theme, the other plugins in case there is an interference—that might be solved through priority levels—so that we can reproduce the exact environment where the bug happens.

Thanks in advance.

@erickson18,

Thank you for the information. I’m almost in the same situation. I couldn’t manage to build up the required sandbox, because I couldn’t get hold of the Grid One theme, installing Westview instead, first in the list of BoldGrid themes coming from the BoldGrid Inspiration plugin setup, and Footnotes is working fine; Editus on the other hand is out of reach for a quick test.

Three months ago I inadvertently introduced a bug in the Footnotes plugin that lasted from November 2 to November 6, in versions 2.0.5 and 2.0.6. It caused the formatted, truncated footnote to be embedded in the post, and the reference container to disappear or appear in random places with random content. It was due to the hook the_post that the original developer added support for in response to a request to support custom post types, and to me enabling it by default along with the other, content-related hooks. It was a weird mistake on my part that I apologized for in:
https://ww.wp.xz.cn/support/topic/change-the-position-5/page/2/#post-13630114
https://ww.wp.xz.cn/support/topic/footnotes-appearing-in-header/#post-13630303
https://ww.wp.xz.cn/support/topic/footnotes-appearing-in-header/page/2/#post-13630799
https://ww.wp.xz.cn/support/topic/no-footnotes-anymore/#post-13813233

But that happened three months ago. Can you confirm that you used v2.0.5 or v2.0.6, updated or installed at the start of November 2020?

Else I suspect an interference that is screwing things up. Probably you may need to reach out to BoldGrid support asking for compatibility with the WordPress plugin ecosystem. I never saw anything similar to what you got when you lost footnotes content. I’m sorry for the trouble you are experiencing.

Some issues can be solved by changing the priority levels, in Footnotes’ dashboard under the “Scope and priority” tab. Eventually you may search the Grid One and Editus codebases for their priority level of the_content hook.

Personally for a matter of using the WordPress blog engine I highly recommend sticking with WordPress themes and plugins so as to remain undisturbed while focusing on content, but I’m probably not in a position to give you good advice.

• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.

@erickson18,

You are welcome, but I notice in the datestamps that you posted earlier than the last edit that I made and that is very substantial; please let me repeat to make sure that you get the information along with my apologies and a question:

Three months ago I inadvertently introduced a bug in the Footnotes plugin that lasted from November 2 to November 6, in versions 2.0.5 and 2.0.6. It caused the formatted, truncated footnote to be embedded in the post, and the reference container to disappear or appear in random places with random content. It was due to the hook the_post that the original developer added support for in response to a request to support custom post types, and to me enabling it by default along with the other, content-related hooks. It was a weird mistake on my part that I apologized for in:
https://ww.wp.xz.cn/support/topic/change-the-position-5/page/2/#post-13630114
https://ww.wp.xz.cn/support/topic/footnotes-appearing-in-header/#post-13630303
https://ww.wp.xz.cn/support/topic/footnotes-appearing-in-header/page/2/#post-13630799
https://ww.wp.xz.cn/support/topic/no-footnotes-anymore/#post-13813233

But that happened three months ago. Can you confirm that you used v2.0.5 or v2.0.6, updated or installed at the start of November 2020? If so, you are a victim of my mistake and I beg your pardon for all the trouble!