Book Image

Laravel 5.x Cookbook

By : Terry Matula, Alfred Nutile
Book Image

Laravel 5.x Cookbook

By: Terry Matula, Alfred Nutile

Overview of this book

Laravel is a prominent member of a new generation of web frameworks. It is one of the most popular PHP frameworks and is also free and an open source. Laravel 5 is a substantial upgrade with a lot of new toys, at the same time retaining the features that made Laravel wildly successful. It comes with plenty of architectural as well as design-based changes. The book is a blend of numerous recipes that will give you all the necessary tips you need to build an application. It starts with basic installation and configuration tasks and will get you up-and-running in no time. You will learn to create and customize your PHP app and tweak and re-design your existing apps for better performance. You will learn to implement practical recipes to utilize Laravel’s modular structure, the latest method injection, route caching, and interfacing techniques to create responsive modern-day PHP apps that stand on their own against other apps. Efficient testing and deploying techniques will make you more confident with your Laravel skills as you move ahead with this book. Towards the end of the book, you will understand a number of add-ons and new features essential to finalize your application to make it ready for subscriptions. You will be empowered to get your application out to the world.
Table of Contents (17 chapters)
Laravel 5.x Cookbook
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Troubleshooting your application


In this tip, I am not going to suggest Xdebug or some browser plugin to watch all the methods being called. I am just going to cover some basic things you can do to approach any issue. I will cover a few common troubleshooting situations and how to deal with them.

Getting ready

Not much to do here; feel free to follow along by writing the code that will break, and then we have to fix it.

How to do it…

  1. You go to a page in your browser only to see a breaking site:

    If I did not have debug=true in .env, then I would only see the Whoops message. Keep in mind you do not want to keep this as true on publically accessible sites, because it leaks out possible information about your application that can be a huge security risk. But locally it rocks.

    Also, unlike the preceding message where I just happen to have imported the wrong Response class, it should have been Illuminate\Support\Facades\Response. Sometimes, especially in Views, the message may not be so clear. So, here...