Sometimes you want to have a dynamic segment in a route. For example: /:username, to allow your users to have vanity urls. You might use something like this:

However, you obviously don’t want routes like /login or /logout to be routed to your controller (in the above case, the profiles controller). In this case we would use segment constraints. Rails allows you to use either a regular expression as shown in this rails guide on segment constraints.

The other method is to use a Constraint class:

Reference the ProfileConstraint class by creating a new directory/file called app/constraints/profile_constraint.rb:

Above, Rails looks for the matches? method in ProfileConstraint sends it a request object, which we then use to decide whether to match the route or not by comparing it against an array of reserved_words.

Another useful way to add on to the above would be to use scope. This allows you to extend your route like /:username/comments:

And now you’ll have routes like so:

Hope someone finds this useful as I did.

Tips for improving:
- Dynamically add model/controller classnames and routes to the reserved_words array.

As you may know, CI 2.0 came with a new core/ folder that allows you to simply drop classes to extend the CI core with.

For example, to extend the base CI_Loader class, you would just drop in MY_Loader.php into the /application/core folder, and all is set and done. Of course, you’d make sure that the ‘subclass_prefix’ config variable is set to ‘MY_’. This is the default configuration.

Being able to just drop in subclasses in the core/ folder is pure awesome, because you don’t need to modify the core CI classes to extend its functionality, and you keep everything separate in each /application instance.

You may think you can just drop in a file called “MY_DB_active_rec.php” into the /application/core folder, but this is not the case. It will not work, as verified by Phil Sturgeon himself in this StackOverflow post.

To do so requires a teeny bit of hacking of the core CI files. If you don’t like the idea of doing so, you may want to just head home now.

Still with me? The good news is that this only requires a few lines of code change. Here we go:

Locate the piece of code in

, starting on line 110 (as of CI 2.0.0):

This is the bit of code that loads CI’s active record class. Replace it with this:

What happens here is that it will check the /application/core/ folder to see if a “MY_DB_active_rec.php” file exists (where MY_ is the prefix name you specified in your config file), and if it does, it loads that instead of the CI_DB_active_record class.

Next you’ll also need to extend the CI_Loader class to override the database() method, as well as the specific database driver that you’ll be using. In my case I extended the CI_DB_mysql_driver to override the _insert() method to allow the “INSERT DELAYED” feature of MySQL.

I’ve included a zip file of the changes. The files below were meant for CodeIgniter 2.0.0. CI 2.0.1+ shouldn’t be much more different, just get into the file and look around to make the necessary adjustments.

Download extend_ci_active_record.zip

If you still want to stick to this method, I would recommend implementing some sort of caching for your minified/concatenated files. Carabiner does this for your automatically, however!

——–
As any good UI developer will tell you, one of the best practices for speeding up your website is to minimize HTTP requests. Since most of the user’s loading time is tied up in things like loading scripts, images, flash, stylesheets, etc., reducing the number of these requests can drastically help improve loading time. It also helps to Gzip the components as well, which we’ll also cover in this tutorial.

This first tutorial will cover how to concatenate and minify your javascript and CSS files into a single HTTP request, using the CodeIgniter framework. For sites that load lots of scripts like jQuery plugins, this can be very beneficial for performance. Additionally, minification of scripts and stylesheets can help reduce the size of files, saving you bandwidth and shortening loading times for user.

So, let’s get started!

NOTE: I am assuming in this tutorial that you are already using an .htaccess file to eliminate index.php from your URIs.

Create an assets directory

You’ll want to manage your static assets (js, css, images, etc) by placing them in a directory called /assets in your web root. Here’s what your CI folder structure should look like:

You may have your application/ folder elsewhere, but for this tutorial we’ll have it in the default location, inside the /system folder.

You’ll also need the below two libraries, which are essential to this tutorial:

Let’s grab copies of the following two libraries:

JSMin-PHP, Ryan Grove’s PHP port of Douglas Crockford’s JSMin.
Joe Scylla’s CssMin

Name these two files JSMin.php and CssMin.php, respectively, and place them in your application/libraries folder.

Create an asset_url() helper function

Having a helper function to access your assets URL can be helpful in the event you decide to rename or change the location of your application. It works like the base_url() function, only it will link to your assets rather than your base URL (obviously). In config.php, add the following code:

We’ll be using css_path and js_path a little later in this tutorial, so keep those in mind.

Next, add this function in /system/helpers/path_helper.php

Add the following to your config/autoload.php file, to helpers:

Now you’re set! You can now call asset_url() anywhere to access your asset URL path. So instead of writing:

You would write instead:

Now that that’s out of the way, let’s get to the good stuff:

Create asset loader helper functions

In order to reduce our HTTP requests for our scripts to a single call, we’ll need a script tag that does the call for all files in one <script>tag. In your application/helpers folder, create a new file called asset_helper.php and insert the following code:

These helpers will be used on pages that you need to load specific JS or CSS files. Usage would be:

You might want to also add this helper to your autoload.php file as well, just like the path helper above. Just add it to the array.

Create a loader controller

In order to actually load our asset files, we’ll need a controller that handles the concatentation and minification of the scripts and files. Create a new file in your application/controllers directory called loader.php with the following code:

And that’s it!

Usage examples:

Javascript:

CSS:

To load files inside a directory, for example, assets/js/plugins/example.js, you would include 'plugins/example' inside your the array as shown above.

If you update your css/js, you can use the option $version parameter. Simply use an incrementing integer value of your choice and the browser will read the file as a new file rather than loading the cached file.

Happy coding!

parameter in the Search API response to use a

. Since our data was returned using JSON, PHP’s native

automatically converts the ID to a floating point value, like

. Not cool.

If you are finding you’re having this problem when using

in general, and you’re running a development version of PHP 5.3+, you can use the bitmask

in your

call to output any bigints as a string.

Example usage:

json_decode($json, false, 512, JSON_BIGINT_AS_STRING);

Anyway Twitter has now added an

field in the search response. So if you’re using PHP and you need to store or output the status ID, you should use this value instead:

{
    from_user_id_str: "52138619"
    profile_image_url: http://a3.twimg.com/profile_images/403904047/BC_color_logo_normal.jpg
    created_at: "Sat, 13 Nov 2010 03:00:56 +0000"
    from_user: "BCSportsNews"
    id_str: "3281128077139968"
    metadata: {
        result_type: "recent"
    }
    to_user_id: null
    text: "MSOC: North Carolina has defeated Boston College, 1-0, to advance to the ACC Championship game."
    id: 3281128077139968
    from_user_id: 52138619
    geo: null
    iso_language_code: "en"
    to_user_id_str: null
    source: "<a href="http://twitter.com/">web</a>"
}

A Daft Punk original to boot.

or a

?

Just add the

tag to it and all will make sense.

echo '<pre>';
print_r($someVar);
echo '</pre>';

Enjoy!