Any Hostname alters all WordPress-generated URLs according to the servers current hostname, allowing you to use a single site on multiple hostnames.
This plugin will not be able to alter the contents of constants such as
WP_PLUGIN_URL as these are (quite naturally) defined before any plugins are loaded. Plugin developers should instead rely on either one of the
get_option() functions, which will always return the filtered hostname. An example of this is the WPtouch plugin, in which case you can override WPtouch's
compat_get_wp_content_url function, as described by this Gist: https://gist.github.com/1401269.
Any Hostname might also obscure the value of WordPress and Site URL settings on the Options » General settings page, due to the fact that these values are retrieved using the
get_option() function. The values actually stored in WordPress' database is in fact your site's true URL. From 1.0b2 up the plugin will deactivate the host filters on this page, which might cause some page resources to load from the default URL (potentially being unreachable).
Any Hostname will not work on WordPress Network sites (WPMU) due to the fact that the pages in a network install stores its URLs explicitily in the database. Any ideas on how to circumvent this would be greatly appreciated.
Due to a bug in the WordPress Settings API (http://core.trac.wordpress.org/ticket/9296) the plugin settings are located on the Privacy page on WordPress versions below 3.5. From 3.5 and up the settings can be found on the Permalinks page.
Any Hostname has two filters, allowing you to programatically override the filtered hostname or the list of allowed hostnames. These are described below.
Takes a host as argument, and returns a host that will be used when substituting the domain in URLs supplied by WordPress. This filter can be used to make the plugin use a specific host under certain circumstances.
Takes an array of allowed hosts as argument, and returns an array of hosts to be used when checking if the user specified host should be allowed. Hosts should be treated as regular expression patterns.
Requires: 2.7 or higher
Compatible up to: 3.9.1
Last Updated: 2014-5-21
0 of 1 support threads in the last two months have been resolved.
Got something to say? Need help?