Fetching contributors…
Cannot retrieve contributors at this time
335 lines (204 sloc) 13.3 KB

Laravel 4 Friendly URL

Easy creation of slugs for your Eloquent models in Laravel 4.

Background: What is a slug?

A slug is a simplified version of a string, typically URL-friendly. The act of "slugging" a string usually involves converting it to one case, and removing any non-URL-friendly characters (spaces, accented letters, ampersands, etc.). The resulting string can then be used as an indentifier for a particular resource.

For example, I have a blog with posts. I could refer to each post via the ID:

... but that's not particularly friendly (especially for SEO). You probably would prefer to use the post's title in the URL, but that becomes a problem if your post is titled "My Dinner With André & François", because this is pretty ugly too:

The solution is to create a slug for the title and use that instead. You might want to use Laravel's built-in Str::slug() method to convert that title into something friendlier:

A URL like that will make users happier (readable, easier to type, etc.).

For more information, you might want to read this description on Wikipedia.

Slugs tend to be unique as well. So if I wrote another post with the same title, I'd want to distinguish between them somehow, typically with an incremental counter added to the end of the slug:

This keeps URLs unique.

The Eloquent-Sluggable package for Laravel 4 will handle all of this for you automatically, with minimal configuration at the start.

Installation and Requirements

First, you'll need to add the package to the require attribute of your composer.json file:

    "require": {
        "expstudio/friendlyurl": "dev-master"

NOTE: Eloquent-Sluggable now uses traits, so you will need to be running PHP 5.4 or higher. If you are still using 5.3, then use the "1.*" version and follow the instructions in that version's file.

Aftwards, run composer update from your command line.

Then, update app/config/app.php by adding an entry for the service provider.

	'providers' => array(

		// ...



Finally, from the command line again, run php artisan config:publish expstudio/friendlyurl to publish the default configuration file.

Updating your Eloquent Models

Your models should implement Sluggable's interface and use it's trait. You should also define a protected property $sluggable with any model-specific configurations (see Configuration below for details):

use Expstudio\FriendlyUrl\SluggableInterface;
use Expstudio\FriendlyUrl\SluggableTrait;

class Post extends Eloquent implements SluggableInterface

	use SluggableTrait;

	protected $sluggable = array(
		'build_from' => 'title',
		'save_to'    => 'slug',


Of course, your database will need a column in which to store the slug. You can do this manually, or use the built-in artisan command to create a migration for you. For example:

php artisan sluggable:table posts

Running that command will create a migration that adds a column named "slug" to your posts table. If you want to use a different name for the slug column, you can provide that as a second argument:

php artisan sluggable:table posts slug_column

Be sure to set your model's save_to configuration to match the column name.

That's it ... your model is now "sluggable"!

Using the Class

Saving a model is easy:

$post = new Post(array(
	'title' => 'My Awesome Blog Post'


And so is retrieving the slug:

echo $post->slug;

// or, if you don't know the name of the slug attribute:
echo $post->getSlug();

See the file for using Eloquent-Sluggable with Ardent.

Also note that if you are replicating your models using Eloquent's replicate() method, then you will need to explicity tell the package to force a re-slugging of the model afterwards to ensure uniqueness:

$new_post = $post->replicate()->resluggify();


Configuration was designed to be as flexible as possible. You can set up defaults for all of your Eloquent models, and then override those settings for individual models.

By default, global configuration can be set in the app/config/packages/expstudio/friendlyurl/config.php file. If a configuration isn't set, then the package defaults from vendor/expstudio/friendlyurl/src/config/config.php are used. Here is an example configuration, with all the default settings shown:

return array(
	'build_from'      => null,
	'save_to'         => 'slug',
	'max_length'      => null,
	'method'          => null,
	'separator'       => '-',
	'unique'          => true,
	'include_trashed' => false,
	'on_update'       => false,
	'reserved'        => null,
	'use_cache'       => false,


This is the field or array of fields from which to build the slug. Each $model->field is contactenated (with space separation) to build the sluggable string. This can be model attribues (i.e. fields in the database) or custom getters. So, for example, this works:

class Person extends Eloquent implements SluggableInterface {

	use SluggableTrait;

	public static $sluggable = array(
		'build_from' => 'fullname'

	public function getFullnameAttribute() {
		return $this->firstname . ' ' . $this->lastname;


If build_from is empty, false or null, then the value of $model->__toString() is used.


The attribute field in your model where the slug is stored. By default, this is "slug". You need to create this column in your table when defining your schema:

Schema::create('posts', function($table)


Setting this to a positive integer will ensure that your generated slugs are restricted to a maximum length (e.g. to ensure that they fit within your databse fields). By default, this value is null and no limit is enforced.

Note: If unique is enabled (which it is by default), and you anticipate having several models with the same slug, then you should set this value to a few characters less than the length of your database field. The reason why is that the class will append "-1", "-2", "-3", etc., to subsequent models in order to maintain uniqueness. These incremental extensions aren't included in part of the max_length calculation.


Defines the method used to turn the sluggable string into a slug. There are three possible options for this configuration:

  1. When method is null (the default setting), the package uses modified Laravel's Str::slug() method to create the slug.

  2. When method is a callable, then that function or class method is used. The function/method should expect two parameters: the string to process, and a separator string. For example, to duplicate the default behaviour, you could do:

    	'method' => array('Illuminate\\Support\\Str', 'slug'),
  3. You can also define method as a closure (again, expecting two parameters):

    	'method' => function( $string, $separator ) {
    		return strtolower( preg_replace('/[^a-z]+/i', $separator, $string) );

Any other values for method will throw an exception.

For more complex slugging requirements, see Extending Sluggable below.


This defines the separator used when building a slug, and is passed to the method defined above. The default value is a hyphen.


This is a boolean defining whether slugs should be unique among all models of the given type. For example, if you have two blog posts and both are called "My Blog Post", then they will both sluggify to "my-blog-post" (when using Sluggable's default settings). This could be a problem, e.g. if you use the slug in URLs.

By turning unique on, then the second Post model will sluggify to "my-blog-post-1". If there is a third post with the same title, it will sluggify to "my-blog-post-2" and so on. Each subsequent model will get an incremental value appended to the end of the slug, ensuring uniqueness.


Setting this to true will also check deleted models when trying to enforce uniqueness. This only affects Eloquent models that are using the softDelete feature. Default is false, so soft-deleted models don't count when checking for uniqueness.


A boolean. If it is false (the default value), then slugs will not be updated if a model is resaved (e.g. if you change the title of your blog post, the slug will remain the same) or the slug value has already been set. You can set it to true (or manually change the $model->slug value in your own code) if you want to override this behaviour.

(If you want to manually set the slug value using your model's Sluggable settings, you can run $model->resluggify() to force Sluggable to update the slug field.)


An array of values that will never be allowed as slugs, e.g. to prevent collisions with existing routes or controller methods, etc.. This can be an array, or a closure that returns an array. Defaults to null: no reserved slug names.


When checking for uniqueness, the package will query the database for any existing models with the same or similar slugs, and then see if an increment is required. This means more DB usage, and could also lead to a race condition if you are saving a lot of models at the same time.

Turning on use_cache will store the last generated increment using Laravel's cache so that your app can save those database requests.

The default value is false: don't use caching. If you are already using a cache system that supports the Cache::tags() feature (i.e. anything except database and file caches), then you should really enable this setting. Change it to a positive integer, which equals the number of minutes to store slug information in the cache.

(If for whatever reason you want to clear out all of Sluggable's cache entries, then just run Cache::tags('sluggable')->flush().)

Extending Sluggable

Sometimes the configuration options aren't sufficient for complex needs (e.g. maybe the uniqueness test needs to take other attributes into account, or maybe you need to make two slugs for the same model).

In instances like these, your best bet is to overload some of SluggableTrait's methods with your own functions, either on a per-model basis, or in your own trait that extends SluggableTrait. Each step of the slugging process is broken out into it's own method, and those are called in turn when the slug is generated.

Take a look at SluggableTrait->sluggify() to see the order of operations, but you might consider overloading any of the following protected methods:


Determines if the model needs to be slugged. Should return a boolean.


Returns a string that forms the source of the slug (usually based on the build_from configuration value).


The actual slugging code. Usually implements whatever is defined in the method configuration, but could call out to other slugging libraries. Takes the source string (above) and returns a string.


Validates that the generated slug is valid, usually by checking it against anything defined in the reserved configuration. Should return a valid slug string.


Checks to see if the given slug is unique. Should return a unique slug string.


Writes the (generated, valid, and unique) slug to the model's attributes.

Bugs, Suggestions and Contributions

Please use Github for bugs, comments, suggestions.

  1. Fork the project.
  2. Create your bugfix/feature branch and write your (well-commented) code.
  3. Create unit tests for your code:
    • Run composer install --dev in the root directory to install required testing packages.
    • Add your test methods to eloquent-sluggable/tests/SluggableTest.php.
    • Run vendor/bin/phpunit to the new (and all previous) tests and make sure everything passes.
  4. Commit your changes (and your tests) and push to your branch.
  5. Create a new pull request against the eloquent-sluggable develop branch.

Please note that you must create your pull request against the develop branch.

Copyright and License

Laravel4 Friendly Url was modify from Eloquent-Sluggable by Watee Wichiennit and released under the MIT License. See the LICENSE file for details.

Copyright 2014 Watee Wichiennit