David Artiss

Patrick Lumumba

Divi Banks

Stoil Dobreff

Milimo Emmanuel

vikmark

Footnotes Made Easy is a simple, but powerful, method of adding footnotes to your posts and pages.
Key features include…
<ul>
<li>Simple footnote insertion via double parentheses</li>
<li>Combine identical notes</li>
<li>Solution for paginated posts</li>
<li>Suppress Footnotes on specific page types</li>
<li>Option to display ‘pretty’ tooltips using jQuery</li>
<li>Lots of configuration options</li>
<li>And much, much more!</li>
</ul>
Footnotes Made Easy is a fork of <a href="https://github.com/drzax/wp-footnotes" title="Github - wp-footnotes" rel="nofollow ugc">WP Footnotes</a>, a plugin by Simon Elvery which was abandoned some years ago.
Please visit the <a href="https://github.com/lumumbapl/footnotes-made-easy/" title="Github" rel="nofollow ugc">Github page</a> for the latest code development, planned enhancements and known issues.
<h3>Getting Started</h3>
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/LuXMb8Hz4tc?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
Creating a footnote is incredibly simple – you just need to include your footnote in double parentheses, such as this…
This is a sentence ((and this is your footnote)).
The footnote will then appear at the bottom of your post/page.
Important note: Make sure you include a space before your opening double parentheses or the footnote won’t work!
<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 under ‘Settings -> Footnotes’.
<h3>Paginated Posts</h3>
Some of you seem to like the paginating post, which is kind of problematic. By default, each page of your post will have its 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 Footnotes Made Easy 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>Available in 8 Languages</h3>
Footnotes Made Easy is fully internationalized, and ready for translations.
Many thanks to the following translators for their contributions:
<ul>
<li><a href="https://profiles.wordpress.org/dartiss/" rel="nofollow ugc">David Artiss</a>, English (UK)</li>
<li><a href="https://profiles.wordpress.org/markscottrobson/" rel="nofollow ugc">Mark Robson</a>, English (UK)</li>
<li><a href="https://profiles.wordpress.org/yayannabelle/" rel="nofollow ugc">Annabelle W</a>, English (UK)</li>
<li><a href="https://profiles.wordpress.org/maboroshin/" rel="nofollow ugc">maboroshin</a>, Japanese</li>
<li><a href="https://profiles.wordpress.org/wplmillet/" rel="nofollow ugc">Laurent MILLET</a>, French (France)</li>
<li><a href="https://profiles.wordpress.org/cansmile/" rel="nofollow ugc">B. Cansmile Cha</a>, Korean </li>
<li><a href="https://profiles.wordpress.org/danbilabs/" rel="nofollow ugc">danbilabs</a>, Korean</li>
<li><a href="https://profiles.wordpress.org/danbilabs/" rel="nofollow ugc">denelan</a>, Dutch </li>
<li><a href="https://profiles.wordpress.org/psmits1567/" rel="nofollow ugc">Peter Smits</a>, Dutch</li>
<li><a href="https://profiles.wordpress.org/nekojonez/" rel="nofollow ugc">Pieterjan Deneys</a>, Dutch (Belgium)</li>
<li><a href="https://profiles.wordpress.org/alexvgrey/" rel="nofollow ugc">Alex Grey</a>, Russian</li>
</ul>
If you would like to add a translation to this plugin then please head to our <a href="https://translate.wordpress.org/projects/wp-plugins/footnotes-made-easy" title="Translating WordPress" rel="nofollow ugc">Translating WordPress</a> page

Footnotes Made Easy


Adding footnotes is really easy, and they have nice links that go back to the footnote in the post.


Makes it really easy to create footnotes


Happy with this plugin as a seamless replacement for an old footnotes plugin that had stopped working with php8.


Works great

This plugin was great. Then the original developer got busy and passed it to another developper, who in months hasn't fixed small bugs that users takes the time to report, claims to be PHP 8.2 compliant, which is not. I believe the new owner was the wrong choice.

Plugin not updated anymore

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

kochm

Mendeley Plugin for WordPress is a plugin for displaying information from the Mendeley “shared bibliography system” (www.mendeley.com) in WordPress blogs.
Using the public API from Mendeley, meta-information on documents in personal, public or shared collections is loaded and formatted as bibliographic entries.
The lists can be included in posts or pages using WordPress shortcodes:
<pre>
[mendeley type="folders" id="xxx" groupby="xxx"]
[mendeley type="groups" id="xxx" groupby="xxx" style="cover,link"]
[mendeley type="groups" id="xxx" sortby="xxx" sortorder="xxx" style="short"]
[mendeley type="groups" id="xxx" groupby="xxx" filter="author=Michael Koch"]
[mendeley type="groups" id="xxx" groupby="xxx" filter="author=Michael Koch;type=journal"]
[mendeley type="groups" id="xxx" groupby="xxx" filter="type=book_section"]
[mendeley type="groups" id="xxx" groupby="xxx" csl="http://DOMAINNAME/csl/custom_style.csl" style="cover,link"]

- the attribute "id" is the Mendeley identifier of the group or folder - You can find this in Mendeley (Web or desktp app) - or use the function "Request Collection Ids" in the backend of the plugin - example value: 1f0508c0-8256-3ba7-b924-485e720245d5
- the attribute "type" can be set to "folders" or "groups" or "own"
- the attribute "groupby" is optional; possible values are all mendeley document attribute - see http://dev.mendeley.com/methods/#core-document-attributes - e.g. "authors", "year"
- the attribute "sortby" is optional; possible values are the same as for groupby
- the attributes "sortorder" and "grouporder" can have the values "asc" and "desc"
- sorting on the sort key is done before grouping on the group key if both are provided
- in "filter" one or more equal matches can be filtered for; if more than one filter rule is specified, than documents are displayed only when all filter rules match 
- possible attribute names to filter for are: type, title, year, author, editor, publisher, tag, keyword, abstract (when filtering for tag or keyword, a substring search is performed, so "blog" also matches "microblog")
- possible values for attribute type: ['journal' or 'book' or 'generic' or 'book_section' or 'conference_proceedings' or 'working_paper' or 'report' or 'web_page' or 'thesis' or 'magazine_article' or 'statute' or 'patent' or 'newspaper_article' or 'computer_program' or 'hearing' or 'television_broadcast' or 'encyclopedia_article' or 'case' or 'film' or 'bill']
- the attribute "style" controlls the output - you can specify several values separated by commas - possible values are: cover (add cover images), link (add links to full texts), short (use a short version - i.e. for widgets - not possible if csl formatting is used)
- the attribute "csl" is optional; the value must contain a valid URL with a .csl file
- the attribute "maxdocs" can be used to limit the number of documents displayed (e.g. maxdocs="10")
</pre>
<h3>Changes in v1.0 (December 2014)</h3>
In v1.0 of the plugin there are some important changes due to support 
for the new Mendeley API.
The most important issue is that ids of groups and folders now have to 
be uuids – so, you have to look up the ids again – e.g. using the list 
feature in the settings page of the plugin in the WordPress backend.
Additionally, some attribute names and possible values have been 
changed – so for example filters for type have to be changed.
We now also no longer support the outdated collection types “shared”, 
“sharedcollections”, “collections” – Only “groups” and “folders” are 
supported.
<h3>Known Problems</h3>
The current version of the plugin (v1.0) has one known problem with 
requesting and authorizing access tokens: When the activity is 
triggered in the backend using the Safari browser, the redirection to 
the Mendeley API site might not work (blank page) – If this is the 
case for you, please try with a different browser. For us Firefox has 
always worked.
<h3>Formatting</h3>
If you do not specify a CSL stylesheet, full entries are formatted the following way – so, the style can be tailored using CSS.
<pre>
 <h2 class="wpmgrouptitle">grouptitle</h2>
 
 $authors&lt/span>
 ($year): 
 $title
 , $publication_outlet
 $volume($issue)
 , $editors
 , $pages
 , $city: $publisher
 , <a target="_blank" href="$url">$urltxt<>/span</a&gt
 
</pre>
<ul>
<li>urltxt is per default “url” or “pdf”, “ps”, “zip” if this is the extension of the file referenced by the url</li>
</ul>
By adding some lines in your style sheets, you can format the output according to your needs. One example:
<pre>
.wpmref {
}

.wpmauthors {
color: #666666;
}
.wpmyear:after{
content: ": ";
}
.wpmyear {
color: #666666;
}
.wpmtitle:before{
content: "\"";
}
.wpmtitle:after{
content: "\"";
}

.wpmurlpdf:before {
content: url("/image/pdf.gif");
}

.wpmoutlet,
.wpmvolume,
.wpmissue,
.wpmpages {
font-style: italic;
color: #336633;
}
</pre>
Additionally, there are widgets to display the content of collections or shared collections in widget areas of a theme (list of titles with links only). 
The output in the widgets is formatted the following way:
<pre>
 <ul class="wpmlist">
 <li class="wpmlistref">
 title (if url is defined, then this title is linked to url)
 </li>
 ...
 </ul>
</pre>
The title will additionally be equipped with a div-tag including the 
full reference in the title attribute – which will in most browsers 
display the full reference when you are hoovering over the title with 
the mouse pointer.
You can use the plugin in non widgetized themes, just try
<pre>
echo $mendeleyPlugin->formatWidget("groups", 763, 10, array ('author' => 'Michael Koch'));
</pre>
For using the plugin you have to obtain an API key from Mendeley, 
enter this Customer Key in the configuration section of the plugin, 
and authorize the API. To do so the following steps have to be taken:
<ol>
<li> install plugin
</li>
<li> activate plugin
</li>
<li> get Customer Key and Customer Secret from http://dev.mendeley.com/
</li>
<li> enter the information in the wp-mendeley tab in the backend
</li>
<li> press “Get Access Key” on the wp-mendeley configuration page
</li>
<li> then you are redirected to the Mendeley web site to authorize the request, and redirected back to the blog (see Known Problems when this step does not work)
</li>
<li> now you can use shortcodes in your pages and blogs
</li>
</ol>
<h3>Details presentation</h3>
The document lists in the widgets only include the title of the 
document and a link. Per default the link is either the url attribute 
of the document – or if not set a link to the doi attribute in the 
document if set.
To present more details for those list entries without leaving the web 
site beginning in Version 0.8.1 you have two options:
1) if enabled in the configuration, the list items will include 
mouseover tooltips showing the full reference – this can be 
constructed in a simple default way or using CSL stylesheets.
2) if a details url is set in the configuration, all list items are linked to 
 $DETAILSURL?docid=XXXX 
You can create a details page on your WordPress installation in the following way: 
– create a page 
– insert the [mendeleydetails]…[/mendeleydetails] shortcode in the page 
– the text between the shortcodes is interpreted the following way: 
 every tag “{attributename}” is replaced by the corresponding attribute in the 
 Mendeley document 
– if you only use the simple shortcode [mendeleydetails] then the plugin 
 looks for the file “mendeley-details-template.tpl” in the plugin directory 
 and interprets the content of this file in the same way
In addition to all attributes returned from Mendeley (abstract, 
authors, doi, editors, translators, categories, identifiers, issue, 
keywords, mendeley_url, pages, producers, publication_outlet, 
published_in, tags, title, type, url, uuid, volume, year – also see 
the Mendeley API documentation at 
http://dev.mendeley.com/methods/#core-document-attributes) you 
can use the special attribute “full_reference” to insert a full 
reference. The attribute can be annotated with a CSL url to do the 
formatting according to a CSL stylesheet: 
{full_reference,http://site/url.csl}
When caching PDF files is enabled, you additionally can use “filelink” 
which will produce the word PDF with a link to the PDF file – and the 
special attribute “coverimage” which will produce an image tag with a 
link to an image of the first page of the PDF. To switch off generating 
file links for single documents (e.g. because of copyright issues), 
you can add the tag “nofilelink” to the tags of the document in 
Mendeley.
<h3>JSON data source</h3>
In version 0.7 we added the functionality to create a JSON data source 
– e.g. to be used as data source in Exhibit/Simile application.
For example the page http://www.kooperationssysteme.de/pub/cscm/ uses 
such a data source in an interactive JavaScript application to search 
the references.
The following line is used in the Exhibit/Simile application:

In the directory “examples” you find a file bibexhibit.tpl.php that can 
be placed in your WordPress theme directory. Then you can create a new 
page with the Template BibExhibit that will show the application with 
the data source. Do not forget to edit the file – specify the id of the 
Mendeley group you want to access in the link-line.
<h3>CSL integration</h3>
When you specify a CSL (citation style language) stylesheet via the csl parameter, 
the formatting specified in the stylesheet is used to generate details.
A .csl file must be a XML formatted file, containing the style tags 
defined by the citation Style language. For further information of 
CSL you should visit the citationstyles.org website. If you want to 
use an existing CSL style, you should browse the zotero style 
repository on zotero.org/styles. For creating your own CSL file, you 
can either write an XML-file or use a visual editor 
e.g. editor.citationstyles.org/visualEditor/.
We include some CSL files in the sub directory “style” – So, an easy 
way to try the functionality could be to link to one of those files – 
e.g. by an URL like the following: 
http://YOURDOMAIN/wp-content/plugins/mendeleyplugin/style/apa.csl
For formatting entries via CLS, we are relying on the CiteProc.php 
formatting engine by Ron Jerome, which usually is included in the 
plugins distribution. (See https://bitbucket.org/rjerome/citeproc-php 
for the original project.)
The library includes locale-files for adapting the output to different 
languages. We have only included the DE and EN locales here. Please 
load additional locales from 
https://bitbucket.org/rjerome/citeproc-php/src/ and add them in the 
locale folder in the plugin folder.
<h3>Source Code Documentation</h3>
The source code of the plugin is more or less documented. Here some 
information about the overall structure:
The main function of the plugin is “formatCollection”. This function 
is called from different places in order to create a formatted list of 
references. In this function
<ul>
<li>first the output cache ist checked (getOutputFromCache) – in this cache completely formatted outputs for queries are stored
</li>
<li>then the list of documents is retrieved from Mendeley – depending on the type of collection (group or folder) – either by getDocumentListForFolder() oder getDocumentsForGroup()
</li>
<li>and then the documents are sorted and grouped according to the request (groupDocs)
</li>
<li>finally (in the loop producing the output) filter parameters are checked (checkFilter)
</li>
<li>the output for single references is produced using the functions formatDocumentShort() and formatDocument()
</li>
</ul>
The following Mendeley API calls are used
<ul>
<li>retrieving document list from a group: /documents?group_id=GROUPID
</li>
<li>retrieving document list from a folder: /folders/FOLDERID/documents; Iterate /documents/DOCID
</li>
</ul>
<h3>Thanks …</h3>
Thanks for various contributions to Rhodri Cusack, Constantin Orasan and Matthias Budde.
Thanks for contributing to the CSL integration in V0.8 to Philipp Plagemann, Claudia Armbruster and Martin Wandtke. 
Thanks for contributing to the details display in V0.8.1 to Björn Trappe.

Mendeley Plugin

Mendeley Plugin for WordPress is a plugin for displaying information from the Mendeley "shared bibliography system" in WordPress blogs.

Footnotes Made Easy vs Mendeley Plugin