Adrian Mörchen

moewe.io

Markus Weigelt

Tiles Proxy for OpenStreetMap provides a basic proxy, which allows other OpenStreetMap plugins to load map tiles from your server instead from OpenStreetMap servers.
Sponsor: <a href="https://sachsen.tours" rel="nofollow ugc">sachsen.tours</a>
Contribute: <a href="https://github.com/moewe-io/osm-tiles-proxy" rel="nofollow ugc">https://github.com/moewe-io/osm-tiles-proxy</a>
Known to work with these plugins
<ul>
<li><a href="https://de.wordpress.org/plugins/leaflet-map/" rel="nofollow ugc">Leaflet Map</a></li>
<li><a href="https://wordpress.org/plugins/cpt-to-map-store/" rel="ugc">Custom Post Type to Map Store</a></li>
<li><a href="https://wordpress.org/plugins/geolocation/" rel="ugc">Geolocation</a></li>
<li>Another plugin? Let us <a href="https://wordpress.org/support/plugin/osm-tiles-proxy" rel="ugc">know</a>.</li>
</ul>
Notes
<ul>
<li>Beware: Depending on your map and the tiles you need, a lot of storage is needed.</li>
<li>Might be slower than official servers (depends on your server)</li>
<li>First requests might be slow as map tiles are cached on request</li>
</ul>
Filters
You can use filters to get the URLs from the plugin:
<pre><code> $proxy_cached_url = apply_filters( 'osm_tiles_proxy_get_proxy_url', $proxy_cached_url );
 $proxy_rest_api_url = apply_filters( 'osm_tiles_proxy_get_proxy_rest_url', $proxy_rest_api_url );
 $leadlet_js_url = apply_filters( 'osm_tiles_proxy_get_leaflet_js_url', $leadlet_js_url );
 $leadlet_css_url = apply_filters( 'osm_tiles_proxy_get_leaflet_css_url', $leadlet_css_url );
</code></pre>
Constants
To disable cache invalidation when WP Rocket or WP Fastest Cache invalidate their cache, you can set the following constant in your <code>wp-config.php</code>
<pre><code>define( 'OSM_PROXY_DISABLE_CLEAR_CACHE', true );
</code></pre>

Tiles Proxy for OpenStreetMap

A basic proxy that lets OpenStreetMap plugins load map tiles from your own server instead of OpenStreetMap servers.

TinyMCE SpellChecker API – this plugin provides action/filter hooks to allow easy customisation of the TinyMCE SpellChecker.
This plugin was created to solve the problem of not being able to use GoogleSpell behind a firewall. For background information on the issue read the discussions on <a href="https://core.trac.wordpress.org/ticket/9798" rel="nofollow ugc">trac ticket #9798</a>. The ultimate goal of this plugin is to be merged into WordPress Core.
You need this plugin if…
<ul>
<li>You want to write a plugin for the TinyMCE SpellChecker. This plugin will provide you with respective hooks that allow to control which SpellChecker Engine is used, adjust the configuration used for initialisation of the engine and manipulate spellchecking results (independent of engine).</li>
<li>You are behind a firewall and you’d like to use the Google Spellchecker. This plugin contains a customised version of GoogleSpell that uses the new Http Transportation methods added in WordPress 2.8 which include Proxy Support for all external requests.</li>
</ul>
This plugin also contains a simple sub-plugin called “WP-SpellCheck Exceptions” which allows you to add custom words to the spellchecking dictionary. Note that this plugin is more a proof of concept than a complete/full-fleged solution. (It does not have any kind of visual administration; it only adds “WordPress” as an exception at the moment).

WP-Spellcheck

TinyMCE SpellChecker API - this plugin provides action/filter hooks to allow easy customisation of the TinyMCE SpellChecker.

Tiles Proxy for OpenStreetMap vs WP-Spellcheck