marapper

Manage custom fields using the insert shortcodes [custom name=”field-name” value=”field-value“] or HTML conditional comments <!–custom name=”field-name” value=”field-value“–> in text of post. It’s a hook for desktop blog clients, which don’t support customfields natively.
Простой хак Вордпресса, позволяющий управлять произвольными полями из любого внешнего клиента или при отправке через почту с помощью шорткодов [custom name=”имя-произвольного-поля” value=”значение“] или условных комментариев <!–custom name=”имя-произвольного-поля” value=”значение“–> прямо в тексте поста.

Custom Shortcodes

Manage custom fields using the insert shortcodes or HTML comment in text of post.

Scott Reilly

This plugin allows you to easily define text or HTML that should be used in your posts in place of words or phrases that are actually present in the posts. This is a handy technique for creating shortcuts to common, lengthy, or frequently changing text/HTML, or for smilies.
Additional features of the plugin controlled both via settings and filters:
<ul>
<li>Text replacement can be enabled for comments (it isn’t by default)</li>
<li>Text replacement can be made case insensitive (it is case sensitive by default)</li>
<li>Text replacement can be limited to doing only one replacement per term, per post (by default, all occurrences of a term are replaced)</li>
<li>Text replacement can be handled early or late in WordPress’s text filtering process (it’s early by default)</li>
<li>Text replacement can be expanded to affect other filters</li>
</ul>
A few things to keep these things in mind:
<ul>
<li>
Your best bet with defining shortcuts is to define something that would never otherwise appear in your text. For instance, bookend the shortcut with colons:
:wp: => <a href='https://wordpress.org' rel="ugc">WordPress</a> 
:aol: => <a href='http://www.aol.com' rel="nofollow ugc">America Online, Inc.</a>
</li>
</ul>
Otherwise, you risk proper but undesired replacements:
<pre><code>Hi => Hello
</code></pre>
Would have the effect of changing “His majesty” to “Hellos majesty”.
<ul>
<li>
If you intend to use this plugin to handle smilies, you should probably disable WordPress’s default smilie handler on the Writing Settings admin page.
</li>
<li>
This plugin is set to filter ‘the_content’, ‘the_excerpt’, ‘widget_text’, and optionally, ‘get_comment_text’ and ‘get_comment_excerpt’. Filters from popular plugins such as Advanced Custom Fields (ACF) and Elementor are also handled by default (see FAQ for specifics). The “More filters” setting can be used to specify additional filters that should be handled by the plugin. The filter ‘c2c_text_replace_filters’ can also be used to add or modify the list of filters affected.
</li>
<li>
Text inside of HTML tags (such as tag names and attributes) will not be matched. So, for example, you can’t expect the :mycss: shortcut to work in <code><a href="" style=":mycss:">text</a></code>
</li>
<li>
SPECIAL CONSIDERATION: Be aware that the shortcut text that you use in your posts will be stored that way in the database. While calls to display the posts will see the filtered, text-replaced version, anything that operates directly on the database will not see the expanded replacement text. So if you only ever referred to “America Online” as “:aol:” (where <code>:aol: => <a href='http://www.aol.com'>America Online</a></code>), visitors to your site will see the linked, expanded text due to the text replace, but a database search would never turn up a match for “America Online”.
</li>
<li>
However, a benefit of the replacement text not being saved to the database and instead evaluated when the data is being loaded into a web page is that if the replacement text is modified, all pages making use of the shortcut will henceforth use the updated replacement text.
</li>
</ul>
Links: <a href="https://coffee2code.com/wp-plugins/text-replace/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/text-replace/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/text-replace/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Developer Documentation</h3>
Developer documentation can be found in <a href="https://github.com/coffee2code/text-replace/blob/master/DEVELOPER-DOCS.md" rel="nofollow ugc">DEVELOPER-DOCS.md</a>. That documentation covers the numerous hooks provided by the plugin. Those hooks are listed below to provide an overview of what’s available.
<ul>
<li><code>c2c_text_replace_filters</code> : Customize what hooks get text replacement applied to them.</li>
<li><code>c2c_text_replace_third_party_filters</code> : Customize what third-party hooks get text replacement applied to them.</li>
<li><code>c2c_text_replace_filter_priority</code> : Override the default priority for the ‘c2c_text_replace’ filter.</li>
<li><code>c2c_text_replace</code> Customize or override the setting defining all of the text replacement shortcuts and their replacements.</li>
<li><code>c2c_text_replace_comments</code> : Customize or override the setting indicating if text replacement should be enabled in comments.</li>
<li><code>c2c_text_replace_case_sensitive</code> : Customize or override the setting indicating if text replacement should be case sensitive.</li>
<li><code>c2c_text_replace_once</code> : Customize or override the setting indicating if text replacement should be limited to once per term per piece of text being processed regardless of how many times the term appears.</li>
</ul>

Text Replace

Replace text with other text. Handy for creating shortcuts to common, lengthy, or frequently changing text/HTML, or for smilies.

Custom Shortcodes vs Text Replace