mschwar

Google Maps made Simple by WP-G-Mappity
WPGMappity allows you to easily insert Google Maps into your posts. No XML or JavaScript needed, building a Google Map is done completely in a WYSIWYG form inside your blog.
Versions 0.5 and above use version 3 of the Google Maps API. For you this means:
<ul>
<li>No API key needed</li>
<li>New features</li>
<li>Fast downloads: visitors to your blog only download one extra file from Google – nothing from you.</li>
</ul>
Features include:
<ul>
<li>Markers and custom icons</li>
<li>Routing</li>
<li>Map Controls</li>
<li>Completely customizable size and alignment</li>
</ul>
Project Home, full instructions, and help: <a href="http://matthewschwartz.me/wordpress/wpgmappity/" rel="nofollow ugc">http://matthewschwartz.me/wordpress/wpgmappity/</a>

Google Maps made Simple

Point, Click, Map. Build and insert Google Maps just as easily as you insert images.  All WYSIWYG: no JavaScript, no XML, no coding at all.

Joeri van Veen

Easily manage a large number of landing pages or small websites from a single WordPress site.
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.
You don’t have to set anything up, it works out of the box.
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.
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).
<h4>Benefits:</h4>
<ol>
<li>
Easily reuse and maintain elements like forms on several domains at once.
</li>
<li>
Bring in more traffic using landing pages for multiple domains without hassle.
</li>
<li>
Favicon support for each domain, fallback from child pages to parents.
</li>
<li>
Support for custom post types, e.g. FAQ posts, portfolio posts.
</li>
<li>
The rest of your website keeps working as usual.
</li>
</ol>
<h4>Caveats:</h4>
<ul>
<li>
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).
</li>
<li>
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.
</li>
<li>
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.
</li>
<li>
If you need more flexibility (and more work) there is WordPress Multisite.
</li>
</ul>
I put special care in making the plugin very lightweight, you will notice it has virtually no effect on the speed of your installation.
<h3>Favicons</h3>
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).
Supplying the correct favicon(s) is your responsibility, the plugin will not verify their validity.
As a rule of thumb I would use a small(ish) SVG for modern browsers, and a 32×32 pixel ICO file as fallback.
You may need a plugin to be able to upload ICO and SVG files, since they are blocked by default.
<h4>.htaccess</h4>
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’:
<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>
You may need to switch on headers module in your Apache configuration, if it is not already.
<h3>NGINX</h3>
NGINX does not process <code>.htaccess</code> files as standard. Best is to add the following to your nginx.conf file:
<pre><code>location ~* \.(eot|ttf|otf|woff|woff2)$ {
 add_header Access-Control-Allow-Origin *;
}
</code></pre>
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.

Each domain a page

Five Stars!

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

Google Maps made Simple vs Each domain a page