NGINX New Site Creation and Server Configurations

Today I’m going to share with my readers my list for manually creating another website on one of my NGINX servers. I am partially logging this here for my own reference as I often look for these directions I keep stored in a .txt file on my laptop. Wherever you see text in green in this post, it will indicate that the text is to be entered as a command at the command prompt in Linux.

Step by Step Directions to Add a New Site on NGINX Servers

1) Sign into Linux server using an application like Putty (Windows) or Terminal (Mac):

Login with root user and password if possible, otherwise login with the user and password you have and remember to use sudo commands(purring sudo before each command line command)

2) Create the website directory (for example,

mkdir -p /var/www/
mkdir -p /var/www/

3) Change the ownership of the directory to the web user:
chown -R www-data:www-data /var/www/
chown -R www-data:www-data /var/www/

4) Create the web site config file. To do this, you can simply copy the config file of an existing site and then make the required changes. For example try this command but change the existing_site to your own existing website on your server:
cp /etc/nginx/sites-available/ /etc/nginx/sites-available/

5) Edit the new config file to replace with the new site’s values:

nano /etc/nginx/sites-available/
Edit the line that reads: root /var/www/ to be the current domain name.
Edit the two server_name instances to be the new domain name.
Edit access_log and error_log paths for new domain name
Save the file by hitting Ctrl-X, then Y and then Enter.

6) Enable the new site in NGINX:

ln -s /etc/nginx/sites-available/ /etc/nginx/sites-enabled/

7) Restart NGINX:

service nginx restart

9) Create the database and user.

mysql -u root -p
create database database name;
(note: I often create the db and user with the same name as the domain name. That makes it easy to remember. However, MySQL users are limited to 16 characters. so if the domain name is longer, I truncate both in some fashion. Just make sure theu match.
grant all on your_new_site.* to ‘your_new_site’ identified by ‘secret_password’;
(the last part is the password. just make up a hard one – record this where only you can find it, you’ll need it with the restore)

8) Copy your new website files into the public_html folder with your sFTP client and your site is up and running!

Using PHP to create an NGINX SITE MAKER

I used the above knowledge to create a Site Maker tool that does all the steps for you. All you have to do is enter a domain name. Email me if interested at


So, this isn’t too hard if you have something to reference such as the above cheat sheet. Once you get used it doing it, it is really easy. However if it’s too complex, you can do what I did and make a tool to do it for you. Even if it’s not too difficult, the tool saves you time if you add a lot of sites to your NGINX server as I do. Email me if you have interest in such a tool and I can custom build you one for your server! is my email.

PHP Function explode

The PHP explode function is one of the most used PHP functions, at least by me. It is used to turn a string into an array. Let’s say you had the following string:

$str = “Pizza, Pork, Ham, Sub, Chicken, Lamb, Rice, Noodles”;

You can very easily turn such a string into an array using the PHP explode function like this:

$foods = explode(“,”, $str);

Now you have the equivalent of this:

$foods = array(‘Pizza’, ‘Pork’, ‘Ham’, ‘Sub’, ‘Chicken’, ‘Lamb’, ‘Rice’, ‘Noodles’);

Here is a complete PHP example that demonstrates the use of explode:

$str = “Pizza, Pork, Ham, Sub, Chicken, Lamb, Rice, Noodles”;

$foods = explode(“,”, $str);

foreach($foods as $food){

echo $food.”<br />”;


The above example simply uses explode to break the $str string into the $foods array by splitting the string up by the commas.


The PHP explode function takes two arguments:

explode(‘split-by’, $string);

  • split-by – can be any value in $string that you want to separate the string into an array by.
  • $string – is the string you want to turn into an array.


This post should give you a good idea of how to use the explode function. If not, feel free to post your comments on this post and I’ll be happy to explain. Also, feel free to publish your own example code that users explode in the comments.

How to Remove Slugs for a Custom Post Type in WordPress

So, back in the day, not to long ago, one could remove slugs in a CPT(Custom Post Type), simply by adding the following line to the arguments array when calling the register_post_type function:

‘rewrite’ => array(‘slug’ => ”),//NOT THE SOLUTION!

However, that no longer works as of WordPress version 4.7.?, so I put together the following two function from various other solutions I’ve seen. This solution works for a single post type or multiple post types. I am publishing it because I haven’t seen any elsewhere that could handle more than one CPT at a time. I wrote this to remove slugs for two CPTs, but you could us it for one or as many as you want, the two functions are as follows and can be added to functions.php or, as I do, to a plugin file, below the register_post_type functions:


//Two functions to remove slug from team_member and event CPTs:
function remove_evil_slugs($post_link, $post, $leavename) {

    if(‘team_member’ != $post->post_type || ‘event’ != $post->post_type ||’publish’ != $post->post_status) {
        return $post_link;

    $post_link = str_replace(‘/’ . $post->post_type . ‘/’, ‘/’, $post_link);

    return $post_link;
add_filter(‘post_type_link’, ‘remove_evil_slugs’, 10, 3);

function  parse_evil_slugs($query) {

    if(!$query->is_main_query() || 2 != count($query->query) || !isset($query->query[‘page’])) {

    if(!empty($query->query[‘name’])) {
        $query->set(‘post_type’, array(‘post’, ‘team_member’, ‘event’, ‘page’));
add_action(‘pre_get_posts’, ‘parse_evil_slugs’);


Those are the two functions that accomplish the goal. Simply replace all occurrences of “team_member” and “event” with the names of your own custom post types. If you use any rewrite rules in the args parameter for the register_post_type function, comment it out. For example if you see anything that looks like this:

‘rewrite’ => array(‘slug’ => ”),


‘rewrite’ =>false,

…either comment it out of delete it all together from the function that creates the custom post type(CPT).

Update 3-27-2017

I’ve noticed that on some servers, the above solution no longer works, so I was able to program a new solution for NGINX servers. If your server is not an NGINX server, I found a solution here that should work for all even though it is a bit outdated: The code below is code I wrote based on that link but updated for nginx servers:

class JAFTY_CPT_SlugKiller{
    static $_s = null;
    private $htaccess_tag = ‘SLUG KILLER REMOVE SLUG RULES’;
    public function __construct() {
        add_action(‘wp_insert_post’, array(&$this, ‘post_save’));

        add_filter(‘post_type_link’, array(&$this, ‘remove_slug’), 10, 3);
    static public function init() {
        if (self::$_s == null) {
            self::$_s = new self();
        return self::$_s;
    static public function flush_rewrite_rules() {
        $jafty_o = self::init();

    public function post_save($post_id) {
        global $wp_post_types;
        $post_type = get_post_type($post_id);
        foreach ($wp_post_types as $type=>$custom_post) {
            if ($custom_post->_builtin == false && $type == $post_type) {
    public function remove_slug($permalink, $post, $leavename) {
        global $wp_post_types;

        foreach ($wp_post_types as $type=>$custom_post) {
            if ($custom_post->_builtin == false && $type == “team_member”) {
                $custom_post->rewrite[‘slug’] = trim($custom_post->rewrite[‘slug’], ‘/’);
                $permalink = str_replace(get_bloginfo(‘url’) . ‘/’ . $custom_post->rewrite[‘slug’] . ‘/’, get_bloginfo(‘url’) . “/”, $permalink);
        return $permalink;
    public function rewrite_rules($flash = false) {
        global $wp_post_types, $wpdb;
        foreach ($wp_post_types as $type=>$custom_post) {
            if ($custom_post->_builtin == false && $type == “team_member”) {
                $querystr = “SELECT {$wpdb->posts}.post_name
                                FROM {$wpdb->posts}
                                WHERE {$wpdb->posts}.post_status = ‘publish’
                                        AND {$wpdb->posts}.post_type = ‘{$type}’
                                        AND {$wpdb->posts}.post_date < NOW()”;
                $posts = $wpdb->get_results($querystr, OBJECT);
                foreach ($posts as $post) {
                    $regex = “{$post->post_name}\$”;
                    add_rewrite_rule($regex, “index.php?{$custom_post->query_var}={$post->post_name}”, ‘top’);            
        if ($flash == true)
    private function add_rules_htaccess() {
        global $wp_post_types;
        $suffix = get_option(‘jafty_permalink_customtype_suffix’);
        $write = array();
        $htaccess_filename = ABSPATH . ‘/.htaccess’;
            $htaccess = fopen($htaccess_filename, ‘r’);
            $content = fread($htaccess, filesize($htaccess_filename));
            foreach ($wp_post_types as $type=>$custom_post) {
                $rewrite_rule = (!empty($suffix))
                            ? “RewriteRule ^{$custom_post->query_var}/(.+)/\$ /\$1\.{$suffix} [R=301,l]”
                            : “RewriteRule ^{$custom_post->query_var}/(.+)/\$ /\$1 [R=301,L]”;
                if (strpos($content, $rewrite_rule) == false && $custom_post->_builtin == false)
                    $write[] = $rewrite_rule;
            add_action(‘admin_notices’, array(&$this, ‘compatibility_notice’));
        if (!empty($write) && is_writable($htaccess_filename)) {
            $new_rules = ‘# BEGIN ‘ . $this->htaccess_tag . PHP_EOL;
            $new_rules .= str_replace(‘$’, ‘\\$’, implode(PHP_EOL, $write)) . PHP_EOL;
            $new_rules .= ‘# END ‘ . $this->htaccess_tag;
            if (strpos($content, “# BEGIN {$this->htaccess_tag}”) === false) {
                file_put_contents($htaccess_filename, $new_rules . PHP_EOL . PHP_EOL . $content);
            else {
                $pattern = “/# BEGIN {$this->htaccess_tag}.*?# END {$this->htaccess_tag}/ims”;
                $content = preg_replace($pattern, $new_rules, $content);
                file_put_contents($htaccess_filename, $content);
        }else if(!is_writable($htaccess_filename))
            add_action(‘admin_notices’, array(&$this, ‘compatibility_notice’));
    }//end add_rules_htaccess function

    public function compatibility_notice() {
        global $wp_post_types;
        $rules = ”;
        foreach ($wp_post_types as $type=>$custom_post) {
            if ($custom_post->_builtin == false && $type == “team_member”) {
                $slug = str_replace(‘/’, ”, $custom_post->rewrite[‘slug’]);
                $rules .= ‘RewriteRule ^’ . $slug . ‘/(.+)$ /$1 [R=301,L]<br />’;
        echo ‘<div class=”error fade” style=”background-color:red;”><p><strong>Remove Slug Custom post type error!</strong><br />.htaccess is not writable, please add following lines to complete your installation: <br />’.$rules.'</p></div>’;
}//End JAFTY_CPT_SlugKiller class to remove slugs from team_member CPT

//actions and hooks for above class to remove slug from team_member CPT:
add_action(‘init’, array(‘JAFTY_CPT_SlugKiller’, ‘init’), 99);
//the following two lines make it so you don’t have to manually go to settings/permalinks and re-save settings for links to work:
register_activation_hook( __FILE__, array(‘JAFTY_CPT_SlugKiller’, ‘flush_rewrite_rules’) );
register_deactivation_hook( __FILE__, array(‘JAFTY_CPT_SlugKiller’, ‘flush_rewrite_rules’) );


The above code can be added to a plugin file or your themes functions.php.

NOTE: although the above code hasn’t been thoroughly tested on non-nginx servers, it should work if you un-comment the two lines that call the add_rules_htaccess function. Simply do a search for “add_rules_htaccess” and remove the “//” before it in two occurrences and this code should work on any server as long as your .htaccess file is writable.

Get the Nth Weekday of Any Month and Year with JavaScript

In today’s challenge for a client of mine, I had to write a JavaScript function that returns the Nth Weekday of any given month and year. For example it can tell you what the 1st Monday is in December, 2017. It can do past, present and future so if you needed to know the 4th Friday in August of 1910, this function can tell you. If you need to know what the second Sunday of January 2050 is going to be, this JavaScript function will tell you!

Without any further time wasting, here is the JavaScript code that can determine the first, second, third, fourth or even fifth Monday, Tuesday, Wednesday, Thursday, Friday, Saturday or Sunday for any month and year you pass it:

JavaScript Code Returns Nth Weekday for any Given Month & Year:

/* JavaScript getMonthlyWeekday Function:
 * Written by Ian L. of
 * Description:
 * Gets Nth weekday for given month/year. For example, it can give you the date of the first monday in January, 2017 or it could give you the third Friday of June, 1999. Can get up to the fifth weekday of any given month, but will return FALSE if there is no fifth day in the given month/year.
 * Parameters:
 *    n = 1-5 for first, second, third, fourth or fifth weekday of the month
 *    d = full spelled out weekday Monday-Friday
 *    m = Full spelled out month like June
 *    y = Four digit representation of the year like 2017
 * Return Values:
 * returns 1-31 for the date of the queried month/year that the nth weekday falls on.
 * returns false if there isn’t an nth weekday in the queried month/year
function getMonthlyWeekday(n,d,m,y){
var targetDay, curDay=0, i=1, seekDay;
    if(d==”Sunday”) seekDay = 0;
    if(d==”Monday”) seekDay = 1;
    if(d==”Tuesday”) seekDay = 2;
    if(d==”Wednesday”) seekDay = 3;
    if(d==”Thursday”) seekDay = 4;
    if(d==”Friday”) seekDay = 5;
    if(d==”Saturday”) seekDay = 6;
while(curDay < n && i < 31){
    targetDay = new Date(i++ + ” “+m+” “+y);
    if(targetDay.getDay()==seekDay) curDay++;
targetDay = targetDay.getDate();
return targetDay;
}else{return false;}
}//end getMonthlyWeekday JS function
<a href=”JavaScript:var dy = getMonthlyWeekday(1,’Sunday’,’March’, 2017);alert(‘1st Sunday in March, 2017 falls on March, ‘+dy);”>Get first sunday in March, 2017</a><br />
<a href=”JavaScript:var dy = getMonthlyWeekday(2,’Sunday’,’March’, 2017);alert(‘2nd Sunday in March, 2017 falls on March, ‘+dy);”>Get second sunday in March, 2017</a><br />
<a href=”JavaScript:var dy = getMonthlyWeekday(5,’Sunday’,’March’, 2017);alert(‘5th Sunday in March, 2017 falls on March, ‘+dy);”>Get fifth sunday in March, 2017</a><br />
<a href=”JavaScript:var dy = getMonthlyWeekday(4,’Friday’,’April’, 2017);alert(‘4th Friday in April, 2017 falls on April, ‘+dy);”>Get 4th Friday in April, 2017</a><br />
<a href=”JavaScript:var dy = getMonthlyWeekday(5,’Monday’,’April’, 2017);alert(‘5th Monday in April, 2017 falls on April, ‘+dy);”>Get 5th Monday in April, 2017</a><br />
<a href=”JavaScript:var dy = getMonthlyWeekday(3,’Wednesday’,’October’, 1995);alert(‘3rd Wednesday in October, 1995 falls on October, ‘+dy);”>Get 3rd Wednesday in October, 1995</a><br />
<a href=”JavaScript:var dy = getMonthlyWeekday(4,’Wednesday’,’October’, 1995);alert(‘4th Wednesday in October, 1995 falls on October, ‘+dy);”>Get 4th Wednesday in October, 1995</a><br />
<a href=”JavaScript:var dy = getMonthlyWeekday(4,’Wednesday’,’May’, 1975);alert(‘4rd Wednesday in May, 1975 falls on May, ‘+dy);”>Get 4th Wednesday in May, 1975</a><br />


That will do the job! All you have to do is copy and paste the above code in green into a blank text file and name it something like weekdays.html or test.html and open it in any web browser to test the code. Then feel free to alter it to fit your exact needs. Have fun!