Could not retrieve status.

svn: OPTIONS of ‘https://campuslive.slsapp.com/source/campuslive/branches/3.146.0_to_ux’: Server certificate verification failed: Issuer is not trusted (https://www.campuslive.slsapp.com)

To fix this, you should check the SVN path that Coda is using, and compare that to the output of “which svn” at your command line.

Coda was looking here:

/usr/bin/svn

My local SVN installation was looking here:

/opt/subversion/bin//svn

Changing the path in Coda fixed the problem for me.

1. Make sure you are using INNODB for a table engine instead of MyISAM. The table level locking of MyISAM can make inserts very slow on import.
2. Find and open your MySQL config file. On linux this is typically at /etc/my.cnf. On Windows this is typically a file in your MySQL folder named my.ini
3. Add a line (or update if it is there) with the following:
   innodb_flush_log_at_trx_commit=0
4. Add a line (or update if it is there) with the following:
   innodb_buffer_pool_size=1G
5. Set the above size to 50% of the available memory on the server. In the above we set it to “1G” for if you have 2GB available on the server. If you have 8 GB on the server you could set this to “4G”
6. You MUST restart MYSQL on the server for these changes to be used.

I wondered why i had no data under site speed. After some research I found that I needed to modify the GA javascript to include a directive for page speed. You’ll need to add _gaq.push(['_trackPageLoadTime']);   to the inline  javascript as shown here..

<script type="text/javascript">
  var _gaq = _gaq || [];
  _gaq.push(['_setAccount', 'UA-858386-1']);
  _gaq.push(['_trackPageview']);
  _gaq.push(['_trackPageLoadTime']);

...continued...
</script>

After you save your modified file(s), you should begin to see data within 24 hours. Google tracks a small sample of pageviews and averages them all. You’ll see a page by page breakdown of speeds and how many times that page was sampled. This is helpful for finding outliers.

Pros: Nice data over time in a GUI with 2 seconds of work. Breakdown of individual page speeds.

Cons: Using this method fires an additional request to google for a second tracking pixel. Generally you shouldn’t notice this addition.

http://www.youtube.com/watch?v=dW2eAbr5FBw

Here is a screenshot of the CampusLIVE team page inside the view. Cool!

1) Go to your email from YouSendIt and right click on the download button. Copy this link.

2) SSH into your server.

3) Issue the “lynx” command to open a text-based browser

lynx https://rcpt.yousendit.com/1258529888/2f2b4adaf69882f770

4) Anytime you are prompted for a cookie or SSL error, just follow the prompt by pressing “y” or “Y”

5) Once the page loads, you just hit the down key until you get to the link to the file. Then hit the right arrow key to start the download.

6) exit lynx (ctrl + z)

7) locate the file that was downloaded. It’s likely in the folder you’re currently in.

unzip the file

unzip nameoffile.zip

<?
// all of your items to shuffle go here
$links = array('<a href="http://www.google.com">Google</a>',
                 '<a href="http://www.yahoo.com">Yahoo</a>',
                 '<a href="http://www.ebay.com">EBay</a>',
                 '<a href="http://www.cnn.com">CNN</a>',
                 '<a href="http://www.wsj.com">Wall Street Journal</a>'                
                 );

// this shuffles up the array order
shuffle($links);

// let's create a unordered list to display the items
    echo "<ul>";
    
// here's where all the items get printed    
foreach ($links as $link) {
    echo "<li>$link</li>";
    }

// closing the unordered list    
    echo "</ul>";
?>

Stereotypes aside it’s an interesting world we live in

Sink the Splash Pages
Splash Pages: Bad for Usability, Bad for SEO
Splash Pages: Do we really need them?

So if you’re building a website with WordPress and you have a client that despite the horrible idea, demands a splash page, I have a solution for you.

1) Edit header.php (inside your theme folder), adding this to the top

This code checks to see if the cookie “no_splash” is set. If the user hasn’t seen the splash page before, they’ll be redirected to the splash page… splash_page.php (which we create in step 2)

<?php
if(!isset($_COOKIE['no_splash'])) { // Start of the IF statement - if the user does not have a cookie that says whether he/she has visited the splash page, take them to the splash page
header('Location:http://www.yoururlhere.com/splash_page.php'); // Redirect code
} else { // But... if they do have the cookie (they have been on the splash page), just serve the page as normal
//.... do page here
}
?>

2) Create a file called splash_page.php and put it in your site root

At the top of the file we need to add the code to create the cookie, so that next time they come to the site they don’t see this horrible splash page.

<?php

$expire = time() + 60*60*24; // This means, expire in 1 day - 60 seconds * 60 minutes * 24 hours
setcookie("no_splash", "1", $expire); // This makes the cookie. It goes in this order: setcookie(cookie_name, cookie_value, expiry_time)

// Do splash page from here down....
?>

Below this code you will put your HTML for the splash page.

3) You promise to never create another useless splash page!