How much SHOULD you be paying for web hosting and web development?

June 27, 2014 at 2:27 pm

Web Development can become a tricky thing to budget for when you don’t really know what your options are or how much those options should cost. This really great tool which is 100% FREE will ask you a couple of questions and give you some really valuable insight into how much you can expect to pay for various services.

Try it out for FREE here.

Here’s some of the advice I got regarding hosting…

Free Quote Estimation

Get your own Drupal Project Funded!

June 26, 2014 at 5:31 pm


Is there a module or a feature you’ve been dying to get off the ground, but just haven’t been able to get the funding to build it? Then is just the thing for you.

I’ve been using Drupal for about 6 years and to date I’ve never found a place where once can easily submit a project and get funding for that project. I submitted my first project to DrupalFund 7 days ago and today it went into the funding stage. The module I propose is something I know people would definitely use, but how if people are willing to throw money at it… that’s the million dollar question.

You can view my project here.


My Skype Broke and This is How I Fixed It

June 25, 2014 at 7:33 am

Skype was working great for a while, until I recently opened it and saw this:

What my broken skype looks like


This is what I did to fix it:

  1. Completely uninstalled Skype, including “Click to Call”
  2. Delete the entire folder in C:/Users/~username~/AppData/Roaming/Skype (Warning: you will lose all previous chat data)
  3. Delete the entire folder in C:/ProgramData/Skype
  4. Click start and type in: %temp%\skype
  5. Now delete the delete the dbTemp folder
  6. I then downloaded an older version of skype here (i picked Skype
  7. I installed the app and all was well with the world again

How to debug SSL?

June 16, 2014 at 11:57 am

Until quite recently, this blog post would have consisted of me explaining how you use Firebug to inspect each request to see if any URLs are being called without “https”. Luckily that’s no longer necessary, thanks to this very cool tool:


i.e. This site:

It allows you to enter the URL giving you problems, and breaks down exactly why the SSL isn’t doing what it should. Here’s an example:


How to deal with SSL in Laravel?

June 16, 2014 at 6:31 am

SSLAs you probably already know, Laravel has a lot of flexibility around “routes” and even more so if you combine it with “filters“. The easiest way to deal with SSL in Laravel is using filters. As apposed to struggling with .htaccess or doing it some other way in code. I created the following two filters and this solved the problem for me:

    Route::filter('force.ssl', function()
        if( ! Request::secure())
                    Request::path().(empty($_SERVER['QUERY_STRING']) ? '' : '?'.$_SERVER['QUERY_STRING'])

    Route::filter('no.ssl', function()
        if( Request::secure())
            return Redirect::to(
                Request::path().(empty($_SERVER['QUERY_STRING']) ? '' : '?'.$_SERVER['QUERY_STRING']), 302, array(), false

You can then use it like this:

Route::group(array('before' => 'no.ssl'), function()
    Route::resource('/', 'SiteController');

I’m sure the “QUERY_STRING” part could probably be replaced with a more Laravel-y way of doing this, but this worked for me.

Help! Avast is blocking my website!

June 13, 2014 at 1:30 pm

avastIf you ever needed a reason to do more thorough code reviews, here’s a good one. I made the mistake of leaving the following link in the code of one of my projects:

Yes, spare me the lecture. I know this is bad and could easily have been avoided. Nevertheless, I am writing about this, because what was annoying about this was how I managed to find that it was causing issues: a friend of mine actually told me they can’t access the site because Avast is blocking them. Long story short, Avast sees this kind of code as a malware attack. Rightly so too, because a malicious website could do malicious things using a tactic like this.

My problem, however, came in after fixing the link. Even after restarting my machine, and telling Avast that the URLs are safe, it still decided to block the site. First prize would’ve been for it to just forget that it came across the site and rescan it as a new potential threat. This way I would be able to tell if something was still wrong. Unfortunately, Avast doesn’t work like that. In order to fix the problem, you get to do this:

  1. Double click on the Avast icon in the bottom right
  2. Click on “Settings”
  3. Click on “Active Protection”
  4. Disable “Web Shield”

This solved the problem for me, and me only. I still need to figure out how much of a problem this is for other users. There are bound to be other Avast users that are still blocked from accessing the site. I started by reporting the issue as a false positive here.

And now I play the waiting game…


Its a day later and I never heard back from Avast but it seems Avast is no longer blocking my site. So either they saw my complaint, or it expires after a  certain amount of time.