Golemiq

Footnotes & Content plugin is a powerful method of adding footnotes into your posts and pages. You can have as many footnotes as you like pretty easily in every page, post or ACF block, WooCommerce is also supported. That is the fastest footnote plugin which is using extremely low resources – you wont even notice that it is there.
You can visit the <a href="https://github.com/sdobreff/awesome-footnotes/" title="Github" rel="nofollow ugc">Github page</a> for the latest code development, or if you want to report an issue with the code.
To gain more control over WP, directly from the WP admin – try out our plugin <a href="https://wordpress.org/plugins/0-day-analytics/" rel="ugc">0 day analytics</a>
<h3>Key features include…</h3>
<ul>
<li>Simple footnote insertion via markup of choice (default – double parentheses)</li>
<li>Gutenberg support</li>
<li>Combine identical footnotes</li>
<li>Paginated posts are supported</li>
<li>Suppress Footnotes on specific page types</li>
<li>Option to display ‘pretty’ tooltips using jQuery</li>
<li>Option to display footnotes as tooltips using vanilla JS</li>
<li>Lots of configuration options</li>
<li>Different footnotes settings per post – you can use different settings on Post level – changing styles and UI</li>
</ul>
Footnotes & Content plugin is designed to ease the creation of a new footnote. It also gives you the ability to easily switch from most of the existing footnotes plugins to this one. Lets face it – almost 100% of them are abandoned or in awful condition. It supports PHP8, it is written using best practices and follows the WordPress standards, give it a try. You can quickly check the plugin <a href="https://playground.wordpress.net/?plugin=awesome-footnotes&networking=yes" title="WP Playground" rel="nofollow ugc">here</a>
<h3>Technical specification…</h3>
<ul>
<li>Designed for both single and multi-site installations</li>
<li>PHP8 fully compatible</li>
<li>PHP multibyte must be installed</li>
</ul>
<h3>Getting Started</h3>
Creating a footnote is incredibly simple – you just need to include your footnote in double parentheses (default, but you can change that), such as this:
This is a sentence ((and this is your footnote)).
You can change the markup for the footnote in the settings page of the plugin.
The footnote will then appear at the bottom of your post/page.
Don’t put footnotes in short description / excerpts – the plugin won’t work there by design.
Or you can use a shortcode for where you want your footnotes to appear. The shortcode is “<code>awef_show_footnotes</code>“. The shortcode also accepts a parameter of the post id in format of ‘post_id=1’. If not presented, the global \WP_Post object will be used.
You can also use a PHP call in your templates or whatever you like by using the following: 
 AWEF\Controllers\Footnotes_Formatter::show_footnotes( array( ‘post_id’ => 1 ) ); 
Note: If you choose this way (above), you have to go to the plugin settings, and set “Do not autodisplay in posts” to true.
Advanced Custom Fields (ACF) are also supported out of the box – just read and keep in mind this:
Unfortunately there are limitations with the ACF because of its block structure. There is no way to guess how many blocks are there, which is first, second, are there more blocks or not … So every block will show its own footnotes, and shortcodes are not working outside them. Currently there is no way to achieve that functionality. So they are treated more like endnotes if there are multiple blocks using the footnotes tags.
What plugin does is to keep track of the footnotes and keep proper numbering among the blocks (again there is no way to guess which is which, so they are parsed in order of their callings from backend, but they can be shown in entirely different places on the front end.)
WooCommerce (including new product editor) is also supported.
Unlike any other plugin, this one gives you the ability to have different settings for different posts. When editing post, you can change the setting for the plugin which will apply for that specific post, and others will keep using the global settings. If you think that this is too much, you can always disable this from advanced settings.
<h3>Other plugins compatibility</h3>
There are plugins with which that one is 100% compatible – meaning that you can directly jump from them to this one:
<ul>
<li><a href="https://github.com/drzax/wp-footnotes" title="Github - wp-footnotes" rel="nofollow ugc">WP Footnotes</a></li>
<li><a href="https://wordpress.org/plugins/footnotes-made-easy" title="WordPress.org - footnotes-made-easy" rel="ugc">Footnotes Made Easy</a></li>
</ul>
<h3>Options</h3>
You have a fair few options on how the identifier links, footnotes and back-links look which can be found in the WordPress admin area either on the stand alone page, or under Settings -> Footnotes – that depends on your desired setting in the plugin.
<h3>Shortcode options</h3>
<pre><code>[awef_show_footnotes] Is the shortcode you should use. Inside the post content, there is nothing more that you have to do.
</code></pre>
If you want to use the shortcode outside of the post content, then you need to add the post id as a parameter: 
 [awef_show_footnotes post_id=1] 
If outside of the post content, and there is no parameter of the post id provided, then the plugin will try to use the global post if presented.
<h3>Paginated Posts</h3>
Some of you seem to like paginating post, which is kind of problematic. By default each page of your post will have it’s own set of footnotes at the bottom and the numbering will start again from 1 for each page.
The only way to get around this is to know how many posts are on each page and tell Awesome Footnotes what number you want the list to start at for each of the pages. So at some point on each page (that is, between each <code></code> tag) you need to add a tag to let the plugin know what number the footnotes on this page should start at. The tag should look like this <code></code> where “5” is the number you want the footnotes for this page to start at.
<h3>Referencing</h3>
Sometimes it’s useful to be able to refer to a previous footnote a second (or third, or fourth…) time. To do this, you can either simply insert the exact same text as you did the first time and the identifier should simply reference the previous note. Alternatively, if you don’t want to do all that typing again, you can construct a footnote like this: <code>((ref:1))</code> and the identifier will reference the footnote with the given number.
Even though it’s a little more typing, using the exact text method is much more robust. The number referencing will not work across multiple pages in a paged post (but will work within the page). Also, if you use the number referencing system you risk them identifying the incorrect footnote if you go back and insert a new footnote and forget to change the referenced number.
<h3>FAQ Schema Usage Guide</h3>
<h3>For Administrators</h3>
<ol>
<li>Edit any post or page</li>
<li>Scroll to the “Awesome Footnotes – Settings” meta box</li>
<li>Click the “FAQ Schema” tab</li>
<li>Click “Add FAQ Item”</li>
<li>Fill in the Question and Answer fields</li>
<li>Repeat for additional FAQs</li>
<li>Use move up/down buttons to reorder</li>
<li>Click Remove to delete items</li>
<li>Save/Update the post</li>
</ol>
<h3>For Content Display</h3>
<ol>
<li>In the post content editor, add: 
 <code>[awef_faq]</code></li>
<li>Publish/Update the post</li>
<li>View the post on the frontend</li>
<li>FAQs will display at the shortcode location</li>
<li>JSON-LD schema automatically added to <code><head></code></li>
</ol>
<h3>For Developers</h3>
Get FAQ data programmatically: 
 `php 
use AWEF\Controllers\Post_Settings;
$post_id = get_the_ID(); 
$faqs = Post_Settings::get_faq_schema( $post_id );
foreach ( $faqs as $faq ) { 
 echo $faq[‘question’]; 
 echo $faq[‘answer’]; 
} 
 `
Check if FAQ shortcode is used: 
 <code>php 
$content = get_post_field( 'post_content', $post_id ); 
if ( has_shortcode( $content, 'awef_faq' ) ) { 
 // FAQ shortcode is present 
}</code>

Footnotes & Content

Allows post authors to easily add and manage footnotes in posts.

designerken

Reftagger Shortcode creates a button in the TinyMCE visual editor in WordPress allowing you to easily add semantic Bible markup.
The Reftagger plug-in is a great plug-in except when it comes to finding verses that are by themselves in text.
Often when creating a sermon page for my church’s website I would have something like:
<ul>
<li>2 Corinthians 5:1-8</li>
<li>Our Destination – What we know (v.1)</li>
</ul>
<a href="http://reftagger.com" rel="nofollow ugc">Reftagger</a> plug-in doesn’t know that “v.1” was supposed to be verse 1 from 2 Corinthians 5:1-8 that was mentioned earlier in the text.
That’s where this shortcode comes in. Simply highlight the “v.1” text in the visual editor and click the reftagger button.
The shortcode is then placed in the main edit window as [reftagger title=””]v.1[/reftagger] and all you need to do is add “2 Corinthians 5:1” to the title attribute. The rest is handled by the plug-in, it will render the code in semantic Bible markup on the front end.
If you have the <a href="http://reftagger.com" rel="nofollow ugc">Reftagger</a> Bible reference plug-in active it identifies references to the Bible verses and turns the references into links to the verse on Biblia.com.
For more information on the Reftagger Bible reference plug-in, visit http://reftagger.com.
<h3>Usage</h3>
<ul>
<li>
The plugin will begin working immediately when you activate it on the ‘Plugins’ page.
</li>
<li>
You will get a notification if you do not have the “Reftagger” plugin active. You can dismiss the notification if you wish.
</li>
<li>
Go to your post or page edit screen and you will see a new icon in the visual editor.
</li>
<li>
Simply click the icon to place the shortcode in your main edit window at the location of your cursor.
</li>
<li>
You can also highlight text in the edit window and click the button to have the shortcode wrap around your highlighted text.
</li>
</ul>

Reftagger Shortcode

Reftagger Shortcode creates a button in the TinyMCE visual editor in Wordpress allowing you to easily add semantic Bible markup.

Footnotes & Content vs Reftagger Shortcode