podpirate

<p>WP Multisite plugin to maintain URL-redirects for Blogs.</p>
<h3>Features</h3>
<ul>
<li>Permanent 301 Redirect to blogs main domain</li>
<li>Painless installation and activation – no file access necessary.</li>
<li>Checks domain status</li>
<li>Supports UTF-8 Domains</li>
<li><a href="https://wp-cli.org/" rel="nofollow ugc">WP-Cli</a> commands</li>
</ul>
<h3>Usage</h3>
<ol>
<li><strong>Set up your DNS</strong>. Make sure your Domain points to your WordPress installation. You can achieve this by either setting up an A- or CNAME-Record in your DNS configuration. Your webserver must be configured to handle requests on the given Domain.</li>
<li>Under <strong>Network Admin – Sites</strong> edit the site and select the Alias Domains Tab.</li>
<li>Enter the domain without <code>http</code> ao <code>/</code> and click “Add”.</li>
<li>Click “Check Status” to see if it worked. If something went wrong you will see an error message.</li>
</ol>
<p>If you want to redirect with URL path appended (e.g. from <code>some-alias.tld/some/path</code> to <code>some-real-blog.tld/some/path</code>), add this to your <code>wp-config.php</code>:</p>
<pre><code>define( 'WPMU_BLOG_ALIAS_REDIRECT_WITH_PATH', true );
</code></pre>
<h4>Status messages</h4>
<p><strong>Warning: The domain matches the site URL of this blog:</strong> The Blog is using the domain name as Site URL.</p>
<p><strong>Error: The domain is already used by another site:</strong> A different Blog is already using the domain as Site URL. Eiter Remove the alias from the sblog you are currently workin on, or from the other one.</p>
<p><strong>The domain is unreachable:</strong> There is likely an error in your DNS or your Webserver configuration. Use <code>nslookup</code> from he command line or <a href="https://www.whatsmydns.net/" rel="nofollow ugc">whatsmydns.net</a> to check the DNS-Settings.</p>
<p><strong>The domain or a redirect does not point to this blog:</strong> Following all redirects did not end up on your WordPress-Site, but somewhere else. There is likely an error in your DNS or your Webserver configuration.</p>
<h3>WP-CLI Examples</h3>
<h3>Listing Domain aliases</h3>
<p><strong>List alias domains for blog-id 123</strong></p>
<pre><code>wp alias-domains list --blog_id=123
</code></pre>
<p><strong>Output minified json of all aliases</strong></p>
<pre><code>wp alias-domains list --format=json --compact=2
</code></pre>
<p><strong>Output csv including the header row but omitting other messages into file</strong></p>
<pre><code>wp alias-domains list --format=csv --compact > alias-list.csv
</code></pre>
<h3>Add Domain Alias</h3>
<pre><code>wp alias-domains add --blog_id=123 --domain_alias=quux.foobar.tld
</code></pre>
<h3>Remove Domain Alias</h3>
<p><strong>Remove a specific alias</strong></p>
<pre><code>wp alias-domains remove --domain_alias=quux.foobar.tld
</code></pre>
<p><strong>Remove all aliases for blog 123</strong></p>
<pre><code>wp alias-domains remove --blog_id=123
</code></pre>
<h3>Testing Domain Aliases</h3>
<pre><code>wp alias-domains test --domain_alias=quux.foobar.tld<h3>Plugin PHP-API</h3>
</code></pre>
<p>The plugin introduces two functions allowing you to add / remove a domain aliases from inside PHP.</p>
<p><strong>Add Domain alias</strong></p>
<pre><code>$result = alias_domain_add( $blog_id, 'quux.foobar.tld' );
if ( is_wp_error( $result ) ) {
    // handle error
}
</code></pre>
<p><strong>Remove specific Domain alias</strong></p>
<pre><code>$result = alias_domain_remove_by( 'domain_alias', 'quux.foobar.tld' );
if ( is_wp_error( $result ) ) {
    // handle error
}
</code></pre>
<p><strong>Remove Domain aliases for a specific blog</strong></p>
<pre><code>$result = alias_domain_remove_by( 'blog_id', 123 );
if ( is_wp_error( $result ) ) {
    // handle error
}<h3>Development</h3>
</code></pre>
<p>Please head over to the source code <a href="https://github.com/mcguffin/multisite-blog-alias" rel="nofollow ugc">on Github</a>.</p>


Multisite Blog Alias


Thanks for sharing! Works like a charm!


Just works!


This let me do exactly what I needed to do in the most ideal/streamlined/WordPress-integrated way I could imagine it being implemented (it can be so annoying when plugins create their own admin page layout, tables, tabs, styles, etc. when they could've/should've just used what WordPress offers for those as standard, like this plugin has done.) It's flexible depending on certain needs & even has WP-CLI commands without having feature creep of stuff that's unrelated to this plugin's core goal (also on GitHub and doesn't have any ads/promos/upgrades like other plugins.) Even the "Check Status" tool when viewing a site's domain alias(es) is capable (checks many different possible situations [great to see the whatsmydns.net mention for if/when a DNS change might be needed]) yet concise to then be addressed swiftly.



I simply network-enabled the plugin, edited the site details to add the Alias Domain(s), and it worked! This plugin really checked off every box to have this be a top-recommended plugin for this (now more people just need to find out about this & use it instead of hard-coding redirects/rewrites or using plugins that, simply put, aren't as nice as this one. Honestly, this seems like a go-to if/when a WordPress multi-site network has a site on it that wants to use "www." as the primary domain of the site while then not including "www." has WordPress wanting to show either the "register a site" or "you cannot register a site here" since it's considered as a different subdomain & therefore a different site (even though a site that doesn't want to use "www." still resolves properly when that is provided in the URL)... maybe WordPress core will make that no longer needing to be manually accommodated, but this is now my favored way to handle this (replacing rewrites/redirects [especially if/when on nginx or some other hosting setup that might be more restrictive where WordPress should probably just handle it.])



Even the "Donate to this plugin" link for this plugin's details on WP.org is currently going to UN Refugees instead of themselves. This plugin has really earned its praise.


Feature Complete yet Simple to Use (Great for WP Multi-Site Network "www.")

laugei

<p>Have you ever been frustrated when trying to find the text domain of translatable string you want to translate? This task can be challenging and it can take a lot of your time even if you have code reading skills.</p>
<p>This plugin aims to solve this problem by allowing website administrator to inspect text domains of translatable strings directly in the browser.</p>
<p>How to use:<br />
* Press “Inspect Text Domains” button in admin menu bar;<br />
* Red dots will appear next to translatable strings;<br />
* Hover the red dot to view the text domain;<br />
* Open source code in the browser to view text domains in HTML attributes (ctrl+u (Windows) / cmd+opt+u (Mac));</p>
<p>Works in:<br />
* HTML documents;<br />
* HTML fragments;<br />
* HTML attributes;<br />
* Plain text;<br />
* Dynamically loaded content (through AJAX);<br />
* JSON;</p>


Text Domain Inspector


This plugin can inspect the text domain that belongs to which plugin or theme, whatever front-end or back-end.



If you want to do complete or partial localization for the plugin or theme, Text Domain Inspector is the must-have tool.


The MUST-HAVE tool for WordPress localization

Text Domain Inspector is a plugin that helps to inspect text domains of translatable strings

Multisite Blog Alias vs Text Domain Inspector