Laravel
Laravel 4: Be Careful With Your After Filters
Learn how to use the after filter in Laravel 4 to perform tasks after your routes and controllers have run. This filter can be used for various purposes, such as logging or checking specific conditions. By using the after filter, you can manipulate the response content before it is sent to the client. However, if you are working with views and want to avoid potential issues with nested queries being executed twice, it is recommended to use the getContent() function instead of casting the view object to a string.
Laravel 4: Working With Checkboxes and Input
Learn how to create a checkbox in a Blade view using the Form class in Laravel. You can check if a checkbox is checked in a controller by using an if statement. Ensure the checked state of the checkbox is set by passing a boolean value as the third argument in the checkbox function. You can also use Input::old() to set the checked state based on the previous input.
Laravel: Calling Artisan Commands From Your Application
Learn how to run Artisan commands from within your application's code with this helpful tip. You can use the Artisan::call method to execute commands, and even pass command options as arguments. Keep in mind that when calling commands from your application, the paths are relative to the location of the calling file. You can simplify path management by using Laravel's path helper functions.
Laravel 4: Default Events
Laravel 4 provides a variety of events that are fired throughout your application's life cycle, such as auth.attempt, auth.login, auth.logout, and more. These events are called in specific files like /Illuminate/Auth/Guard.php and /Illuminate/Database/Connection.php. You can find where an event is called or explore available events in this quick reference. Keep an eye on this page for updates and additional event information.
Laravel 4: Getting User Input
Learn how to get input from users in Laravel 4 using the Input facade. Find out how to get the value of a specific input element by name, and how to specify a default value if the input is empty. Additionally, discover how to get all of the input values as an associative array using the all() method. Learn how to handle ambiguous input when there are variables with the same name in both a POST request and a URL query parameter. Finally, see how to specify the source of the data you want using the instance() method and access the POST and query data directly.
Laravel 4: Rendering a View to a String
Laravel 4 provides a way to separate controllers and business logic from the presentation layer through its Views feature. Instead of outputting a view directly to the client, you can render it into a local variable. This is especially useful when you need to further process the view as a string, such as generating a PDF of the web page. Laravel 4's View::make()->render() method allows you to accomplish this.
Getting the Environment Name in Laravel 4
Learn how to use environments in Laravel 4 to develop your application in a way that responds to its running environment. Environments allow for automatic changes to database servers and cache drivers. Check the current environment in your code using the App::environment() method and perform different actions based on the result.
Latest posts
A Forte development update: the parser now supports backtracking, improvements to node metadata, ide...
Read moreWrapping up attribute parsing in Forte's HTML parser, from simple HTML attributes to complex, edge-c...
Read moreExploring how Forte's parser extensions can be used to handle complex Blade directives like nested s...
Read moreDigging into parsing Blade and HTML comments while building Forte's HTML parser for Laravel Blade.
Read moreThis week I’m tackling Forte's HTML parser - consolidating Blade, Flux, and Livewire components into...
Read moreRecapping Laracon in Denver with the Statamic team, this post introduces Forte - a new Blade extensi...
Read more