What we’ll do is just give the user non-administrator access to the analytics. This isn’t ideal, but it’s the best we can do. Here’s how:

1. Log in to Google Analytics.
2. Click the “Admin” button at the top-right.
3. Click the Account the website belongs to.
4. Click the Property you want to give access to. If you skip this step, you’ll probably do something you didn’t want to
5. Click the Profile (or “All Web Site Data”) that you want to give access to.
6. Click on the “Users” tab
7. Click “+ New User”
8. Enter the person’s email address and select “User” as the role.

The next time they log in they’ll be able to see the data for that website only and none of the other websites that you have in your Account. Like I said earlier, this has some drawbacks in that you are still the admin and could revoke their access at any time. I recommend that the new owner create a new Account/Property/Profile in their own Google Analytics account and change all of the analytics codes in their website to the new code. With this method, they’ll have full control of their analytics, but still have access to the historical data.

First, let’s go over some terminology. Since there’s a deep hierarchy, it’s important to know what’s what. Throughout this article, I’ll capitalize these terms so they’re easier to identify.

• User Account – This is your Google account.
• Account – This is the account that you will be transferring.
• Property – This is the website.
• Profile – This is a view of your analytics data.

View your accounts by logging in to Google Analytics and clicking the home button. In this screenshot, I’ve circled an Account that has one Property that has one Profile. You might have multiple items.

You will be transferring the entire account, along with all properties that belong to it. If you see websites listed in that account that you do not want to transfer, you shouldn’t proceed with this tutorial! There is no way to split them up. I wrote a separate post for what you should do in this case.

If everything beneath the Account is okay to transfer, follow these steps:

1. Click the “Admin” button at the top-right.
2. From the list click the account you want to transfer.
3. Click the “Users” tab.
4. Click the “+ New User” button.
5. Enter the new user’s email address, select “Administrator” for the role, and then check “Add User”.

That’s it! If all went well, when the new user logs in to Google Analytics, they will see the account and all of the data. After they’ve confirmed that it’s all working, for security they should remove your email on that same “Users” tab.

1. Initiate the domain transfer. Each registrar has a slightly different process, so check with them to find out how to make the transfer. This process takes at least five days, so I like to do this first. If you want to minimize the total amount of time it takes for the complete site transfer, you should do this right after step 9. The domain is one of the most important assets in a site purchase, so I prefer to do this first-thing.
2. Set up the web host that the site will be moving to. I use HostGator, which has been a pretty good PHP/WordPress host. I have a reseller account so all of my websites are completely sectored off from each other. This makes managing the sites very clean and easy.
3. Transfer the files from the old host to the new host.
4. Transfer all the databases (if any) from the old host to the new host.
5. Transfer all email accounts from the old host to the new host. If applicable, transfer ownership of the Google Apps account.
6. Set up AdSense for the new site. Remember to create ad units for all ads on the site and to update all ad codes. Also, create AdSense custom channels.
7. Transfer ownership of Google Analytics account or set up a new account. Remember to update the Analytics code if you’ve set up a new account.
8. Test the new website and fix any issues. You can hard-code the domain and IP in your computer’s hosts file so you can see the new site without the rest of the world seeing it. Just remember to remove it when you’re done!
9. Change the DNS for the domain to point to the DNS servers of the new host
10. Transfer ownership of Facebook, Twitter, and all other social media accounts.

I figured out how to rank the objects and avoid duplicates. It’s not that elegant, so if you have a better solution I’d love to hear it.

from django.db.models import Sum

photo_list = Photo.objects.annotate(total_votes=Sum('votes')).order_by('-total_votes')


1. Install VirtualBox Guest Additions on the Linux VM
   • On the host VM, click “Devices”->”Install Guest Additions”
   • cd /media/cdrom
   • sudo mount /dev/cdrom /media/cdrom
   • sudo ./VBoxLinuxAdditions.run
2. Create the shared folder
   • Open the host VM settings
   • Click “Shared Folders”
   • Click the icon with the plus sign to add a share
   • Select the path on your host system that you want to designate as the commonly shared directory
   • Check “Auto-mount” and “Make Permanent”
   • Click “OK” to save the share
3. Add your user to the group so you can access the share
   • useradd -a -G vboxsf [username]
   • Reboot

After you do these steps, your share will be available on your host operating system and your Linux guest operating system (and will be there on reboot). You can find the share on your Linux system at /media/sf_shared .

Today, I discovered that Google Calendar does this exact thing! And since I sync my calendar with my Android phone, I get the birthdays placed on my phone’s calendar too. I absolutely love this feature, but it’s sort of obscure to get to. There are instructions on how to do it at Nicholas Overstreet.

Before you even fire up the computer, decide on the 3-5 most important attributes of a successful worker in your business. You will attract better matches when your job listing describes what is important in a new recruit. It will also help make filtering through all the applicants significantly easier.

Especially in today’s economy, you’ll no doubt have a lot of people respond to your job opportunity. You need to remember all along the way the things that matter most to your business. One of the things that is important for us is that our writers pay extremely close attention to detail. When we create a job listing, we state in the first sentence that that’s what we’re looking for. Then we proceed to state the exact steps that they need to take to be considered. It always surprises me at how many people don’t follow our directions, even when we’ve stated in the first sentence that we won’t consider anybody who doesn’t follow all the directions. Because we embed a test into the application process, we’re able to weed out in just a matter of seconds about 80% of the applicants.

Be up front with your applicants. For me this means highlighting the advantages of working with your company as well as disclosing the significant disadvantages. Although some might not agree, I like to state a salary range directly in the job posting and outline what it takes to get raises. Sure, this gives the other person a slight advantage in negotiations, but it also reduces the time spent on back-and-forth on every project. This will allow you both to spend more time on what matters most–your product.

Back in February, my friend and I started a business that we named GrabContent. In a nutshell, we create custom, search engine optimized articles in order to help our customers improve their websites’ organic traffic. You’re probably wondering why we’re doing this and how we plan to compete against the jillions of other writers in the world. The current problem is that it takes quite a bit of turnaround time when you need large numbers of articles, and you don’t want to sacrifice the quality of the writing. We’ve got a few tricks up our sleeves to solve these problems without charging more.

I won’t reveal our secret sauce, but in the next few blog posts, I’ll talk about some of the things we’ve learned along the way. I’m hoping to be able to talk about how to select writers, what writers can improve on, and how we’re managing our technology back end.

To install, just copy that file over to /usr/lib64/purple-2/ . If you don’t have root access, copy it to ~/.purple/plugins/ instead. Then restart Pidgin, enable the plugin, and you’re good to go!

First, create your db table:

CREATE TABLE `users` (
  `id` int(11) unsigned NOT NULL auto_increment,
  `email` varchar(60) default NULL,
  `firstname` varchar(30) default NULL,
  `lastname` varchar(30) default NULL,
  `password` varchar(40) default NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8

Next, create models/user.php and add validation definitions. Modify the validation parameters as neede. You’ll also need a function that checks whether the two password fields match.

class User extends AppModel {
  var $name = 'User';
  var $useTable = 'users';


  var $validate = array(
    'email' => array(
      'kosher' => array(
        'rule' => 'email',
        'message' => 'Please make sure your email is entered correctly.'
      ),
      'unique' => array(
        'rule' => 'isUnique',
        'message' => 'An account with that email already exists.'
      ),
      'required' => array(
        'rule' => 'notEmpty',
        'message' => 'Please Enter your email.'
      )
    ),
    'passwd' => array(
      'min' => array(
        'rule' => array('minLength', 6),
        'message' => 'Usernames must be at least 6 characters.'
      ),
      'required' => array(
        'rule' => 'notEmpty',
        'message'=>'Please enter a password.'
      ),
    ),
    'passwd_confirm' => array(
      'required'=>'notEmpty',
      'match'=>array(
        'rule' => 'validatePasswdConfirm',
        'message' => 'Passwords do not match'
      )
    ),
    'firstname' => array(
      'required' => array(
        'rule' => 'notEmpty',
        'message'=>'Please enter your first name.'
      ),
      'max' => array(
        'rule' => array('maxLength', 30),
        'message' => 'First name must be fewer than 30 characters'
      )
    ),
    'lastname' => array(
      'required' => array(
        'rule' => 'notEmpty',
        'message' => 'Please enter your last name.'
      ),
      'max' => array(
        'rule' => array('maxLength', 30),
        'message' => 'Last name must be fewer than 30 characters'
      )
    )
  );

  function validatePasswdConfirm($data)
  {
    if ($this->data['User']['passwd'] !== $data['passwd_confirm'])
    {
      return false;
    }
    return true;
  }

  function beforeSave()
  {
    if (isset($this->data['User']['passwd']))
    {
      $this->data['User']['password'] = Security::hash($this->data['User']['passwd'], null, true);
      unset($this->data['User']['passwd']);
    }

    if (isset($this->data['User']['passwd_confirm']))
    {
      unset($this->data['User']['passwd_confirm']);
    }

    return true;
}

}

Create the controllers/user_controller.php file:

class UsersController extends AppController {
  var $name = 'Users';
  var $helpers = array('Html', 'Form');
  var $components = array('Auth');

  function beforeFilter() {
    $this->Auth->fields = array(
        'username' => 'email',
        'password' => 'password'
    );

    $this->Auth->allow('register');
  }

  function index() {

  }

  function login() {

  }

  function logout() {
    $this->redirect($this->Auth->logout());
  }

  function register() {
    if (!empty($this->data)) {
      $this->User->create();
      if($this->User->save($this->data))
      {
        $this->Session->setFlash("Account created!");
        $this->redirect('/');
      }
    }
  }

}

Create the login.ctp view:

$session->flash('auth');
echo $form->create('User', array('action' => 'login'));
echo $form->input('email');
echo $form->input('password');
echo $form->end('Login');
echo $html->link('Sign up', array('controller'=>'users', 'action'=>'register'));

Create the register.ctp view:

echo $form->create('User', array('action' => 'register'));
echo $form->input('email');
echo $form->input('firstname');
echo $form->input('lastname');
echo $form->input('passwd');
echo $form->input('passwd_confirm', array('type' => 'password'));
echo $form->submit();
echo $form->end();

Notice that we named the field “passwd” and not “password”? This is because Cake recognizes it as being a password and automatically hashes it. Although you could set up your app this way, it makes it complicated to do validation on it. Instead, we just use “passwd” and assign the value to “password” in our beforeSave function.

That’s it! Your basic user login/registration should be working now. Customize it according to your app’s needs.