Debug mode in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

🔧 Debug

intermediate

What error message appears when debug mode is off and an exception occurs?

In Laravel, if APP_DEBUG is set to false in the .env file, what will the user see when an exception happens?

A The application crashes with a blank white screen

B A detailed stack trace with error message and code lines

C The raw exception message printed on the screen

D A generic error page with a simple message like 'Whoops, something went wrong.'

💡 Hint

Think about what Laravel shows to protect sensitive info when debug is off.

When APP_DEBUG=false, Laravel shows a generic error page to avoid exposing sensitive details. The detailed stack trace only appears when debug is on.

🔧 Debug

intermediate

Which .env setting enables detailed error messages in Laravel?

To see detailed error messages and stack traces during development, which setting in the .env file must be set?

A APP_DEBUG=true

B APP_ENV=production

C APP_LOG_LEVEL=error

D APP_DEBUG=false

💡 Hint

This setting controls whether Laravel shows detailed errors or not.

Setting APP_DEBUG=true enables detailed error messages and stack traces in Laravel, useful for development.

❓ component_behavior

advanced

What happens if you set APP_DEBUG=true in production?

If you accidentally set APP_DEBUG=true on a live Laravel site, what is the likely outcome when an error occurs?

A The application crashes and stops responding

B Users see detailed error info including file paths and code, risking security

C Errors are logged silently without showing anything to users

D The site automatically disables debug mode for security

💡 Hint

Think about what detailed error info might reveal to outsiders.

Enabling debug mode in production exposes sensitive information like file paths and code, which can be a security risk.

📝 Syntax

advanced

Which code snippet correctly reads the debug mode setting in Laravel?

Which of the following PHP code snippets correctly checks if debug mode is enabled in Laravel?

A if (config('app.debug')) { /* debug is on */ }

B if (env('APP_DEBUG') == true) { /* debug is on */ }

C if (app()->debug) { /* debug is on */ }

D if (getenv('APP_DEBUG') === 'true') { /* debug is on */ }

💡 Hint

Laravel recommends using the config helper for settings.

The config('app.debug') call reads the debug setting properly. Using env() directly is discouraged outside config files.

❓ state_output

expert

What is the output of this Laravel error page when APP_DEBUG=false?

Given the following Laravel error page snippet, what will the user see if APP_DEBUG=false?

Exception: Division by zero in Calculator.php line 42

Stack trace:
#0 ...

A The full exception message and stack trace as shown

B A blank page with no content

C A simple error page with message 'Whoops, something went wrong.' without details

D A JSON response with error details

💡 Hint

Remember what Laravel hides when debug is off.

When APP_DEBUG=false, Laravel hides exception details and shows a generic error page to users.

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