Alex Ciobica

<p>Admin Customization allows you to change the appearance of your WordPress backend.</p>
<p>The plugin allows you to:</p>
<ul>
<li>change the backend favicon.</li>
<li>change the backend logo.</li>
<li>hide the admin logo text and / or logo image.</li>
<li>change the logo text font size.</li>
<li>change the login page logo with a logo of any width.</li>
<li>change the admin footer text.</li>
<li>disable dashboard widgets.</li>
<li>hide update notices and plugin update count.</li>
<li>turn on redirection to homepage on administration panels logout.</li>
</ul>
<p>Translations available:</p>
<ul>
<li>Romanian</li>
<li>French</li>
</ul>
<p>The plugin also corrects some WordPress UX mistakes like not being able to click on the backend or on the login logos, and the fact that the user info dropdown list is mistakenly 2px larger than the dropdown header.</p>
<h4>Author</h4>
<p>You should should follow me (@ciobi) on <a href="http://twitter.com/ciobi/" rel="nofollow ugc">twitter</a>.</p>
<h4>Plugin Last Updated</h4>
<p>October 30th, 2011</p>
<h3>Translations</h3>
<ul>
<li>Romanian</li>
</ul>
<h3>Credits</h3>
<ul>
<li>[Cristi Burcă] (http://scribu.net), for scbFramework (http://scribu.net/wordpress/scb-framework), the plugin framework on which this plugin was built</li>
</ul>


Admin Customization

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.

Admin Customization vs Each domain a page