WordPress has a nice multi-site system but I am not working on subdomains and I don’t care for a network.
I did some searches on google and never found anything really useful so I created a quick script to handle the multiple domains on a single install.

To install the script:
Edit your wp-config.php, add this code to the top of the file:

/**
 * WordPress Multiple Domains
 *
 * Loads configs based on domain
 * If no config is found initial WordPress install is used
 * Config files are stored in '_domains' in the WordPress directory
 * Config naming convention: {$domain}_wp-config.php
 *  $domain does not use www.
 *
 * @package WordPress
 * @author Jeremy Simkins
 */
/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
    define('ABSPATH', dirname(__FILE__) . '/');

$website = strtolower(str_replace('www.', '', $_SERVER["SERVER_NAME"]));
$website = preg_replace('[^a-z0-9\.-]', '', $website);

// Check if there is a domain config
if (file_exists(ABSPATH . '/_domains/'.$website.'_wp-config.php')) {
    require_once(ABSPATH . '/_domains/'.$website.'_wp-config.php');
    unset($website);
    return; // Step out of file
} // If no config is found, defaults to initial install (could throw an error if forced to use this method)
unset($website);
// End - WordPress Multiple Domains

In your WordPress directory (same as wp-config.php), create a directory named: _domains. Store all domain configs in this directory to have multiple domains run from a single install of WordPress. When saving the configs to the domains folder, make sure to name them using the naming convention in the above snippet.

It’s a pretty simple script, hope you find this useful.

I did want to make note on one issue that I haven’t worked out yet. This would be the uploads directory. I am not sure if this is even an issue yet but it seems possible… There may be a chance of upload collisions between the sites. For development this is not an issue (at least for me) but on a site in production this could be catastrophic.

Update:
I did find out that the media manager does not conflict. There seems to be no issues with running multiple installs using this method.

How the script works:
First it finds each table setup to use DataTables [in my case I am using classes ('.dataTable .table') because not all tables will implement DataTables].
It will build an array of dontSort with each table id in it (make sure you are using the id attribute in your table).

It will then process each th in the thead to see if a no-sort class exists. If the no-sort class exists, it will disable sorting for this column.

    var dontSort = [];
    $('.dataTable .table').each(function () {
        var tmpID = this.id;
        if (dontSort[tmpID] === undefined) {
            dontSort[tmpID] = [];
        }
        $('#'+tmpID+' thead th').each(function () {
            if ( $(this).hasClass( 'no-sort' )) {
                dontSort[tmpID].push( {
                    "bSortable": false
                } );
            } else {
                dontSort[tmpID].push( null );
            }
        } );
    } );
    
    for (var tmpID in dontSort) {
        $('.dataTable #'+tmpID).dataTable({
            "aoColumns": dontSort[tmpID]
        });        
    }

Pretty simple and easy to modify. Let me know if you have any questions.

// Check if we need to perform a redirect
$fetchedURL = isset($_SERVER['HTTP_HOST']) ? $_SERVER['HTTP_HOST'] : '';
if (substr($fetchedURL,0,4) != 'www.') { // Make sure the URL does not use www.
    // Let do the redirect
     header( "HTTP/1.1 301 Moved Permanently" );
     header('Location: http://www.'.$fetchedURL.((isset($_SERVER['REQUEST_URI'])) ? $_SERVER['REQUEST_URI'] : '')); // Append the REQUEST_URI
}

The code is very simple and is documented. I hope some may be able to make use of this script.
The above code will take the provided URL and forward it to the WWW URL. This will retain the full URL path. I.E.: http://son9ne.com/index.php?somevar=somevalue will be changed to http://www.son9ne.com/index.php?somevar=somevalue

The path you can find these files is:
/Library/Application Support/living-e/MAMP PRO/db/mysql
For the latest version of MAMP Pro (currently 1.8.1):
/Library/Application Support/appsolute/living-e/MAMP PRO/db/mysql

I assume that if you are running MAMP Pro, you would only need to amend the path to MAMP if not.

find . -name .svn -print0 | xargs -0 rm -rf

Remember to cd to the directory you are wanting to remove the .svn files from.

cd Sites/project

1. Download an install the latest version of MAMP
2. Install MAMP
   • Install MAMP Pro – I recommend this if you work on multiple projects, it is way easier than editing your hosts file and the http.conf every time
   • If you are NOT using MAMP Pro please use this tutorial

MAMP PRO :

1. Go ahead and make sure that MAMP is working, go to localhost:8888/MAMP and select phpinfo()
2. Check the powered by image, this is the first image, it should look like this
3. Go to the MAMP Pro Controller, Select General
   • First lets get ride of the :8888 at the end of the url, Click on the “Default Ports” option (this will get rid of the ports on the end of the url)
   • Select the PHP tab and check Zen Optimizer to use the optimizer – (Optional)
   • select “Apply” and let the server restart, or restart it if it does not automatically
4. Now go to localhost/MAMP and again select the phpinfo() option. Scroll down to the same image an now you should notice the Extension Manager and the Optimizer set (The Extension Manager will only be on here if you chose to check the optimizer in the step above)

Now We can Setup the Debugger :
Now lets do the supposed hard part, lets turn on the debugger.

1. Download the latest debugger. You can grab it from here – (i downloaded darwin for my intel based mac book pro)
   • Take the file that was extracted and put it in the MAMP directory -
     /Applications/MAMP/bin/php5/zend/lib/
     (i renamed the unzipped folder to ZendDebugger-5.2.14 so i will be using it through the rest of the tutorial, you can name the file whatever you want)
2. The edits are the same for both MAMP and MAMP Pro. The only difference is where the files are located for each. I believe this is the area that is causing the confusion on setting up MAMP with the debugger.
3. The MOST important part of setting up the debugger is the folder structure. you will have to rename the version folder to the correct format.
   • The original folder name is – 5_2_x_comp – you will need to rename it to – php-5.2.x
   • The folder structure should be setup like this

MAMP PRO :

1. Open the php.ini that is being used by MAMP Pro. Now the problem i had with this was i was using the php.ini from the MAMP Pro directory, that is not the correct one. To get to the correct php.ini you have to be in MAMP Pro and choose File -> Edit Template then the appropriate ini file, i will be using php5.ini since i am using php5.
2. Open the php.ini and scroll to the bottom of the file it should look something like this
3. You will want to add after the “MAMP_zend_optimizer_MAMP”
   

   zend_extension_manager.debug_server=/Applications/MAMP/bin/php5/zend/lib/ZendDebugger-5.2.14
   zend_debugger.allow_hosts=127.0.0.1
   zend_debugger.expose_remotely=always

   • The php.ini should look like this now

4. Save the file and restart the server
5. Go to localhost/MAMP and choose phpinfo() and you should now see the debugger in the powered by image.

Now if you did everything correct you will now have the debugger working with your MAMP Install.

Hope this was helpful.

1. Download an install the latest version of MAMP
2. Install MAMP
   • Install MAMP Pro – I recommend this if you work on multiple projects, it is way easier than editing your hosts file and the http.conf every time
   • If you use MAMP Pro you will need to use this tutorial

MAMP :

1. Go ahead and make sure that MAMP is working, go to localhost:8888/MAMP and select phpinfo()
2. Check the powered by image, this is the first image, it should look like this
3. Go to the MAMP Controller, Select Preferences.
   • First lets get ride of the :8888 at the end of the url, Select “Ports” and then click on the “Set to default” option (this will get rid of the ports on the end of the url)
   • Select the PHP tab and check Zen Optimizer to use the optimizer – (Optional)
   • select “OK” and let the server restart
4. Now go to localhost/MAMP and again select the phpinfo() option. Scroll down to the same image an now you should notice the Extension Manager and the Optimizer set (The Extension Manager will only be on here if you chose to check the optimizer in the step above)
   

Now We can Setup the Debugger :
Now lets do the supposed hard part, lets turn on the debugger.

1. Download the latest debugger. You can grab it from here – (i downloaded darwin for my intel based mac book pro)
   • Take the file that was extracted and put it in the MAMP directory -
     /Applications/MAMP/bin/php5/zend/lib/
     (i renamed the unzipped folder to ZendDebugger-5.2.14 so i will be using it through the rest of the tutorial, you can name the file whatever you want)
2. The edits are the same for both MAMP and MAMP Pro. The only difference is where the files are located for each. I believe this is the area that is causing the confusion on setting up MAMP with the debugger.
3. The MOST important part of setting up the debugger is the folder structure. you will have to rename the version folder to the correct format.
   • The original folder name is – 5_2_x_comp – you will need to rename it to – php-5.2.x
   • The folder structure should be setup like this

MAMP :

1. Open php.ini from /Applications/MAMP/conf/php5/ - (or 4 if using php4)
2. Open the php.ini and scroll to the bottom of the file it should look something like this
3. You will want to add
   

   zend_extension_manager.debug_server=/Applications/MAMP/bin/php5/zend/lib/ZendDebugger-5.2.14
   zend_debugger.allow_hosts=127.0.0.1
   zend_debugger.expose_remotely=always

   • The php.ini should look like this now

4. Save the file and restart the server
5. Go to localhost/MAMP and choose phpinfo() and you should now see the debugger in the powered by image.

MAMP PRO :

1. Open the php.ini that is being used by MAMP Pro. Now the problem i had with this was i was using the php.ini from the MAMP Pro directory, that is not the correct one. To get to the correct php.ini you have to be in MAMP Pro and choose File -> Edit Template then the appropriate ini file, i will be using php5.ini since i am using php5.
2. Open the php.ini and scroll to the bottom of the file it should look something like this
3. You will want to add after the “MAMP_zend_optimizer_MAMP”
   

   zend_extension_manager.debug_server=/Applications/MAMP/bin/php5/zend/lib/ZendDebugger-5.2.14
   zend_debugger.allow_hosts=127.0.0.1
   zend_debugger.expose_remotely=always

   • The php.ini should look like this now

4. Save the file and restart the server
5. Go to localhost/MAMP and choose phpinfo() and you should now see the debugger in the powered by image.

Now if you did everything correct you will now have the debugger working with your MAMP Install.

Hope this was helpful

Since Microsoft can’t get their head out of their ass i thought i would post this fix here. If you update to SP3 and you can no longer install updates from the windows update system you will need to register the wups2.dll file.

The file is located in c:/windows/system32/

double click wups2.dll and choose “Open With”

Now Choose “Select the program from a list” and hit “OK”

Now Click on “Browse”

A window will pop up now for you to choose the path to the file to open with.
Click on “My Computer”
Then choose your C drive
Next choose your Windows folder
And then your system32 folder.

Inside the system 32 folder is a program called “regsvr32″ Choose and open that program.

Now it will take you back to the Open with screen and you should see “Microsoft(C) Register Server in the List.

Choose OK and you should see a success screen.

That is it!

Now you can use Windows update again and your updates will install this time.

Hope this was helpful to some. ]]> http://jeremysimkins.com/windows/windows-xp-sp3-breaking-microsoft-updates-fix/feed/ 2 http://jeremysimkins.com/sweetcron/use-one-sweetcron-install-for-multiple-domains/ http://jeremysimkins.com/sweetcron/use-one-sweetcron-install-for-multiple-domains/#comments Sun, 31 Aug 2008 05:58:50 +0000 SoN9ne http://jeremysimkins.com/wordpress/?p=3 Well,

After playing with sweetcron for a bit I wanted to have 4 sites use it but I didn’t want to have to update each site everytime I need to update sweetcron. I found a little tweak you can do to get sweetcron working on multple domains with one install.

First, create the folder and put the files in there from the sweetcron download.

Next, point a domain to that folder ( i am assuming you already know how to create domains and already know how to point your domains to a folder on your server)

Next, point the second domain to that same folder. (at this point you will notice both domains are identical and use the same sweetcron.)

Now we are ready to get each site using its own sweetcron.

First, open /system/applications/config/config.php
you will want to change
“$config['base_url'] = “http://www.your-site.com/”;”
to
“$url = $_SERVER['SERVER_NAME'];
$config['base_url'] = ‘http://’.$url.’/';”

config.php

This will keep the scope correct for which domain you com in from.

Second, open /system/applications/config/database.php
now since we are using multiple domains we will want to create a switch so we can pull the correct data for each domain. I could not get the database prefix to work for me on this setup and I didn’t bother to look into it since I just used different databases for each site. So I created a switch off of the given domain and set the appropriate database to use.

database.php

Now you are able to have multiple sites point to one install of sweetcron.

** NOTE **
I had one issue with install on this. I could not get the database prefix to work correctly with sweetcron. I’m not sure why but i didn’t spend anytime looking into it either. It was just as easy for me to use different databases for each domain. In theory you could do the same switch on the database prefix instead of the database name.