Evolved version of Laravel – Laravel 4.1

Evolved version of Laravel – Laravel 4.1

Laravel – Sub-version… 4.1

It is very important for a developer to stay updated and upgraded. For the same purpose, Mr. Otwell and his team always kept the evolution component in Laravel Framework which led to sub-versions of Laravel that are Laravel 4.1 and Laravel 4.2 with some updates and upgrades…

Some of the functional changes that Laravel 4.1 had are:

1. SSH Component –  A new SSH component was instigated with the release of Laravel 4.1 which allows developers  to easily SSH into remote servers and run a command
2. Boris In Tinker – The “PHP artisan tinker” command in Laravel 4.1 utilizes the Boris REPL if the current system supports it. The deadline and pcntl PHP extensions must be installed to use this feature, and if not then Laravel 4.0 shell can be used.
3. Improvements in Eloquent – A new has many through the relationship was added to Eloquent in Laravel 4.1
4. Read and Write improvements in Database – Through the database layer, eloquent and query builder, an automated read and write connection was available in Laravel 4.1
5. Failed Queue Job Handling – An automated handling of failed jobs was available on the Queue facility in Laravel 4.1
6. Queue priority – Bypassing a comma-delimited list, Queue priority was supported in Laravel 4.1
7. Cache tags – Cache was superseded by tags. Cache tags allow you to assign multiple “tags” to a cache item and flush all items assigned to a single tag in Laravel 4.1
8. Flexible Password Reminders – The password reminder engine has been changed to provide greater developer flexibility when validating passwords and flashing status messages to the session in Laravel 4.1
9. Improved Routing Engine – Laravel 4.1 was a fully written routing layer. In Laravel 4.1, registering routes has become speedier in comparison to Laravel 4
10. Improved Session Engine – A new session engine was introduced in Laravel 4.1 which was more lean and fast.
11. Doctrine DBAL – In order to use the rename Column function in migrations, the developer was supposed to add the doctrine/dbal dependency to the JSON file in Laravel 4.1