WordPress query_var by domain

Question

I'd like to add a query variable to all queries coming from a certain domain.

For example, mydomain.com and proxydomain.com both show the same WordPress site, but for users visiting via proxydomain.com, I'd like to be able to handle their queries differently.

Additionally, I'd like to apply some different CSS styles for visitors coming through proxydomain.com.

I was thinking I could check for the query_var and apply classes based on the presence of that variable.

It is NOT what you asked for (and as such I am making it a comment instead of an answer), but you could easily use $_SERVER['REMOTE_HOST'] to get the requests and run compares on that. — josh.chavanne, Apr 17 '15 at 23:08
i.e. if($_SERVER['REMOTE_HOST']==='proxydomain.com'){ //do some proxydomain specific stuff or assign a variable } — josh.chavanne, Apr 17 '15 at 23:09

d79 · Accepted Answer · 2015-04-18T13:53:05.923

This is the code to add to your functions.php file:

add_filter( 'body_class', 'domain_as_body_class' );
function domain_as_body_class( $classes ) {
    $classes[] = sanitize_title( $_SERVER['SERVER_NAME'] );
    return $classes;
}

It adds the sanitized domain of your site (i.e. mydomain-com or proxydomain-com) as class of the body tag of your pages, so you can target the relative class for custom styles.

Update

For the queries you could add a function again in functions.php like:

function is_proxydomain() {
    return 'proxydomain.com' == $_SERVER['SERVER_NAME'];
}

And then use it when needed on a query:

if( is_proxydomain() ) {
    $args = array(
        // arguments for proxydomain.com
    );
} else {
    $args = array(
        // arguments for mydomain.com
    );
}

$query = new WP_Query( $args );

score 1 · Answer 2 · edited May 23 '17 at 12:06

I like the answer of d79 for the first part.

For the queries, I think it would be better to extend WP_Query class ( i.e. WP_Query_Custom ) and have one copy for each domain. Then you can load the file you need based on the domain in the functions.php file, and so you don't need to change in the future your calls everywhere you use WP_Query_Custom, even if you need to add more domains and different versions of WP_Query_Custom.

//in functions.php
$mydomain = str_replace('.', '_', $_SERVER['SERVER_NAME']);
require_once("path/to/my/classes/$mydomain/WP_Query_Custom.php");

 //In each path/to/my/classes/$mydomain/WP_Query_Custom.php

 class WP_Query_Custom extends WP_Query {

function __construct( $args = array() ) {
    // Force these args
    $args = array_merge( $args, array(
        'post_type' => 'my_custom_post_type',
        'posts_per_page' => -1,  // Turn off paging
        'no_found_rows' => true // Optimize query for no paging
    ) );

    add_filter( 'posts_where', array( $this, 'posts_where' ) );


    parent::__construct( $args );

    // Make sure these filters don't affect any other queries
    remove_filter( 'posts_where', array( $this, 'posts_where' ) );
}



function posts_where( $sql ) {
    global $wpdb;
    return $sql . " AND $wpdb->term_taxonomy.taxonomy = 'my_taxonomy'";
}
}

The example class is copied from extending WP_Query

You should obviously test for file existence, like `code` if( file_exists( "path/to/my/classes/$mydomain/WP_Query_Custom.php" ) ){ //load }else{ //handle error } `code` — appartisan, Apr 22 '15 at 08:55

WordPress query_var by domain

2 Answers2