Adam Wathan has released a package for outputting SVG’s on your site. It looks nice and might become a standard include in my projects.

Go read more at the Laravel News post.

Laravel password reset caused double password hashing

I recently updated a little weekend project of mine to Laravel 5.2 and started using the re-implemented authentication stuff.
What I hadn’t implemented, or activated, on the site was password resets. Now password resets is sometimes a feature I myself sometimes use a lot, for different reasons and in this particular case I discovered a problem.

Now, when you have a register/login system on your website the passwords should be encrypted, hashed, and so on. How and when this is done is specific to you and your system, one smooth place to add it is on the setPassword method of your User model. This ensures that whenever the password is written to the database it hashed, right.
But here is where the “problem” arose when I activated the password-reset of Laravel (how have I not stumbled on this before?). So when you reset a password out-of-the-box, you get an email with a link -> go to reset page -> post new password -> password gets saved -> you are logged in. Nothing out of the ordinary.

The password gets hashed in the ResetPasswords trait before it is saved, which is all good except if you hash it in the setPassword method. Because now it gets hashed twice and when you try to login you’ll get an error because the passwords will not match. Well luckily there is a simple fix.
In your PasswordController, inside App\Http\Controllers\Auth, add your custom resetPassword method which will override the traits one.

For example:

protected function resetPassword($user, $password)
    $user->password = $password;



If you don’t do your hashing on the User models setPassword method your probably fine. Maybe doing it there is a weird place?
Let me know what you think.

Socialite providers

Providers for Laravel Socialite

A few weeks ago a write an article on how to get started with Laravels Socialite (swedish).
If you are using Socialite you might feel it is a bit light, with just Facebook, Github, Twitter and so on. Fortunately there are awesome people making these kinds of packages just so much better and more useful.

Without further ado, I give you Socialite Providers by DraperStudios. Socialite Providers give you 70+, as of writing,  additional providers for Socialite.

Adding Eloquent to Themosis (wordpress)

At my current job, @NetRelations, I was hired as a PHP/Wordpress developer (and front end dev). So naturally I do WordPress stuff, but working with WP can sometimes feel… Well *sigh*, because of the way the code in the popular, fantastic cms. That is why things like Themosis are so fantastic.

As a fan, user, supporter and Artisan of the great PHP-framewoerk Laravel , Themosis is like a warm, cozy blanket over WordPress! And we are purely talking code now, not the application it self. Themosis implements many features and ideas from Laravel, modern PHP and staying true to everything WordPress.
But this is not an intro to Themosis, this post is about getting more Laravel magic to your WordPress/Themosis setup.

Because yes, there are some things “missing” if you will. At least of your used to building sites and apps with Laravel. So lets get to it and implementing support for using Eloquent.

First we need to add Eloquent to our composer.json file in our root folder. So open your terminal and in your root run.

composer require illuminate/database

You should now see it in your composer file in the “require” object. Now comes the part which I’m not really sure what is the best way or best place to put it. That is loading of Eloquent and handing your database settings to it. I chose to put inside environments config files, so for my local installation I put the following code in side “config/environments/local.php”.

use Illuminate\Database\Capsule\Manager as Capsule;

$capsule = new Capsule;

    'driver'    => 'mysql',
    'host'      => getenv('DB_HOST'),
    'database'  => getenv('DB_NAME'),
    'username'  => getenv('DB_USER'),
    'password'  => getenv('DB_PASSWORD'),
    'charset'   => 'utf8',
    'collation' => 'utf8_unicode_ci',
    'prefix'    => ''


What are the getenv() things in that code. Well if you use Themosis or open the file I mentioned, you will see that they are used for the WordPress database settings. So you can just reuse those code parts.
One little disclaimer here right up front. You cannot remove the WP db-settings, as far as I know because WordPress needs a its database connection.

We have Eloquent added, installed and booted – now what?

Now we can just create our models and make them extend Eloquent, like this.

use Illuminate\Database\Eloquent\Model as Eloquent;

class PostModel extends Eloquent{

	protected $table = 'wp_posts';
	protected $primaryKey = 'ID';


Then in your controller you could do something like

public function allPosts(){
  $allposts = PostModel::all();

  return $allposts;

Not the most beautiful code but you get the gist.

So yeah that was basically it for adding Eloquent to your Themosis based WordPress installation! 🙂
But wait, just one more thing 😉

This last tip is something I’m going to try to make time to make a pull request for and implemented into Themosis.
So what I wanted when I added Eloquent to my project was to use the relationship features of it. At first I didn’t really get them to work as Eloquent (or what not) couldn’t figure what model I was referencing. But after a few minutes I figured I’d try something that I had tried earlier for another reason but failed. You see to be able to use your controllers and models in Themosis you have to ad them to an config file which in turn loads them in your app. Easy enough but a bit cumbersome, *cough* when your used to autoloading a la PSR4 *cough*.

Said and done, opened my composer.json and added a PSR-4 section to the autoload object and pointed it to my “theme/app” folder, like so.

“autoload”: {
“psr-0”: {
“Thms”: “library”
“psr-4”: {
“MyTheme\\”: “htdocs/content/themes/my-theme/app”

Now you just need to add a namespace declaration to your models, and use the complete path when adding a relation.

<?php namespace MyTheme\models
use Illuminate\Database\Eloquent\Model as Eloquent;

class PostModel extends Eloquent{

	protected $table = 'wp_posts';
	protected $primaryKey = 'ID';

   public function tags() {
   /* Given that the related models name is TagModel */
      return $this->hasMany('MyTheme\Models\TagModel');


As simple as that, don’t you think. And as a bonus, you don’t need to define your models in the “loading.config.php” file anymore as they are autoloaded. at least I don’t think you do, works for me so far.
Same should apply for your controllers, just don’t forget to put in the namespace declaration and “use” the files you, well use inside your class!

That is all for now. Comments, suggestions and improvements on the above is welcome.

Read more about EloquentThemosis

Get started with Laravel 4

This first part is less about Laravel and more about Git and Composer. We will set up our local Laravel installation och push it to Github.

This post-series is written in Swedish and you can find it by clicking the link to the right –> [with the Swedish flag]


Update: Dec 2014

As this post get tweeeted out, I feelI should say that it is an old article (series) I started summer 2013, but never got finished.
I am planning on a new Laravel 5 series, also in swedish, during January. So come back soon 🙂

Laravel PHP Framework

coming up: A small Laravel tutorial

Yes, here we go. I am going to embark on my first ever tutorial (series) adventure, and it will be on the great Laravel PHP framework.
Now a few things I want to note: first of I have never done this before, so it will be a learning experience for myself. I’m hoping to get some of you interested in Laravel and at the same time deepen my own knowledge in the framework. Very egoistic right 😉

Second, it will be in swedish. Oooooh please don’t cry, there is a reason for it.
Even though most of this site will be in english, from time to time I will make some swedish elements. Reason being, there is so much stuff out there for you english speakers already. Swedish people are generally very good at english, but some do prefer to get their info in their “mother tongue”.

I’m working on the first, and second, part at the moment and it will hopefully be out this week, but the swedish midsummer holiday is on friday so will have to see. I might end up just barbecuing and having some beers.

STAY tuned…