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.")

Joeri van Veen

<p>Easily manage a large number of landing pages or small websites from a single WordPress site.</p>
<p>This plugin offers an easy way to map different domains to different landing pages on your WordPress site. Now you can easily maintain a large number of small sites from a single WordPress installation.</p>
<p>You don’t have to set anything up, it works out of the box.</p>
<p>Just point a domain that you own to your WordPress installation. In WordPress, create a page for that domain. The slug should be the domain name without ‘www’ and with the <code>.</code>’s replaced by hyphens.</p>
<p>You can see it working on my own domain: wp-developer.eu, which shows a special page with slug <code>wp-developer-eu</code> on my joerivanveen.com blog (joerivanveen.com/blog/wp-developer-eu is the same).</p>
<h4>Benefits:</h4>
<ol>
<li>
<p>Easily reuse and maintain elements like forms on several domains at once.</p>
</li>
<li>
<p>Bring in more traffic using landing pages for multiple domains without hassle.</p>
</li>
<li>
<p>Favicon support for each domain, fallback from child pages to parents.</p>
</li>
<li>
<p>Support for custom post types, e.g. FAQ posts, portfolio posts.</p>
</li>
<li>
<p>The rest of your website keeps working as usual.</p>
</li>
</ol>
<h4>Caveats:</h4>
<ul>
<li>
<p>Some themes use webfonts, for them to work a couple of lines are added to your <code>.htaccess</code>, these are clearly marked #ruigehond007 (this is my seventh plugin).</p>
</li>
<li>
<p>If your blog is in a subfolder of the main site (e.g. my-site.com/blog) you need to take an extra step for this to work, see installation tab.</p>
</li>
<li>
<p>Not all custom post types are guaranteed to work as landing page, e.g. WooCommerce products need additional work to be able to access the main cart.</p>
</li>
<li>
<p>If you need more flexibility (and more work) there is WordPress Multisite.</p>
</li>
</ul>
<p>I put special care in making the plugin very lightweight, you will notice it has virtually no effect on the speed of your installation.</p>
<h3>Favicons</h3>
<p>Switch on <code>with_favicon</code> on the settings page, to allow adding favicons to each landing page (and other pages and posts as well).</p>
<p>Supplying the correct favicon(s) is your responsibility, the plugin will not verify their validity.</p>
<p>As a rule of thumb I would use a small(ish) SVG for modern browsers, and a 32×32 pixel ICO file as fallback.</p>
<p>You may need a plugin to be able to upload ICO and SVG files, since they are blocked by default.</p>
<h4>.htaccess</h4>
<p>In case the plugin was not able to update your <code>.htaccess</code>, these are the lines for your <code>.htaccess</code> to make webfonts function properly, you can add them right after ‘#END WordPress’:</p>
<pre><code>&#35; BEGIN ruigehond007
<IfModule mod_headers.c>
<FilesMatch ".(eot|ttf|otf|woff|woff2)$">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>
</IfModule>
&#35; END ruigehond007
</code></pre>
<p>You may need to switch on headers module in your Apache configuration, if it is not already.</p>
<h3>NGINX</h3>
<p>NGINX does not process <code>.htaccess</code> files as standard. Best is to add the following to your nginx.conf file:</p>
<pre><code>location ~* \.(eot|ttf|otf|woff|woff2)$ {
    add_header Access-Control-Allow-Origin *;
}
</code></pre>
<p>Alternatively you can switch on processing of <code>.htaccess</code> files in your <code>nginx.conf</code> file. In your hosting environment this may be done by disabling ‘direct delivery’ or something similar.</p>


Each domain a page

Five Stars!

Serves a specific page or post from WordPress depending on the domain used to access your WordPress site.

Multisite Blog Alias vs Each domain a page