When you want to check a Hashed value generated by `Hash::make()` you need to use `Hash::check('unhashed', $hashed)`.
Every time you run `Hash::make('string')`, a different hash is made and will not match the previous one.
Sometimes the compiled file could get corrupted and not function properly, breaking your Laravel installation. This is a list of steps you could use trying to fix a Laravel installation that previously worked just fine on a server.
I have added a sitemap to this very site and was thinking that some of you want to do the same for SEO purposes. The way to add a sitemap would be pretty easy by using a Blade template for the XML that sitemap requires but there is an easier solution. You can use a package from https://github.com/RoumenDamianoff/laravel4-sitemap that would make it super simple to generate a sitemap for your Laravel application. See for yourself.
This trick is what we use to make writing controllers very quick and easy. The base controller has methods plugged in where needed to automatically load views to a set of templates on it's own. All you need to do is pass it the data you want displayed. It also handles missingmethod to automatically look for logical views. Let me know what you think or any ideas for improving upon it. As a note, I use a separate controller to set the page title and menu items.
When creating JS heavy apps some times you need to simulate a network delay so you can see how things are working as it's loading. This simple trick will do just that.
I spent a good hour trying to figure out why my Eloquent relationship wasn't working when I found out it was because of the difference between `$model->relationship->value` and `$model->relationship()->value`.
This is a laravel command i wrote to handle the upgrade to 4.1 It covers everything in the upgrade doc except for handling missing method. It should be easily addable if you need it.
Make sure to add the following to start/artisan.php
Artisan::add(new UpgradeCommand);
Artisan::resolve('UpgradeCommand');
Once finished, run the following
php artisan auth:reminders-controller
If you're like me, you don't like to keep repetitive ->where()'s in your routes file, this is where route patterns come in handy. Makes your routes file DRY too, especially when you'll need to change some expression.
An example of how I did my filters.php and routes.php to populate many of the same structured routes.
Used Sentry 2 for Authentication and short syntax for array()
Suggestions to make it even DRYer are welcome.
php artisan route output of the example http://paste.laravel.com/1cnE