thingsym

<p>WP Is Mobile Text Widget plugin adds text widget that switched display text using wp_is_mobile() function whether the device is mobile or not.</p>
<h4>Filter Hooks</h4>
<ul>
<li><a href="https://developer.wordpress.org/reference/hooks/widget_title/" rel="nofollow ugc"><code>widget_title</code></a></li>
<li><a href="https://developer.wordpress.org/reference/hooks/widget_text/" rel="nofollow ugc"><code>widget_text</code></a></li>
<li><code>wp_is_mobile_text_widget_text</code> – Filters the content of the Text widget when wp_is_mobile is false.</li>
<li><code>wp_is_mobile_text_widget_is_mobile_true</code> – Filters the content of the Text widget when wp_is_mobile is true.</li>
</ul>
<h4>Support</h4>
<p>If you have any trouble, you can use the forums or report bugs.</p>
<ul>
<li>Forum: <a href="https://wordpress.org/support/plugin/wp-is-mobile-text-widget/" rel="ugc">https://wordpress.org/support/plugin/wp-is-mobile-text-widget/</a></li>
<li>Issues: <a href="https://github.com/thingsym/wp-is-mobile-text-widget/issues" rel="nofollow ugc">https://github.com/thingsym/wp-is-mobile-text-widget/issues</a></li>
</ul>
<h4>Contribution</h4>
<p>Small patches and bug reports can be submitted a issue tracker in Github. Forking on Github is another good way. You can send a pull request.</p>
<p>Translating a plugin takes a lot of time, effort, and patience. I really appreciate the hard work from these contributors.</p>
<p>If you have created or updated your own language pack, you can send gettext PO and MO files to author. I can bundle it into plugin.</p>
<ul>
<li><a href="https://github.com/thingsym/wp-is-mobile-text-widget" rel="nofollow ugc">VCS – GitHub</a></li>
<li><a href="https://wordpress.org/plugins/wp-is-mobile-text-widget/" rel="ugc">Homepage – WordPress Plugin</a></li>
<li><a href="https://translate.wordpress.org/projects/wp-plugins/wp-is-mobile-text-widget" rel="nofollow ugc">Translate WP Is Mobile Text Widget into your language.</a></li>
</ul>
<p>You can also contribute by answering issues on the forums.</p>
<ul>
<li>Forum: <a href="https://wordpress.org/support/plugin/wp-is-mobile-text-widget/" rel="ugc">https://wordpress.org/support/plugin/wp-is-mobile-text-widget/</a></li>
<li>Issues: <a href="https://github.com/thingsym/wp-is-mobile-text-widget/issues" rel="nofollow ugc">https://github.com/thingsym/wp-is-mobile-text-widget/issues</a></li>
</ul>
<h4>Patches and Bug Fixes</h4>
<p>Forking on Github is another good way. You can send a pull request.</p>
<ol>
<li>Fork <a href="https://github.com/thingsym/wp-is-mobile-text-widget" rel="nofollow ugc">WP Is Mobile Text Widget</a> from GitHub repository</li>
<li>Create a feature branch: git checkout -b my-new-feature</li>
<li>Commit your changes: git commit -am ‘Add some feature’</li>
<li>Push to the branch: git push origin my-new-feature</li>
<li>Create new Pull Request</li>
</ol>
<h4>Contribute guidlines</h4>
<p>If you would like to contribute, here are some notes and guidlines.</p>
<ul>
<li>All development happens on the <strong>develop</strong> branch, so it is always the most up-to-date</li>
<li>The <strong>master</strong> branch only contains tagged releases</li>
<li>If you are going to be submitting a pull request, please submit your pull request to the <strong>develop</strong> branch</li>
<li>See about <a href="https://help.github.com/articles/fork-a-repo/" rel="nofollow ugc">forking</a> and <a href="https://help.github.com/articles/using-pull-requests/" rel="nofollow ugc">pull requests</a></li>
</ul>
<h4>Test Matrix</h4>
<p>For operation compatibility between PHP version and WordPress version, see below <a href="https://github.com/thingsym/wp-is-mobile-text-widget/actions" rel="nofollow ugc">Github Actions</a>.</p>


WP Is Mobile Text Widget

WP Is Mobile Text Widget plugin adds text widget that switched display text using wp_is_mobile() function whether the device is mobile or not.

Scott Reilly

<p>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.</p>
<p>Additional features of the plugin controlled both via settings and filters:</p>
<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>
<p>A few things to keep these things in mind:</p>
<ul>
<li>
<p>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:</p>
<p>:wp: => <a href='https://wordpress.org' rel="ugc">WordPress</a><br />
:aol: => <a href='http://www.aol.com' rel="nofollow ugc">America Online, Inc.</a></p>
</li>
</ul>
<p>Otherwise, you risk proper but undesired replacements:</p>
<pre><code>Hi => Hello
</code></pre>
<p>Would have the effect of changing “His majesty” to “Hellos majesty”.</p>
<ul>
<li>
<p>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.</p>
</li>
<li>
<p>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.</p>
</li>
<li>
<p>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></p>
</li>
<li>
<p><strong>SPECIAL CONSIDERATION:</strong> 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”.</p>
</li>
<li>
<p>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.</p>
</li>
</ul>
<p>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></p>
<h3>Developer Documentation</h3>
<p>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.</p>
<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.

WP Is Mobile Text Widget vs Text Replace