A.N.R.GHG Publishing Toolkit Icon

A.N.R.GHG Publishing Toolkit

By ANRGHG

Download

Active Installs

10+

Last Updated

January 21, 2026

First Released

June 3, 2021

Download History (Last one month)


Contributors

anrghg anrghg
martinneumannat martinneumannat
milindmore22 milindmore22
misfist misfist
vyskoczilova vyskoczilova
westonruter westonruter

An AMP compatible toolbox to help complete WordPress. Core features include:

  • Security by locking the login dialog
  • HTML partial including
  • Thank You and other messages
  • Date information: published, updated, first published, meta tags
  • Paragraph links and list item links
  • Heading links
  • Table of contents
  • Notes and sources in two lists
  • Reference lists, bibliographies
  • Webfont loading
  • Templates for messages, notes, sources, references
  • Exporting and importing settings, templates and custom options
  • Backing up the settings and templates
  • Customize anchors and slugs programmatically

Notice about Language support: While American English is supported natively, British English support is at 100% (generated). French and Spanish with all sublocales supported by WordPress benefit from internal translation, currently at 18% and 6% respectively. About one in four string instances are in sync with WordPress Core.

The A.N.R.GHG Publishing Toolkit can load and filter HTML partials from the file system, and it addresses the challenge to do by HTML and CSS things that used to be done by JavaScript, which was one reason the internet loaded slowly on mobiles and consumed more resources than with AMP technology. So far, the A.N.R.GHG Publishing Toolkit is not yet up to its full design goal, but it already can:

Security

  • Protect WordPress websites against password leak effectiveness, by hampering the login process depending on the value of a constant defined in a mini-plugin (editable on the hosting platform);
  • Make that constant configurable so that in multisite networks, individual sites may be toggled independently;
  • Extend authentication cookie lifespans to a configurable period of time, for example until the day after the next scheduled login rush;
  • Display the login activation status with an icon in the Admin bar;
  • Blank the login dialog out if it is convenient to access the WordPress Admin area through the hosting platform exclusively.
  • CAUTION: Unless the hosting provider has set up VPS level security, shared hosting is prone to being hacked by web shell even if only a single one of the websites sharing the same server’s home directory is compromised. Therefore, the A.N.R.GHG Publishing Toolkit’s security feature is efficient only on websites hosted on a dedicated server, a Virtual Private Server (VPS), or shared hosting with VPS level security set up by the hosting provider.

HTML partials

  • Include locally stored HTML partials directly from the file system;
  • Replace optional placeholders with CSS classes and a configurable value;
  • Enable updating the partials in bulk by FTP, rather than individual Custom HTML blocks or reusable blocks;
  • Solve the issue of size, since posts containing too much code cannot be saved.

Thank You message

  • Display a configurable message after posts and/or pages;
  • Help with activating and configuring the message on a per-page basis in the Post Meta box;
  • Make available a set of rich text messages configured in the Template editor;
  • Provide a block to configure an unlimited number of messages right in the post or page.

Date information

  • Display the last modified date at post/page start or end;
  • Display the published date at the start or end of pages where WordPress does not display it natively;
  • Optionally add a freely configurable field about where the post was first published;
  • Add date meta tags (may be useful if not already added by an SEO plugin).

Paragraph links

  • Add a fragment identifier in a configurable link prepended to every paragraph and list item;
  • Use position independent identifiers derived from the content;
  • Use the custom ‘HTML anchor’ for all paragraphs that it has been configured for, further improving identifier stability;
  • Keep the identifiers fully localized also when using a non-Latin script, for legible display in the URL bar.

Heading links

  • Add localized and optionally stable fragment identifiers and hyperlinks to headings.

Table of contents

  • Number the headings by CSS in appended or prepended position with a backlink to the table of contents;
  • Replace the appended number with a generic arrow if numbers are not desired next to headings;
  • List the headings in a table of contents, that the heading numbers link back to;
  • Optionally collapse and expand the table of contents from the label, also when JavaScript is off;
  • Insert a table of contents automatically in all posts with a configurable minimum number of headings;
  • Deactivate the table of contents for a particular post or page in the added Meta box;
  • Add a table of contents if the Table of contents block is present;
  • Use a configurable string as an alternative positioner in the Classic Editor to override the configured default position;
  • Configure its label for all posts in the settings, and for a particular post in the Post Meta box or in the block, or by adding an argument in the code;

Notes and sources

  • Parse inline notes and sources and display them either as descriptive endnotes or as bibliographic endnotes depending on their delimiters;
  • Process sources nested in notes;
  • Show notes and sources in responsive, adaptative and configurable rich tooltips when hovering their inline anchor;
  • Support six numbering systems including Eastern Arabic digits to help distinguish notes from sources;
  • Register notes and sources on the fly for reuse across a post or page;
  • Store notes and sources as templates for reuse across the website;
  • Display additional text around reused notes and sources;
  • Handle multiple notes and/or sources reused in a single instance;
  • Parse the notes and sources delimiters as freely configured also using non-Latin script or punctuation only;
  • Support switching complement delimiters midway, parsing older posts for the previous ones while the current ones are processed in posts from a configurable ID on;
  • Save the current delimiters with each post, so that delimiters may be reconfigured at any time and are valid in new posts;
  • Parse post-specific sets of delimiters configured in the Post Meta box;
  • Display complements in a number of columns (up to three) configurable for notes and sources separately, and responsively with respect to mobiles;
  • List complements section-wise at each instance of the block in the Block Editor, or alternatively, of a configurable positioner code in the Classic Editor;
  • Defer complement lists to the footer of a particular post, or do so for all posts unless specified otherwise;
  • Post-process the web page to move complement lists from the built-in WordPress default position below the footer to within the footer;
  • Specify the writing direction in complement lists and anchor tooltips for notes and for sources separately on a per-post basis in the added Post Meta box, or per instance in the block (Block Editor) or the positioner code (Classic Editor);
  • Display a complement in a new tab or window using its URL even when lists are collapsed by default;
  • Keep complement lists collapsed except for the target item after clicking an anchor, so as to not distract from the other features and information;
  • Optionally expand the full list on clicking any anchor as it is useful for ibid notation;
  • Combine identical complements to a single item, and enumerate the related anchors in a tooltip shown on hovering its number in the list;
  • Display a warning if an opening delimiter is unbalanced, quoting the context for easy location.

Reference lists

  • Display lists of references in the post or page;
  • Optionally make them collapsible, and display them collapsed or expanded at page load;
  • Help with configuring reference lists in the ‘Reference list’ block with settings for label, display and writing direction.

Web fonts

  • Load web fonts with preconnect after pasting their URL into a text area in the settings;
  • The Google Web Fonts repository is linked from the Settings page;
  • One example URL is provided out of the box, but the switch is off by default.

Templates

  • Help with editing and storing templates that can be used as messages, as notes and as sources, and in reference lists;
  • Bulk-edit saved templates on the fly in the templates list.

Export/import

  • Export and import templates and settings;
  • Export and import freely defined options (this comes in handy when using plugins not providing export and import features);
  • Restore any state using a datestamped file from the backup feature, and prevent accidental data loss.

Backup

  • Automatically back up templates and settings both at accessing and saving these pages;
  • Restore any state using the import feature, and prevent accidental data loss.

Anchors and slugs

  • Help with configuring the rules used to generate fragment identifiers, and optionally page slugs;
  • Allow for uppercase, custom conversions, configurable maximum length.
  • Support custom conversions;
  • Make the maximum length configurable.

Excerpts

  • Mitigate the effect of not using shortcodes, but versatile and internationalized delimiters instead.

Interoperability

  • Integrate with Elementor;
  • Integrate with Advanced Custom Fields.

Character conversions

  • Optionally deactivate WordPress default behavior based on WPTexturize, so that ASCII quotation marks stay as-is also outside code areas.

Category pages and taxonomies

  • Activate rich-text term descriptions.

Scrolling

  • Use a configurable scroll offset and optional CSS smooth scrolling.

CSS

  • Add the post or page slug as a class to the body element to ease customizing the aspect of specific pages.

HTML

  • Clean up errand meta tags and remove stray meta elements on public pages.

User interface

  • Provide 4 Gutenberg blocks to help with configuring messages, reference lists, note and source lists, and the table of contents;
  • Add a configurable Post Meta box for a more fine-grained configuration of various features;
  • Display settings in a single, fully searchable page with three levels of verbosity;
  • Add optional Admin submenu or menu items;
  • Provide an internal header menu.

Planned features

  • A format converter for Markdown ➔ WordPress;
  • A converter for .docx files;
  • An accessible emoji feature.

Concept

The A.N.R.GHG Publishing Toolkit aims to be one more Swiss Army knife to help complete any WordPress installation while reducing greenhouse gas emissions in multiple ways:

  • Thanks to AMP compatibility for a faster, less resource consuming web;
  • With streamlined processes at its end in a slim code base without external style sheets;
  • Through its commitment to web hosting with renewable energy ever since the first months;
  • By developing in a local WordPress stack on a laptop powered with 100% renewable energy from the local grid operator;
  • Being developed by a vegetalian, because going vegan is the single biggest way to reduce our impact on planet Earth, per Oxford University research and helps terminate animal torture.

Beyond being fully AMP compatible, the A.N.R.GHG Publishing Toolkit’s features for the public pages stay functional where JavaScript is turned off, with one limitation: Expanding the table of contents from a heading backlink requires one click more.

Security

Unless the hosting provider has set up VPS level security, shared hosting is prone to being hacked by web shell even if only a single one of the websites sharing the same server’s home directory is compromised. Therefore, the A.N.R.GHG Publishing Toolkit’s security feature is efficient only on websites hosted on a dedicated server, a Virtual Private Server (VPS), or shared hosting with VPS level security set up by the hosting provider.

For an additional layer of security, it is recommended to deny access to the wp-config.php file, and to the debug.log file in case there is any. To achieve this, please add the code snippet provided for the purpose near the bottom of the template-wp-config.php file by copy-pasting it from this file in the anrghg/ plugin folder to the .htaccess file in the WordPress base directory.

Requirements

Prior to installing the A.N.R.GHG Publishing Toolkit, please make sure that the PHP memory limit is configured appropriately in the web hosting. The large settings page requires more than 32MB. A too low memory limit results in the failure of important processes: theme updates, plugin updates, editing large posts and pages, and generally in a lot of malfunctioning and buggy behavior in WordPress and other systems.

Safe is to set the PHP memory limit to 256M as a rule of thumb, but many hosting providers throttle it down to 128M. If your plan includes cPanel, more options such as 512M may be available in the “MultiPHP INI Editor” under “Software” in the “Tools” menu on the cPanel home page in your hosting account.

WordPress configuration

The memory limit defaults to 40 megabytes for a single site, 64 MB for a multisite, so it may be necessary to increase this limit, although the A.N.R.GHG Publishing Toolkit is not known for being particularly memory-intensive. Options include 64M, 128M, 192M, 256M, 368M and 512M as the value should match the memory limit set in the website’s hosting. The file template-wp-config.php includes a template for this.

Install process

  • A. Standard process in the WordPress Admin area
  1. In the Admin menu, navigate to Plugins > Add New;
  2. In the search bar, type ‘anrghg’;
  3. In the search results, spot the ‘A.N.R.GHG Publishing Toolkit’;
  4. Click the ‘Install Now’ button next to it;
  5. Eventually click the ‘Activate’ button showing after installation complete.
  • B. Mixed process in the WordPress Admin area
  1. Download ‘A.N.R.GHG Publishing Toolkit’ as a .zip file from the WordPress Plugin Directory;
  2. In the Admin menu, navigate to Plugins > Add New;
  3. Click the ‘Upload Plugin’ button next to the page heading;
  4. Click the ‘Choose File’ button;
  5. Choose the downloaded .zip file;
  6. Click the ‘Install Now’ button;
  7. Eventually click the ‘Activate Plugin’ button.
  • C. By uploading via FTP
  1. Download ‘A.N.R.GHG Publishing Toolkit’ as a .zip file from the WordPress Plugin Directory;
  2. Uncompress the downloaded .zip file;
  3. Switch to an FTP client;
  4. Access the plugins directory;
  5. Make sure the same plugin is not already there, else delete the old one;
  6. Upload the folder anrghg/ resulting from step 2;
  7. Refresh the Plugins list;
  8. Eventually click the ‘Activate’ action link of the ‘A.N.R.GHG Publishing Toolkit’.

Plugin configuration

To activate the security feature, a constant needs to be defined in a mini-plugin. The code is already in the mini-plugin template template-mini-plugin.php. Please make sure this constant is always set to false unless somebody needs to log in. In that case, the constant needs to be set to true. But do not forget to set it back to false as soon as everybody is logged in.

Once the A.N.R.GHG Publishing Toolkit is installed, it needs to be configured:

  1. Most features are deactivated by default and may be activated individually. To access the settings page, please click the Settings action link of the ‘A.N.R.GHG Publishing Toolkit’ entry in the Plugins list. No menu items and no Post Meta box are added by default. To activate any of these, or the ‘Thank You messages’ or ‘Reference lists’ block, please choose the desired UI elements in the ‘User interface’ section of the Settings page.
  2. Even if the setting to turn a feature on uses the glide-switch design with ON and OFF button symbolic, please be still sure to save the form clicking the Save Changes button at the bottom of the window. Unlike the behavior specified in Android Material Design and SAP Fiori Design, changes require saving the form to become effective.
  3. Several headings or labels may need to be configured to your locale. That may be done on the Settings page, or in the ‘String translation’ pane of a multilingual plugin after saving the Settings page at least once to the database, or using configuration filters as provided in the file template-filter-config.php.
  4. The strings delimiting notes and sources are freely configurable and come also with two presets as suggestions. So do the inner delimiters. Codes needed to materialize positions are configurable too. Most of these configurations are versatile in that the plugin adapts to changes on the fly or mid-way.
  5. In the optionally added Post Meta box, every single section can be deactivated individually. After activating the Meta box, it displays with all elements by default just to make selection easier. Please be sure to switch elements in and out individually as desired in the settings page under ‘User interface’.
  6. Many features may be configured alternatively in a mini-plugin, easy to set up on the basis of the included template template-mini-plugin.php, or especially for theme-specific values, in your child theme’s functions.php, using configuration filters as documented in the file template-filter-config.php. That may be useful to help with adapting the configuration to theme-specific requirements while using multiple themes like in AMP Reader mode.
  7. Configuration filters are currently the only means to configure some features, notably the previous complement delimiters, used in posts and pages with an ID that is less than a configurable number. These filters are documented in template-filter-config.php under ‘Previous delimiters’ and ‘Previous delimiters for tooltips’.
  8. When using a translation manager with a String Translation pane, please be sure to save the Settings page at least once to your database, because translation filters require retrieving the strings in the database.
  9. Adding more hooks is projected for the purpose of filtering the HTML output. Overriding the theme style rules by Custom CSS however is not supported, since in multisite networks, Custom CSS is prohibited by default. See more hints in the A.N.R.GHG Publishing Toolkit settings page Customization section.

Register templates post-wide

To reuse a complement already used in the same post, it may be given a name in the first instance like so: [note]a_name[/name]The complement.[/note]. In case of conflicts, post-wide names prevail over site-wide names.

The name start delimiter ([name]) is not used for new complements. Its sole purpose is to delimit names in arbitrary positions.

Register templates site-wide

Complements become reusable site-wide when registered with the ‘Template editor’.

The name of a template may be any Unicode string; the only constraint is to not contain ordinary space.

In the list, existing complements are displayed full height with formatting, and HTML markup may be added directly too if JavaScript is on. If JavaScript is turned off, the source code is displayed, and new complements need to be written in source code as well.

Changes to existing complements can be made directly by editing the list.

Alternatively, a complement may be moved into the editor by clicking the ‘Move into editor’ button next to it, but before doing so, please make sure that TinyMCE is in Visual mode (both methods to set the mode programmatically fail and the one to get/check the mode is missing), as else the editor.setContent() method fails, the content disappears, and the page will need to be refreshed to get the item back instantly.

The ‘Move into editor’ buttons are deactivated for safety when either TinyMCE or the new name text box is not empty.

To help with choosing unique names, the names already in use are displayed in alphabetical order below the new name text box. The data is validated server-side, and if a problem is detected with missing, duplicate or invalid names, a warning will display and the cursor will be set to fix it.

All templates are backed up in a time-stamped file on accessing the list and on saving the form, if this feature is not deactivated in the settings. The backups are located in a subfolder named anrghg/ in the uploads/ folder in your wp-content/ directory.

Reuse complements

Simple syntax: To reuse an already registered complement, put its name as the first, last, or only word in a note or source.

To add more text like a page number, use a space as a separator between the complement name and the added text, like so, where ␣ stands for an ordinary space:

Before (the prepended space is kept): [src]According to the explanation set out on page 10 of␣name1[/src]

After (the appended space is skipped): [src]name1␣, page 10.[/src] or [src]name1␣␣explains it on page 10.[/src] (To have the source followed by a space, two spaces need to be typed.)

Full syntax: Beyond this simple syntax, the full syntax brings the opportunity to add more text on both sides, and to reuse multiple complements in a single instance.

Example: [note]See [name]reusable_one[/name], page 31, and [name]reuse2[/name], chapter 4.[/note]

What does A.N.R.GHG stand for?

A.N.R.GHG is the initialism of ‘Act now, reduce greenhouse gasses’.

The dots have been added to help screenreaders spell it as an initialism rather than as an acronym.

The climate crisis requires us to enroll all aspects of our work and lives so that our efforts converge towards addressing the crisis now as a top priority urgency.

The AMP technology contributes to streamlining processes and making the internet less energy-consuming.

Moreover, development and maintenance are powered with renewable energy as well since the developer subscribed to the green electricity option offered by the local grid operator to individual households at a monthly fee of about $2.

Most importantly, the developer is a vegetalian, as avoiding meat and dairy, eggs and fish helps making an end of animal torture and is the scientifically recommended single biggest way to reduce our impact on planet Earth, an Oxford University study assessed.

Why are multiple features crammed into a single plugin?

A number of features like heading links and table of contents, notes and sources or last modified date and published date of pages are interrelated, and solutions using one plugin per feature are suboptimal because of inconsistent identifiers or presentation.

Beyond consistency, among the reasons that further fueled the adoption of an “all”-in-one concept are efficiency and economies of scale, much like what Jetpack is achieving at an incomparable magnitude.

As a result, making individual plugins out of some of the features is not required and would be inefficient. Keeping them all together seems like the best option.

Why are all settings crammed together on a single page?

This way, the settings can be searched using the browser search functionality (Control + F), and all occurrences can be accessed directly. That would not be the case if the settings were grouped by topic under a number of tabs.

The table of contents at the top of the settings page replaces the tab row or column, while allowing for longer, more explicit labels. It can be accessed by clicking the ‘Back to top’ button at the top of the window in a fixed position.

Likewise, the ‘Save settings’ button is constantly visible at the bottom of the window. Clicking it does not require scrolling down to the bottom of the page.

Why do processes fail when this plugin is active?

This issue depends on the PHP memory limit. The large settings page requires more than 32MB. Safe is to set the PHP memory limit to 256M as a rule of thumb, but many hosting providers throttle it down to 128M. If your plan includes cPanel, more options such as 512M may be available in the “MultiPHP INI Editor” under “Software” in the “Tools” menu on the cPanel home page in your hosting account.

The limitations involved by a low memory limit affect plugin updates, theme updates, as well as other actions performed by WordPress and its plugins, for example editing large posts in the Block Editor. Other content management systems are likewise impacted by low memory limits such as 32M, that may be the default settings value in shared hosting.

How about using jQuery?

As the jQuery JavaScript library is not fully AMP compatible, features like tooltips, expand/collapse and scrolling back and forth do not use jQuery. Another reason is that when using jQuery, and JavaScript is turned off in a browser, these features are broken in that browser. Yet another reason is bad user experience as links to end notes are either unavailable, or available hard links cannot be opened while the relevant list is collapsed. Moreover, using jQuery prevents from saving a fully functional copy of a page. These frustrating issues outweigh the benefits of using jQuery.

Regardless, for end notes there is another plugin out there that uses jQuery by default and offers the ability to opt out: The Footnotes plugin, although closed since 2022-11-14, was consistently recommended in 2023, and it is compatible with the Twenty Twenty-Three theme. It can be installed as a .zip file following process B after downloading its latest version directly from the WordPress Plugin Directory, as it is one or two times a day on average per current stats, or from the latest backup of its full Plugin Directory page in the Web Archive.

However, since the Footnotes plugin is unmaintained, it may basically become a target of exploiting security vulnerabilities. That is why reading the abandonment statement made by its last developer, or its archived version, is strongly recommended.

Can I use various themes alongside?

Yes, using configuration filters, that have precedence over settings values from the database, each theme can have specific settings values stored in its child theme’s functions.php, so that sensitive values may be fine-tuned in accordance with particular layout options, while values that are constant across themes may still be configured in the settings page and called from the database.

The A.N.R.GHG Publishing Toolkit includes a template file called template-filter-config.php documenting all filters available so far (while process filters are being added as documented in template-filter-output.php).

How to keep configuration filters when switching themes?

As a stable place to add configuration filters and process filters, a mini plugin is convenient. A mini plugin template is included in the plugin folder. To use it, please move it out of the folder, eventually rename it, optionally place it in a new folder, then make it a plugin by deleting the seven percent signs standing out in front of the %%%%%%%Plugin Name: field label, and activate it after refreshing the Plugins list.

Why are the strings not in the translation pane?

For multilingual plugins to show the strings in the translation pane and to work effectively, the translation keys must be present in the database. To achieve this, please access the plugin’s settings page and click the ‘Save Settings’ button at the bottom of the window.

After this, all translatable configuration values will show up in the translation pane, even those that are not yet configurable on the settings page.

Are rich-text category pages supported?

Yes, category pages are supported through the term_description hook, so that all features are fully functional as configured.

When using the A.N.R.GHG Publishing Toolkit, category pages are unaffected by the filter that would usually delete HTML markup, and may be drafted like pages in the Block Editor, kept as drafts, and copy-pasted from the Code Editor to the term description window. Eventual leftover block markup is removed at runtime.

Are custom post types supported?

Yes, the A.N.R.GHG Publishing Toolkit supports all post types applying the filters hooked on the the_content hook; for example, custom post types of WooCommerce like product pages are supported through this hook. Additionally it supports popups from Popup Maker (Code Atlantic) by hooking on pum_popup_content, and from Popup Builder (Sygnoos) by hooking on sgpbSubscriptionForm.

Beyond, it processes a configurable list of additional hooks. The only requirement for a content type is to apply filters on the content, using whatever hook. The name of that hook needs to be filled in an input field on the settings page, or in the configuration filter found among the templates under “Support alternative content hooks.” Multiple hook names are comma-separated.

For convenience, a dedicated hook is also available, that the A.N.R.GHG Publishing Toolkit adds filters to for subsequent application to a given content by calling the WordPress apply_filters() function:

$content = apply_filters( 'anrghg_content_filter_hook', $content );

Are custom fields supported?

Wysiwyg fields added using Advanced Custom Fields are optionally processed for inline complements and other features as well, and complement lists are appended at the bottom of each field. That can be deactivated so that these fields would be processed as part of the post content if displayed accordingly.

Alternatively, when the hook that the field applies filters to is known, its name may be added to the content hooks in the settings.

The A.N.R.GHG Publishing Toolkit also adds numerous fields, among which the ‘first published date’ that will be displayed if its prefill has been changed in the Post Meta box.

Can I use shortcodes instead of blocks?

Yes, sort of. The A.N.R.GHG Publishing Toolkit does not rely on the WordPress Shortcodes API, because Shortcodes cannot be used to reliably process notes and sources. For example, the scheme is disabled in forms set up using the WPForms plugin. Also, available options are too restricted and may exclude your preferred ones; so, not being internationalized, the shortcode API fails on Non-Latin shortcodes; and not being versatile, it cannot process delimiters made of brackets, braces, parentheses or other punctuation characters only.

Additionally, registered shortcodes are removed from other usages such as schema and meta descriptions for SEO. That is appropriate for most shortcodes, but may not be desirable for sources: Stripping off these complements may convey a misconception of the content as containing unsourced statements, and thus harm the website’s reputation.

On the other hand, the A.N.R.GHG Publishing Toolkit is fully compatible with the Classic Editor relying on shortcodes: Instead of using the blocks, fully configurable strings like [anrghg_toc] and [/anrghg_section] may be manually inserted, both with optional arguments.

Can the appended message be edited in rich text?

Yes, by configuring it in the Template editor. Then insert its name in the input field on the settings page or as a return value in the configuration filter.

Can I use the post title in the appended message?

Yes, to insert the title of the current post or page, please insert the placeholder %s in the template text.

Why does the link to a code block not show up on hovering the code?

As the code block is scrollable, its overflow is hidden, so any protruding elements like the paragraph link are cut off. To work around the issue, code blocks are wrapped into a paragraph, but this paragraph becomes two paragraphs due to the block level code block, and the first paragraph stops before the code. That is why the link shows up only when hovering the area in the margin before the start of the code.

Does adding a paragraph break links to other paragraphs?

In most cases not, because the identifiers that the A.N.R.GHG Publishing Toolkit assigns are content-based, both for Latin and for non-Latin scripts. These are URL-encoded, much like WordPress derives slugs from titles.

The main case where numbering is added is to disambiguate identical headings.

As paragraphs are unlikely to have identical beginnings spanning over more than 200 characters—the length that fragment identifiers are shortened to before cleaning up truncated last words—, every paragraph has a unique stable identifier, unless the underlying text is modified, resulting in the need to fix the fragment identifier.

HTML anchors set in the WordPress block inspector’s “Advanced” section have precedence over content-derived anchors. Like these, they are prepended with the post number. The part after this and the separator may be copy-pasted into that field to make an existing paragraph link insensitive to further edits, provided that the resulting discrepancy is not an issue.

How to edit headings or paragraph starts without breaking links?

By giving them an “HTML anchor” in the Block Inspector. For each heading, paragraph or list item, the A.N.R.GHG Publishing Toolkit uses its existing “HTML anchor” in the first place. Only if none is configured, it proceeds to derive a fragment identifier from the content.

If a URL with a content-based fragment ID is in use prior to editing the underlying content, then the existing ID may be grabbed in preview mode and copy-pasted into the “HTML anchor” input field without the prepended post ID, as this number is always prepended automatically to any ID.

Prepending the post number helps ensure that each ID is unique across the website, in support of the infinite scroll (AJAX autoload) feature.

How to position the table of contents without the block?

That is done by typing [anrghg_toc] or any bracketed string that this code is configured to.

Arguments between the code name and the closing bracket are also supported, and both names and values are designed for ease of input. Argument names are preceded by a space and start with an underscore. Values are delimited by vertical bars. The equals sign may or may not be space-padded:

  • Label tailored to the instance: _1=|Contents of ‘%s’|, where %s is replaced with the post title (for tables after the post);
  • Alignment: _2=|0| or _2=|center|, or _2=|-1| or |left|, or _2=|1| or |right|;
  • Collapsing behavior:_3=|-1|for expanded (and collapsible), or_3=|1|for collapsed (and expandable), or_3=|0|` for uncollapsible.
Why are level 1 headings supported?

Stray level 1 headings do indeed have a negative impact on search engine rankings. Using H1 outside the post title is strongly discouraged. Also the heading formatting defaults to H2 in the Block Editor, while in the Classic Editor the shortcut Shift + Alt + 1 is deactivated. We are warned.

Yet multiple level 1 headings are in current use outside the web, so the support for H1 is consistent with standard word processing user experience. And when the .docx or .odt formats are converted to WordPress, headings are usually not downgraded (despite they should be), to prevent H6 from being degraded to paragraph level, since custom H7 markup is not well supported by the web.

The A.N.R.GHG Publishing Toolkit supports level 1 headings if they are present in an article body, because H1 formatting is available in WordPress, that inherits it from TinyMCE where it makes actual sense, as TinyMCE is also used in systems that may not feature an extra field for the page title.

Do the added fragment IDs interfere with my custom anchors?

No, because the “HTML anchor” configured in the Block Inspector is added right inside the element’s start tag, while the A.N.R.GHG Publishing Toolkit adds its IDs in an extra span.

Can I have heading anchors also in a linked PDF?

Yes if they are built-in; but these fragment identifiers are like scroll instructions. More universally, using URL parameters, scroll instructions may apply to any PDF opened in a browser:

To scroll to the page, add a hash to the PDF’s file name in the URL, then page= and the page number:

domain.tld/folder/your-file.pdf#page=123

To scroll to a heading in the page, append an ampersand, then zoom= and three comma-separated numbers: first the zoom factor in per cent (a zero is interpreted as 100%), next the X offset in pixels, then the Y offset. Basically you only need the third number, a best-guess determined by trial-and-error or measuring pixels so that the target heading displays a little below the upper viewport edge:

domain.tld/folder/your-file.pdf#page=123&zoom=0,0,700

How is the table of contents expanded?

The A.N.R.GHG Publishing Toolkit’s table of contents features a CSS-only transition when expanding or collapsing.

For AMP compatibility, JavaScript is avoided on public pages when the same behavior is not implementable in the AMP framework.

What is the lone heading after the table of contents label?

That happens after clicking a heading number while JavaScript is turned off, because expanding the table of contents from heading numbers relies on JavaScript (either in AMP or Vanilla); else, the scrolling wouldn’t work. So, without JavaScript, the target list item displays alone thanks to CSS, and the table of contents waits for its label or twistie being clicked to expand by CSS.

There is a small likelihood for the same to happen while JavaScript is on. On AMP pages, the related style rule is always valid, but after clicking a heading number (which is when it would come into play) it is overridden by another one, activated using the AMP framework. Reloading the page in that state would result in a lone heading as pointed in the question.

How are complement lists expanded?

The A.N.R.GHG Publishing Toolkit’s complement lists are expanding or collapsing by CSS only, with a slight transition.

For AMP compatibility, JavaScript is avoided on public pages when the same behavior is not implementable in the AMP framework.

Why are complements not soft-linked?

Compared to hard links, soft links have multiple downsides, while the disadvantage of using hard links is easily mitigated by hitting the backbutton instead of clicking backlinks. A configurable plain tooltip on hovering a backlink suggests this workaround, that will remove the anchor click from the browsing history.

Moreover, hard links allow accessing complements from outside, as they are the precondition of using the :target CSS selector to display the desired complement only, without expanding the whole list. That scheme always helps your visitors not be distracted from the other features and contents often displayed after or before the complement lists, notably the social icons and related posts. Your visitors may see these features as soon as looking up a complement in the list, as an alternative to checking it out in its tooltip.

Thanks to using hard links, no script is used, and since expanding and collapsing complement lists and tables of contents from their label is done without JavaScript likewise, the A.N.R.GHG Publishing Toolkit’s features are fully functional in browsers where JavaScript is turned off (and AMP actions won’t work either). Additionally, for convenience, CSS-based scroll offset as well as smooth scrolling are supported, too.

Are identical complements combined?

Yes, optionally identical notes or sources are combined into a single item with a single number. Thanks to using hard links, scrolling back up is performed by using the backbutton. For reference, all links to the instances where the complement is used are enumerated in a tooltip on hovering the complement number in the list.

Notes and sources are only combined section-wide. Identical complements occurring in several sections of a post or page appear once in every related list.

What are the numbering options for notes and sources?

Beside the standard Western Arabic digits, notes and sources may be numbered using Eastern Arabic digits, or be numbered each in a distinctive manner among Roman and Latin numerals, both available in lowercase and uppercase.

Are long complements truncated for display in tooltips?

Never, because the tooltips are styled in a way that truncating is unnecessary. When exceeding a configurable number of characters, the tooltip displays full-width even on desktops, and if it would exceed a configurable maximum height, it becomes scrollable.

That said, the A.N.R.GHG Publishing Toolkit supports a dedicated tooltip text, similar to WordPress’ manual excerpt feature. If the (configurable) [/view] delimiter is present in the complement, the text before is displayed as tooltip text, while the following text represents the complement in the list. This is linked to from the end of the tooltip, and from anywhere in the tooltip by delimiting the link text with [link] and [/link], or any delimiters these are configured to.

Can complements be nested?

Yes, provided that the nested ones are sources, and those they are nested in are notes. Notes cannot be nested in sources, nor notes in notes, nor sources in sources. Only this nesting scheme is supported, but each note may include any number of nested sources:

  • …[note]…[src]…[/src]…[/note]
Can I start using other delimiters from now on?

Yes, there is an option to configure the current delimiters separately along with the ID of the post where the new set of delimiters is used first. Currently this requires using configuration filters. Once that is done, new delimiters may be configured the usual way without affecting the older posts and pages.

Can I delimit sections for complements without using the block?

Yes, by ending the section with [anrghg_section] or any bracketed string that this code is configured to.

Arguments between the code name and the closing bracket are also supported, and both names and values are designed for ease of input. Argument names are preceded by a space and start with an underscore. Values are delimited by vertical bars. The equals sign may or may not be space-padded:

  • List labels tailored to the instance: _11=|Notes of ‘%s’| and _12=|Our sources|, where %s is replaced with the post title;
  • Writing direction tailored to the instance: _21=|-1| in Note list, _22=|-1| in Source list, or _20=|-1| in both lists, where -1 is right-to-left, and 1 is left-to-right;
  • Collapsing behavior tailored to the instance: _31=|-1| for the Note list, _32=|-1| for the Source list, or _30=|-1| for both lists, where-1is expanded (and collapsible),1is collapsed (and expandable), and0` is uncollapsible;
  • Footer deferral: _40=|1| or _40=|0| for whether this instance must be deferred to the footer, or must not be deferred.
Could multipage posts display all notes at the end?

Multipage posts are reported not to be properly indexed, and they are not properly navigatable either, with page numbers at the bottom only, and no distinctive head zone for the extra pages. Thus, ‘Page break’ is a bogus feature and should never be used.

Being able to read the whole content merely by scrolling is much more user friendly. Consistently, implementing anything specifically for multipage posts would be wasting the time of all involved parties, which is why WordPress did not properly implement its multipage feature in the first place.

How to reset the settings to default values?

The easiest way is to import an empty file.

Alternatively, deleting the ‘anrghg’ row in the ‘wp-options’ table in the database has the same outcome.

Why do setting descriptions not display in tooltips only?

Info hover buttons would cause issues for either accessibility or keyboard navigation.

Thanks to the ‘Save settings’ button being constantly visible at the bottom of the window, the settings are not spatially constrained. If full tab navigation is active, the ‘Save settings’ button is active after each settings section.

Although the settings page is mostly visited at setup while information is wanted, but less often later on, the settings page verbosity is configurable at three levels, one of which is with information expand buttons. Another option fully hides almost all explanatory information.

Why is the database so heavy?

That is mainly due to WordPress documenting by default the full version history of every post and page.

If this is too much information and ends up taking too much disk space, with backups getting bulky, and potentially restoring the database would be hard, then revisions may be deactivated by defining the constant WP_POST_REVISIONS as false.

Another option is to limit the number of stored revisions as in the example provided in the file template-wp-config.php.

Changelog

1.17.6 (2026-01-21)

  • Web fonts: Debug after the 1.17.2 Localization fix.
  • Slug body class: Debug after the 1.17.2 Localization fix.
  • Date meta tags: Debug after the 1.17.2 Localization fix.
  • Delay 3 more filters from plugins_loaded to init to make sure everything keeps working.

Note

Changelog display may be truncated to 5 000 characters. The full changelog is available as part of the latest readme.txt in the repository.

1.17.5.1 (2025-12-17)

3422244

  • Documentation: Fix changelog display in the Plugin Directory.

1.17.5 (2025-12-17)

3422214

  • Internationalization: Debug translations by restoring call to load_plugin_textdomain.
  • Internationalization: Remove ‘Table of contents’ from optional syncing with WP Core.
  • Settings: Assess direct filesystem calls as safe and necessary in this context.
  • Templates: Assess direct filesystem calls as safe and necessary in this context.
  • Documentation: Export/import: Elaborate on the support of custom options.
  • Documentation: Expand the Data section in the feature list to Templates..Backup.
  • Documentation: Move the Category pages and taxonomies section in the feature list.
  • Documentation: Update the feature short list.

1.17.4 (2025-12-11)

3416910

  • Paragraph links: Replace deprecated seems_utf8() with wp_is_valid_utf8().
  • Settings: Security: Debug and remove sanitization callback in register_setting().
  • Export/import: Security: Debug and remove sanitization callback in register_setting().
  • Templates: Security: Debug and remove sanitization callback in register_setting().
  • Conversion: Security: Debug and remove sanitization callback in register_setting().

1.17.3 (2025-12-09)

3414896

  • Settings: Security: Try adding sanitization when calling register_setting().
  • Export/import: Security: Try adding sanitization when calling register_setting().
  • Templates: Security: Try adding sanitization when calling register_setting().
  • Conversion: Security: Try adding sanitization when calling register_setting().
  • Settings: Prefix unprefixed global variable $g_a_registered.
  • Settings: Prefix unprefixed global $g_a_fast_tracked_defaults.
  • Settings: Prefix unprefixed key/value pairs in a global context.
  • Complements: Prefix unprefixed global $g_m_unbalanced_delim.
  • Interoperability: Prefix unprefixed global $g_b_elementor_test_markup.
  • Security: Prefix unprefixed global $g_s_login_control_constant.
  • Security: Prefix unprefixed global $g_i_login_deactivation_profile.
  • Metadata: Tags: Shorten the enumeration to 5 items.
  • Metadata: Short Description: Shorten to less than 150 characters.
  • Documentation: Improve filter template anrghg_the_content.

1.17.2.1 (2025-12-07)

3413713

  • WordPress Core: Assess compatibility with WP 6.9 (admin/blocks.php).
  • Documentation: Changelog: Add previously unmentioned package updates.
  • Documentation: Changelog: Add revision number linked to SVN changeset.
  • Documentation: Stable Tag: Add a ‘stability policy’ (in anrghg.php).
  • Documentation: Rename svn-revs.txt to SVN-log.txt for intuitivity.
  • Documentation: Copy ‘Stable Tag stability policy’ into SVN-log.txt.
  • Documentation: Rename the script copy from build.sh to build.txt.

1.17.2 (2025-11-03)

3389246

  • Localization: No longer call load_plugin_textdomain.
  • Localization: Delay translation loading from plugins_loaded to init.
  • Localization: Add anrghg_alternative_sanitize_title_active to wpml-config.xml.

1.17.1 (2025-10-30)

3387349

  • User experience: Scroll offset: Fix CSS bug introduced in v1.10.2.

1.17.0 (2025-10-14)

3378367

  • Paragraph links: Add palm branch “⸙”, flowers “✿”, “❀”, “❁”, ivy leaves/fleurons “❦”, “☙”, “❧” in select box.
  • Localization: IDs and slugs: Convert micro sign to small letter “u” as is usually done where “µ” is missing.

1.16.5.1 (2023-12-29)

3015571

  • WordPress Core: Update “Tested up to” value in readme.txt to 6.4.

1.16.5 (2023-11-06)

2990010

  • Configuration filters: Debug filter application.
  • Configuration filters: Clarify priority configuration.
  • Internal CSS: Fix priority configuration.
  • Priority configuration: Make WPAutoP fix optional.
  • Documentation: Changelog: Delete erroneous entry from the 1.16.4 changeset.
  • Documentation: Streamline feature descriptions.

1.16.4 (2023-10-30)

2986383, 2986384

  • Internal CSS: Move internal CSS from manually hard-coded style element to wp_add_inline_style().
  • Internal CSS: Add and enqueue an empty stylesheet for the purpose of getting the required handle.
  • Internal CSS: Merge stylesplit.php into styles.php thanks to an infrastructure improvement.

1.16.3.1 (2023-10-29)

2985620

  • Documentation: Add the “Include HTML partial” feature to the short list.
  • Documentation: Feature short list: Improve readability.

1.16.3 (2023-10-18)

2980627

  • Notes and sources: Lists: Correct number position in printed lists.

1.16.2 (2023-10-15)

2979096

  • Notes and sources: Lists: Fix display bug in collapsed state by removing row top margin since font size issue is fixed.
  • Table of contents: Fix font size issue in collapsed state.
  • Internationalization: Include partial: Block Inspector: Streamline informative texts.
  • Documentation: FAQ item about database size and post revisions.
  • Templates for wp-config.php: Suggest taking control of post revisions.

1.16.1 (2023-10-12)

2978355

  • Security: Add all ARIA attributes to the whitelist of the KSES filter.
  • Blocks: Fix comments in JSON configuration files.
  • Include partial: Block Inspector: Debug base directory display by overflow-wrap anywhere.
  • Include partial: Block: Turn autocomplete on for the file path too.

1.16.0 (2023-10-10)

2977231

  • Include partial: Security: Apply KSES filter to the included partials, with opt-out for top-level Admins.
  • Include partial: Add support for additional CSS classes, with new placeholder {{{anrghg-classes}}}.
  • Include partial: Change existing placeholder name from {{{anrghg-placeholder}}} to {{{anrghg-value}}}.
  • Include partial: Make both placeholder names configurable.
  • Include partial: Setting for the base directory to enable relative paths in the path input.

1.15.0 (2023-10-07)

2975930

  • Include partial: New block in the “embed” category to include locally stored HTML partials.
  • Notes and sources: Lists: Avoid widows and orphans instead of page breaks inside.

1.14.6 (2023-09-14)

2967097

  • Notes and sources: Prevent page breaks inside notes and sources in lists.

1.14.5 (2023-09-13)

2966760

  • Notes and sources: Debug font size of Note lists and Source lists.
  • Notes and sources: Remove gap between Note list label and Source list label in collapsed state.

1.14.4 (2023-09-09)

2964844

  • Notes and sources: Debug number layout in print.

1.14.3 (2023-09-09)

2964790

  • Notes and sources: Remove list heading underline.
  • Notes and sources: Debug printing.
  • Reference lists: Debug printing.

1.14.2 (2023-09-08)

2964638

  • Reference lists: URL-encode configurable strings used in fragment identifiers.
  • Table of contents: URL-encode configurable strings used in fragment identifiers.
  • Notes and sources: URL-encode configurable strings used in fragment identifiers.
  • Style rules: Correct identifier of the added internal CSS element.

1.14.1 (2023-09-07)

2964119

  • Slug body class: Escape sensitive characters in configurable strings.
  • Table of contents: Escape sensitive characters in configurable strings.
  • Reference lists: Escape sensitive characters in configurable strings.
  • Notes and sources: Escape sensitive characters in configurable strings.
  • Notes and sources: HTML parser: Debug inner HTML by admitting > characters.
  • Notes and sources: Lists: Priority: Set default to lowest for compatibility.
  • Notes and sources: Lists: Disambiguate source IDs in note tooltips to debug nested backlinks.
  • Notes and sources: Debug tooltip padding for right-to-left scripts.
  • Notes and sources: Debug tooltip padding for nested sources in note lists.
  • Notes and sources: Debug fullwidth tooltips of nested sources in note lists.
  • Notes and sources: Stray meta tags: Move to dedicated feature.
  • Stray meta tags: Complete removal algorithm.
  • Stray meta tags: Make removal from public pages the default behavior.
  • Settings: Priority: Add warning about block disappearance if higher than 9 (from 8 downwards) for Notes and sources.
  • Settings: Priority: Display warnings in the first place as must-read information i.e. always uncollapsible.
  • Settings: Priority: Turn radio button red for highest priority.
  • Settings: Priority: Show safe range in the first place before possible range.
  • Settings: Fix grammar issues in variable strings.
  • Style rules: Add identifier to the added internal CSS element.

1.14.0 (2023-08-21)

2956453

  • Accessibility: Settings: Section headings: To the top functionality when full tab navigation is active.
  • Accessibility: Settings: Save buttons: Correct tab navigation by moving buttons before.
  • Accessibility: Settings: Save buttons: Display info in section headings on focus.
  • Notes and sources: Tooltips: Debug display of scrollable tooltips.
  • Notes and sources: Backlinks: Prevent backlink link texts from line-wrapping.
  • Notes and sources: Output anchor tooltip style rules on the condition of tooltip activation.
  • Notes and sources: Output backlink tooltip style rules on the condition of identical complement combination.

1.13.0 (2023-08-15)

2953960

  • Accessibility: Settings: Replicate Save button at section headings when full tab navigation is active.

1.12.0 (2023-08-11)

2951898

  • Accessibility: Settings: More fluid tab navigation by skipping the section headings.
  • Accessibility: Settings: Backup: Fix tab navigation disturbance.
  • Accessibility: Settings: Optionally have all links and expand buttons tab navigable.
  • Settings: User interface: Option for full tab navigability.

1.11.0 (2023-08-08)

2949546

  • Notes and sources: Priority: Change default to highest.
  • Settings: Notes and sources: Priority: Move to top of Lists subsection.
  • Settings: Customization: Add link to the Theme Editor.
  • Settings: Customization: Advice for Custom CSS on multisite.
  • Reference lists: Block: Move help from input label to help text.
  • Accessibility: Settings: More fluid tab navigation by skipping all of the links.

1.10.2 (2023-07-01)

2932859

  • User experience: Scroll offset: Prevent WordPress from hiding the scroll padding.
  • Customization: URL slugs: Use fallback title if title is empty or false.

1.10.1 (2023-06-21)

2929413

  • Settings: Security: Modify the warning about shared hosting, after validation by a hosting company.
  • Documentation: Security: Modify the warning about shared hosting, after validation by a hosting company.

1.10.0 (2023-05-27)

2918017

  • Settings: Security: Add a warning in the Security section introduction.
  • Documentation: Security: Add a warning in the Security notice of the Installation section.
  • Documentation: Security: Add a warning in the Security feature description.
  • Documentation: Security: Add a warning in the “How about using jQuery?” FAQ item.
  • Documentation: Change the plugin name from “A.N.R.GHG Publishing Helper” to “A.N.R.GHG Publishing Toolkit”.
  • Documentation: Rename the template files from tpl-*.php to template-*.php.
  • Documentation: Remove the sample anrghg-thanks-block.json file for now.

1.9.4 (2023-05-19)

2914557

  • Security: Provide code to deny access to wp-config.php alongside debug.log.
  • Documentation: Add security recommendation in the Installation section.
  • Documentation: Add the new webfont feature to the feature list.

1.9.3 (2023-05-17)

2913991

  • Web fonts: Performance: Preconnect only once even when multiple fonts are loaded.

1.9.2 (2023-05-17)

2913846

  • Web fonts: Add link to Google Fonts library.
  • Web fonts: Performance: Preconnect to Google Fonts.
  • Interoperability: Restore compatibility with PHP 5.6 lost in v1.9.1 due to fast-tracking a security fix.

1.9.1 (2023-05-17)

2913797

  • Security: Add recommendation and code to deny access to the debug.log file if any exists.

1.9.0.2 (2023-05-09)

2910216

  • Documentation: FAQ: Correct item about recommendation for jQuery using plugin.

1.9.0.1 (2023-05-08)

2913797

  • Documentation: Add server memory limit requirement.
  • Documentation: FAQ: Add item about memory limit issues.
  • Documentation: FAQ: Add recommendation for jQuery using plugin.
  • Documentation: FAQ: Correct item about setting tooltips.

1.9.0 (2023-04-14)

2899298

  • Settings: Interoperability: Split off new section about Customization.
  • Customization: Option to load web fonts.
  • Notes and sources: Lists: Footer deferral: Fix algorithm.
  • Slug body class: Class or ID sanitization: Fix algorithm.
  • Localization: Include configuration for VSCode extension to process PO files for en_US, en_GB.

1.8.4 (2022-12-07)

2830166

  • Localization: IDs and slugs: Fragment identifiers: Debug dash and apostrophe conversion to hyphen-minus.

1.8.3 (2022-11-11)

2816357

  • Post Meta box: Table of contents: Debug fieldset legend.
  • Settings: Improve user interface text strings.
  • Translation: Continue French to 18%.

1.8.2 (2022-11-10)

2815922

  • Split admin/includes/settings.php into 8 files.

1.8.1 (2022-11-10)

2815910

  • Settings: Fix right-to-left position of To-the-top button.
  • Template editor: Add pre-1.8.0 ‘Move into editor’ as an option.
  • Settings: Template editor: Add option for moving into editor in text mode.
  • Internationalization: Increase synergy with WordPress Core, adding context.

1.8.0 (2022-11-08)

2814723

  • Template editor: Debug ‘Move into editor’ buttons, reverting to v0.80.5.
  • Template editor: Add warning not to use ‘Move into editor’ buttons in text mode.
  • Template editor: Default-deactivate pointy bracket unescaping.
  • Settings: Template editor: Unescape pointy brackets: Add switch.
  • Settings: Template editor: Rich text list view: Add switch.
  • Settings: Notes and sources: Tooltips: Position: Add subsection.
  • Settings: Notes and sources: Tooltips: Position: Offset: Add settings.
  • Settings: Notes and sources: Tooltips: Position: Max width: Reorder.
  • Settings: Notes and sources: Tooltips: Scrollable: Add setting.
  • Settings: Notes and sources: Tooltips: Length breakpoint: Rename setting.
  • Settings: Notes and sources: Tooltips: Font size: Add setting.
  • Settings: Notes and sources: Tooltips: Line height: Add setting.
  • Translation: Continue French and Spanish translations up to 12% and 6% respectively.

1.7.8 (2022-11-05)

2812625

  • Templates: Debug when there are no templates.
  • Settings: Security: Reorder information.

1.7.7 (2022-10-28)

2806191

  • Translation: Streamline strings consistently.

1.7.6 (2022-10-23)

2803077

  • Import: Clarify the various button semantics.
  • Localization: Import: Increase synergy with WordPress Core.
  • Settings: Thank You message: Margin: Add missing information.
  • Date information: Support also category pages and date-based archives.

1.7.5 (2022-10-16)

2799649

  • Import: Debug error assessment.
  • Import: Provide more fine-grained information about where the error may reside.
  • Import: Include overwriting templates, by completing the control structure.
  • Import: Stop dying on file errors, with error messages displayed on a white screen.
  • Import: Display error messages normally, using the built-in WordPress feature.
  • Settings: Streamline added information to “Its submenu contains at least Templates and Settings.”

1.7.4 (2022-10-15)

2799294

  • Import: Add pinning functionality to headings.
  • Import: Make success message always visible no matter the scroll position.
  • Import: Fix error handling.
  • Settings: Highlight and advertise pinning functionality.
  • Settings: Admin menu: Add missing information about “The main menu item submenu always contains Templates and Settings.”

1.7.3 (2022-10-09)

2796180

  • Settings: Menu level: Fix menu level transition bug occurring when changed.
  • Settings: Menu level: Remove the checkbox configuring submenu item removal.
  • Settings: Display the reworded success message independently of menu level.
  • Settings: Prevent page from always scrolling to top on reloading after save.
  • Settings: Make success message always visible no matter the scroll position.

1.7.2 (2022-10-08)

2796013

  • Admin pages: Debug current options page slug while settings are not saved or empty.
  • Import: Fix red button style on hover and on active.

1.7.1 (2022-10-02)

2793118

  • Import: Debug display of success message.
  • Import: Display error message instead of dying on problem in custom option name input field.
  • Internationalization: Fix localization syncing with WordPress Core.

1.7.0 (2022-09-27)

2790753

  • Thank You message: Text align setting in the toolbar.
  • Table of contents: Configurable backlink plain tooltips.
  • Admin pages: Header menu: Display also when Export/Import not in submenu.

1.6.22 (2022-09-26)

2790424

  • Template editor: Move ‘Save Changes’ button away from Admin menu to fix submenu access.
  • Templates: Remove empty elements coming in from saving empty editors.
  • Import: Settings: Fix menu level transition bug.

1.6.21 (2022-09-22)

2788512

  • Localization: IDs and slugs: Fix independency of extra conversions.
  • Settings: Localization: IDs and slugs: Reorder settings consistently.
  • Settings: Localization: IDs and slugs: Update more descriptive texts.

1.6.20 (2022-09-20)

2787880

  • Date information: Prevent custom post types from causing variables to be undefined.
  • Localization: IDs and slugs: Stop deleting percent signs, URL-encode them instead.
  • Localization: IDs and slugs: Stop performing no-opt-out character conversions.
  • Localization: IDs and slugs: Stop removing all ‘Symbols-other’ characters.
  • Localization: IDs and slugs: Minimize risk of fixes being overridden.
  • Localization: IDs and slugs: Warn about slug input fields not applying the full set of fixes.
  • Localization: IDs and slugs: Leave punctuation unless accent removal is opted in for, as else dumbing down slugs would be pointless.
  • Settings: Fix Admin submenu access by moving ‘Save Changes’ button to the opposite.

1.6.19 (2022-09-12)

2783090

  • Notes and sources: Anchor tooltips: Restore direct child combinators to debug nested tooltips.
  • Settings: Notes and sources: Lists: Footer deferral: Output buffering: AMP: Advise to edit child theme footer instead.

1.6.18 (2022-09-07)

2781035

  • Localization: IDs and slugs: Fix sanitization by removing full classes.
  • Notes and sources: Lists: Correct line top and bottom padding.
  • Reference lists: Correct line top and bottom padding.

1.6.17 (2022-09-06)

2780783

  • Localization: IDs and slugs: Maintain plus sign instead of letting it turn into space then hyphen-minus.
  • Localization: IDs and slugs: Stop always deleting acute, grave, circumflex accents, macron and hacek.
  • Localization: IDs and slugs: Optionally remove the full set of combining diacritics.
  • Localization: IDs and slugs: Remove the full set of format control characters.
  • Localization: IDs and slugs: Convert Latin alphabetic abbreviation indicators.

1.6.16 (2022-09-05)

2780342

  • Localization: IDs and slugs: Debug portions starting with an ampersand and ending with a semicolon.

1.6.15 (2022-09-04)

2779832

  • Thank You message: Remove direct child combinator from CSS, for AMP compatibility.
  • Notes and sources: Tooltips: Remove direct child combinators from CSS, for AMP compatibility.
  • Slug body class: Debug CSS compliant class names without ASCII characters.
  • Slug body class: Sanitize the “sanitized” plain ASCII class, for CSS compatibility.
  • Slug body class: Add low priority to make sure it keeps working past WordPress v6.

1.6.14 (2022-09-04)

2779672

  • Localization: Extended page slugs: Force lowercase to prevent 404 errors.

1.6.13 (2022-09-03)

2779622

  • Slug body class: Make prefix configurable for test purposes.

1.6.12 (2022-09-03)

2779615

  • Settings: Localization: Streamline acknowledgements.
  • Settings: Add or update acknowledgements.
  • Settings: Slug body class: Prefix configuration setting.

1.6.11 (2022-09-02)

2779423

  • Slug body class: Fix bug occurring when class starts with a hyphen followed by a digit 0-9.
  • Slug body class: Add simplified class based on post ID.
  • Slug body class: URL-decode the page slug.
  • Slug body class: Additional class based on non-sanitized slug.

1.6.10 (2022-09-01)

2779009

  • User experience: Scroll offset: Change CSS so it fits AMP.

1.6.9 (2022-08-31)

2778351

  • Paragraph links: Highlight target link character.

1.6.8 (2022-08-30)

2777873

  • Paragraph links: Debug links added to code blocks.

1.6.7 (2022-08-29)

2777303

  • Table of contents: Debug scroll offset in collapsible tables.

1.6.6 (2022-08-29)

2777091

  • Scroll behavior: Smooth scrolling: Enforce behavior when switch is off.
  • Scroll behavior: Scroll offset: Make universal for consistent user experience.
  • Table of contents: Set end padding from 0 to 7 pixels (awaiting setting).

1.6.5 (2022-08-27)

2776578

  • Localization: PO files: Debug language information.
  • Internationalization: Option to switch between sync and proper.

1.6.4 (2022-08-26)

2776276

  • Localization: Debug translatable strings.
  • Notes and sources: Not process code elements.
  • Notes and sources: Effectively remove underline on anchors and backlinks.
  • Date information: Published first: Support templates.

1.6.3 (2022-08-24)

2775081

  • Settings: Backup: Previews: Correct user experience.
  • Template editor: Debug success message when in Admin submenu.
  • Conversion: Debug success message when in Admin submenu.
  • Import: Add nonce verification.

1.6.2 (2022-08-23)

2773883

  • Thank You message: Fix line breaks, emulate paragraph breaks.
  • Settings: Notes and sources: Combine identical: Move from Lists to Anchors section.

1.6.1 (2022-08-22)

2773700

  • Settings: Backup: Templates: Debug preview toggle.
  • Conversion: Debug editor tabs for localization.
  • Settings: Streamline localization through Backlink tooltip aspect subsection.

1.6.0 (2022-08-21)

2773166

▶ The Thank You message template select configuration is required to change syntax. The only possible separators are space and newline. The previous separator, comma, is allowed in template names. We apologize for the disruption and the inconvenience.

▶ Two added blocks need to change category: The “Thank You message” and “Reference list” blocks were previously in the Design section. As they are about writing and formatting text and lists, they should be moved to the Text section. Making the category configurable for all added blocks is projected. Thank you for your understanding.

  • Settings: Expandable information: Fix accessibility.
  • Blocks: Debug auto-generated preview of editor block.
  • Thank You message: Debug template select configuration.
  • Thank You message: Block: Correct category: “Text”, not “Design”.
  • Reference list: Block: Correct category: “Text”, not “Design”.
  • Reference list: Block: Correct name from plural to singular.

1.5.10 (2022-08-20)

2772962

  • Security: Debug authentication cookie duration configuration.
  • Settings: To the top button: Debug on mobiles.
  • Settings: Subsections: Leading label: Improve readability.
  • Settings: Subsections: Remove excess padding above and below.

1.5.9 (2022-08-19)

2772744

  • Settings: Glide switches: Remove excess padding around.
  • Date information: Chronological order: Set default to no throughout.

1.5.8 (2022-08-18)

2772247

  • Table of contents: List items: Make no underline more robust.
  • Settings: Collapsing behavior: Reorder options for consistency.
  • Options pages: Display top menu only if no top level Admin menu entry.
  • Settings: Settings table of contents: Fix column break.
  • Settings: Settings table of contents: Fix visibility of some features.

1.5.7 (2022-08-17)

2771718

  • Heading links: Debug prepended link text when there is no table of contents.
  • Table of contents: Block: Fix design and textual information.
  • Notes and sources: Backlinks: Fix upper padding.
  • Notes and sources: Backlink tooltips: Debug in target-displayed rows.
  • Notes and sources: Footer lists: Change default text color from blue to green.

1.5.6 (2022-08-16)

2770817

  • Post Meta box: Debug data saving by removing wp_unslash(), additionally to removing sanitize_option().
  • Notes and sources: Block: Add missing collapsing behavior implementation.

1.5.5 (2022-08-15)

2770398

  • Localization: Add four missing sublocale MO files.
  • Settings: Protect must-read information against becoming invisible.
  • Notes and sources: Lists: Remove excess spacing below due to collapsed lines.

1.5.4 (2022-08-14)

2770325

  • Localization: Streamline Gettext strings to alleviate workload.
  • Localization: Inform translators about collapsible and hidden information.
  • Notes and sources: Evaluate tooltip length on the basis of inner HTML.

1.5.3 (2022-08-13)

2770196

  • Table of contents: Remove excess spacing below due to collapsed lines.
  • Import: Fix template overwrite button color for safety and legibility.
  • Import: Improve submit button label readability.
  • Notes and sources: Fix template resolution for CJK with localized space.
  • Localization: Make space and dash localization available for public pages.
  • Reference list: Block: Debug label input placeholder.
  • Table of contents: Block: Fix undefined Gettext function bug.

1.5.2 (2022-08-12)

2769668

  • Notes and sources: Debug post-wide templates preceded by more text.

1.5.1 (2022-08-05)

2766755

  • Notes and sources: Block: Fix design of minimal display mode.
  • Security: Admin bar: Move status icon at the very end of potentially added menus.
  • Internationalization: Make sentence-separating space localizable.
  • Internationalization: Improve context definition of sentence-separating dash.

1.5.0 (2022-08-01)

2764528

▶ Delimiter presets for easy input are changing. If easy default delimiters based on square brackets are in use, and this plugin’s Settings page was not saved since v1.4.7, please save it BEFORE UPGRADING, in order to not be disrupted. Thank you.

  • Security: Display login status in Admin bar.
  • Notes and sources: Delimiters: Ditch square brackets due to interference with Block Editor shortcut.

1.4.14 (2022-07-31)

2763950, 2763951

  • Reference list: Fix CSS error in transition property after 1.4.13.

1.4.13 (2022-07-31)

2763949

  • Notes and sources: Lists: Fix insufficient spacing between heading and first list item.
  • Reference list: Fix insufficient spacing between heading and first list item.

1.4.12 (2022-07-27)

2762177

  • Notes and sources: Tooltips: Debug fullwidth tooltip and its nested tooltips.

1.4.11 (2022-07-26)

2761469

  • Notes and sources: Tooltips: Debug tooltip of source nested in note.

1.4.10 (2022-07-25)

2761232

  • Notes and sources: Lists: Debug visibility of target item on clicking anchor.

1.4.9 (2022-07-24)

2760820

  • Notes and sources: Tooltips: Debug responsive layout for mobile.

1.4.8 (2022-07-20)

2759442

  • Notes and sources: Debug expansion functionality on clicking label.
  • Reference list: Debug expansion functionality on clicking label.
  • Reference list: Block: Correct label and design.
  • Thank You message: Block: Correct label and design.

1.4.7 (2022-07-19)

2758870

  • Notes and sources: Centralize delimiter preset configuration.
  • Notes and sources: Get delimiter presets saved to the DB.

1.4.6 (2022-07-18)

2758223

  • Backup: Fix uploads directory for multisite installations.
  • Template editor: Remove backup preview and bulk upload advice.
  • Import: Templates: Clarify label of ‘Import and Add’ button.
  • Settings: Backup: Correct display of backup paths of templates, settings.
  • Settings: Backup: Add hint about the bulk-upload of templates.

1.4.5 (2022-07-17)

2757477

  • Security: Remove security parameter configuration filters for security reasons.

1.4.4 (2022-07-15)

2757183

  • Thank You message: Debug Gutenberg block for multisite networks by fixing table of contents activation.
  • Table of contents: Remove full deactivation option as useless and causing a bug in multisite networks.
  • Table of contents: Change default to ‘Insert a table of contents if specified accordingly’, and fix legacy.

1.4.3 (2022-07-15)

2757097

  • Thank You message: Prevent last message from block from interfering with default message.
  • Post Meta box: Debug saving data by removing sanitize_option().
  • Settings: Change background color of quoted code from gray to white.

1.4.2 (2022-07-14)

2756584

  • Export: Debug process by debugging .docx ➔ WordPress conversion process.
  • Export: Make existing option name a requirement.
  • Export: Add own heading to reordered templates.
  • Settings: Move ‘Option to deactivate WPTexturize’ to ‘Localization’.
  • Settings: Move ‘URL slug as a CSS selector’ to ‘Interoperability’.
  • Settings: Clarify the relationship between the two ‘ID max length’ settings.
  • Settings: Graceful error handling.
  • Template editor: Graceful error handling.
  • Export/import: Graceful error handling.
  • Conversion: Graceful error handling.

1.4.1 (2022-07-11)

2754765

  • Security: Settings: Add missing nonce field.
  • Security: Settings: Add nonce verification condition to settings saved message.
  • Security: Conversion: Add dual nonce fields and verification.
  • Heading links: Remove tooltips from heading numbers.
  • Heading links: Make CSS more robust, cross-theme compatible.
  • Localization: Allow uppercase in identifiers: Change default from yes to no.

1.4.0 (2022-07-10)

2754237

▶ The security feature’s login screen high and standard profiles should not be used unless the dialog is not useful any longer. Also it is recommended to define the constant in a mini-plugin using the included template, and to delete its definition in wp-config.php.

  • Security: Discourage standard and high profile login screen options.
  • Security: Recommend defining the login control constant in a mini-plugin.

1.3.1 (2022-06-29)

2749921

  • Conversion: Fix bug caused by ignoreFile comment added for linter.

1.3.0 (2022-06-28)

2749265

  • Upgrade notice: Debug and test display after escapement.

1.2.2 (2022-06-28)

2748996

  • Code: Improve online editability of Export, Import, Format conversion and Template editor pages.

1.2.1 (2022-06-27)

2748771

  • Import: Fix bug in exit statements.

1.2.0 (2022-06-27)

2748759, 2748760

  • Import: Templates: Clarify the interface.
  • Import: Custom: Check if provided option name does exist.
  • Import: Fix bug in exit statement display.

1.1.1 (2022-06-27)

2748691

  • Template editor: Backup preview: Improve page searchability by adding the same display toggle as on Settings.

1.1.0 (2022-06-25)

2747832

  • Security: Internal style sheets: Escape style tag elements and arguments.
  • Settings: Backup: Previews: Add scriptless display toggle.
  • Settings: Improve page searchability by removing backup data preview display from default view.
  • Settings: Backup: Make tab navigation more fluid by skipping how-to and preview items.

1.0.4 (2022-06-23)

2747340

  • Localization: Update translations to fix bugs in wording.
  • Template editor: Improve fix of bug appearing at plugin activation.

1.0.3 (2022-06-22)

2746709

  • Notes and sources: Anchor tooltips: Fix display bug.
  • Notes and sources: Backlink tooltips: Fix display bug.

1.0.2.1 (2022-06-22)

2746627, 2746634

  • Documentation: Add screenshots.

1.0.2 (2022-06-22)

2746502

  • Security: Flush unsafe previous versions from the repository.

1.0.1 (2022-06-22)

2746348, 2746353

  • Code: Split six files off anrghg.php to keep the code editable online.

1.0.0 (2022-06-22)

2746150

▶ Plugin re-listing: As of 2022-06-21, this plugin has been re-listed in the Plugin Directory.

  • First production release.

0.81.9 (2022-06-20)

2745571

  • Template editor: Fix bug in form by using correct escapement function and whitelist.

0.81.8 (2022-06-20)

2745384

  • Code: Fix remaining formatting issues before submission.

0.81.7 (2022-06-20)

2745327

  • Security: KSES whitelist: Extend global attributes for a11y.
  • Security: Escape Settings page, Templates editor, other Admin pages.
  • Security: Stall unimplementable security patches.
  • Notes and sources: Fix bug in deactivation setting in Post Meta box.
  • Notes and sources: Replace checkbox with radio buttons in Post Meta box.

0.81.6 (2022-06-18)

2744639

  • Security: KSES whitelist: Fix bug in whitelist extension.
  • Security: Stop trying to use a global KSES whitelist.
  • Security: Date meta tags: Tailor KSES whitelists to the instance.

0.81.5 (2022-06-18)

2744607

  • Security: Internal style sheets: Secure output.
  • Security: Internal style sheets: Restore direct child selectors.
  • Security: KSES: Try implementing the whitelist with extensions.

0.81.4 (2022-06-17)

2744373

  • Revert to 0.81.0, fix broken plugin, remove KSES.
  • Template files: Keep latest versions.
  • Template editor: Fix alignment of ‘Move into editor’ buttons.
  • Admin pages: Header menu: Add plain tooltips.

0.81.3 (2022-06-16)

2743828

  • Security: Settings: Escape UI elements and information.
  • Security: Post Meta box: Escape UI elements.
  • Template editor: Remove pointy bracket conversion.
  • Template editor: Fix alignment of ‘Move into editor’ buttons.
  • Admin pages: Header menu: Add plain tooltips.

0.81.2 (2022-06-15)

2742973

  • Security: Settings: Escaping output: Correct wp_kses() with custom whitelist POC.

0.81.1 (2022-06-15)

2742540

  • Security: Settings: Escaping output: wp_kses() with custom whitelist POC.

0.81.0 (2022-06-14)

2742418

  • Security: Remove Custom CSS feature and CSS configuration filters.

0.80.9 (2022-06-14)

2742232

  • Security: Make login deactivation profile global to fix bug in login …
<br /> <b>Warning</b>: Undefined array key /home/ylinkin/truewp.net/wp-content/plugins/truewp-plugin-info/truewp-plugin-info.php on line 756
" width="120" height="120">
ANRGHG
View Details

Available Versions

Version Download Type
1.17.6 Download Stable
1.17.5 Download Stable
1.17.4 Download Stable
1.17.3 Download Stable
1.17.2 Download Stable
1.17.1 Download Stable
1.17.0 Download Stable
1.16.5 Download Stable
1.16.4 Download Stable
1.16.3 Download Stable
1.16.2 Download Stable
1.16.1 Download Stable
1.16.0 Download Stable
1.15.0 Download Stable
1.14.6 Download Stable
1.14.5 Download Stable
1.14.4 Download Stable
1.14.3 Download Stable
1.14.2 Download Stable
1.14.1 Download Stable
1.14.0 Download Stable
1.13.0 Download Stable
1.12.0 Download Stable
1.11.0 Download Stable
1.10.2 Download Stable
1.10.1 Download Stable
1.10.0 Download Stable
1.9.4 Download Stable
1.9.3 Download Stable
1.9.2 Download Stable
1.9.1 Download Stable
1.9.0 Download Stable
1.8.4 Download Stable
1.8.3 Download Stable
1.8.2 Download Stable
1.6.18 Download Stable
1.6.17 Download Stable
1.6.16 Download Stable
1.6.15 Download Stable
1.6.14 Download Stable
Development Download Trunk

Plugin Info

  • Version: 1.17.6
  • Last Updated: January 21, 2026
  • Active Installs: 10+
  • WordPress Version: 5.5 or higher
  • Tested up to: 6.9.4
  • PHP Version: 7.2 or higher
  • Tags:    
    amp endnotes partials reusable security

Ratings


0.0 out of 5 stars. (0 reviews)

See all reviews

Quick Live Demo

Reports & Analysis

Security Scan

Developer Resources

Useful Links

Scroll to Top