Debug mode in Laravel

Introduction

Debug mode helps you find and fix errors in your Laravel app by showing detailed error messages.

When you are building a new feature and want to see errors clearly.

When something is not working and you need to understand why.

When you want to check the details of exceptions or bugs.

When testing your app locally before making it live.

Syntax

Laravel

APP_DEBUG=true

This is set in the .env file at the root of your Laravel project.

Set APP_DEBUG=false in production to hide error details from users.

Examples

This shows detailed error messages in your browser.

Laravel

# Enable debug mode
APP_DEBUG=true

This hides error details and shows a generic error page instead.

Laravel

# Disable debug mode
APP_DEBUG=false

Sample Program

This route causes a division by zero error. If APP_DEBUG=true, Laravel shows a detailed error page. If false, it shows a simple error message.

Laravel

<?php

// routes/web.php
use Illuminate\Support\Facades\Route;

Route::get('/debug-example', function () {
    // This will cause an error if debug mode is on
    return 1 / 0;
});

Important Notes

Always turn off debug mode (APP_DEBUG=false) on live sites to protect sensitive info.

After changing APP_DEBUG, clear config cache with php artisan config:clear to apply changes.

Summary

Debug mode shows detailed error info to help fix bugs.

Set APP_DEBUG=true in .env to enable it.

Turn it off in production for security by setting APP_DEBUG=false.

Practice

1. What does setting APP_DEBUG=true in Laravel's .env file do?

easy

A. Shows detailed error messages to help find bugs

B. Disables all error messages

C. Automatically fixes bugs in the code

D. Prevents the application from running

Solution

1. Step 1: Understand the purpose of APP_DEBUG

   APP_DEBUG controls whether Laravel shows detailed error messages or not.

2. Step 2: Effect of setting APP_DEBUG=true

   When true, Laravel shows detailed error info to help developers find and fix bugs.

3. Final Answer:

   Shows detailed error messages to help find bugs -> Option A

4. Quick Check:

   APP_DEBUG=true means detailed errors shown [OK]

Hint: True means show errors, false hides them [OK]

Common Mistakes:

• Thinking it fixes bugs automatically
• Believing it disables errors
• Confusing it with app running status

2. Which of the following is the correct way to enable debug mode in Laravel?

easy

A. Set APP_DEBUG=false in .env

B. Set APP_DEBUG=true in .env

C. Add debug_mode=on in config/app.php

D. Run php artisan debug:on in terminal

Solution

1. Step 1: Locate where debug mode is set

   Laravel uses the .env file to set environment variables like APP_DEBUG.

2. Step 2: Correct value to enable debug

   Setting APP_DEBUG=true enables debug mode; false disables it.

3. Final Answer:

   Set APP_DEBUG=true in .env -> Option B

4. Quick Check:

   Enable debug by APP_DEBUG=true [OK]

Hint: Enable debug by setting APP_DEBUG=true in .env [OK]

Common Mistakes:

• Setting APP_DEBUG=false to enable debug
• Trying to enable debug in config/app.php
• Using artisan commands that don't exist

3. Given the following .env setting:
APP_DEBUG=false
What will Laravel show when an error occurs?

medium

A. A detailed error page with stack trace

B. The application will crash without any message

C. A simple generic error page without details

D. Laravel will automatically fix the error

Solution

1. Step 1: Check APP_DEBUG value

   APP_DEBUG is set to false, which disables detailed error messages.

2. Step 2: Laravel's behavior with APP_DEBUG=false

   Laravel shows a simple generic error page to avoid exposing sensitive info.

3. Final Answer:

   A simple generic error page without details -> Option C

4. Quick Check:

   APP_DEBUG=false means generic error page [OK]

Hint: False hides details, shows simple error page [OK]

Common Mistakes:

• Expecting detailed errors with APP_DEBUG=false
• Thinking app crashes silently
• Assuming Laravel fixes errors automatically

4. You set APP_DEBUG=true in your .env file but still see a generic error page. What is the most likely cause?

medium

A. You forgot to clear the config cache after changing .env

B. Laravel does not support debug mode

C. APP_DEBUG=true disables error messages

D. Your PHP version is too old

Solution

1. Step 1: Understand config caching in Laravel

   Laravel caches config settings for performance; changes in .env need cache cleared.

2. Step 2: Effect of not clearing cache

   If cache is not cleared, Laravel uses old settings ignoring new APP_DEBUG=true.

3. Final Answer:

   You forgot to clear the config cache after changing .env -> Option A

4. Quick Check:

   Clear config cache to apply .env changes [OK]

Hint: Run php artisan config:clear after .env changes [OK]

Common Mistakes:

• Thinking Laravel lacks debug mode
• Believing APP_DEBUG=true hides errors
• Blaming PHP version without checking

5. You want to safely deploy your Laravel app to production. Which setting for APP_DEBUG should you use and why?

hard

A. APP_DEBUG=true to see errors and fix bugs quickly

B. APP_DEBUG=false to enable automatic bug fixes

C. APP_DEBUG=true to improve app speed

D. APP_DEBUG=false to hide error details from users

Solution

1. Step 1: Understand production environment needs

   In production, showing detailed errors can expose sensitive info to users.

2. Step 2: Choose correct APP_DEBUG setting

   Setting APP_DEBUG=false hides error details, improving security and user experience.

3. Final Answer:

   APP_DEBUG=false to hide error details from users -> Option D

4. Quick Check:

   Production uses APP_DEBUG=false for security [OK]

Hint: Turn off debug in production for security [OK]

Common Mistakes:

• Leaving debug on in production
• Thinking debug improves speed
• Expecting automatic bug fixes