Registration flow in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a registration route in Laravel.

Laravel

Route::[1]('/register', [RegisterController::class, 'showRegistrationForm']);

Drag options to blanks, or click blank then click option'

Apost

Bput

Cget

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using POST instead of GET to show the form.

Using PUT or DELETE which are for updating or deleting data.

The registration form is shown using a GET request, so the route method should be get.

2fill in blank

medium

Complete the code to handle the registration form submission.

Laravel

Route::[1]('/register', [RegisterController::class, 'register']);

Drag options to blanks, or click blank then click option'

Apost

Bpatch

Cdelete

Dget

Attempts:

3 left

💡 Hint

Common Mistakes

Using GET instead of POST for form submission.

Using PATCH or DELETE which are for updates or deletions.

Form submissions that create new data use the POST method, so the route should be post.

3fill in blank

hard

Fix the error in the validation rules for the registration form.

Laravel

$request->validate([ 'email' => 'required|email|unique:users,[1]' ]);

Drag options to blanks, or click blank then click option'

Aemail

Busername

Cpassword

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'username' or 'password' instead of 'email' in the unique rule.

Using 'id' which is not the email column.

The unique rule needs the column name to check uniqueness. For emails, it should be email.

4fill in blank

hard

Fill both blanks to hash the password and save the user.

Laravel

$user = new User();
$user->email = $request->email;
$user->password = [1]($request->password);
$user->[2]();

Drag options to blanks, or click blank then click option'

AHash::make

Bbcrypt

Csave

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using bcrypt directly without the Hash facade.

Using create() on an instance instead of save().

Passwords should be hashed using Hash::make. To save the user, call save() on the model instance.

5fill in blank

hard

Fill all three blanks to redirect the user after registration with a success message.

Laravel

return redirect()->[1]('home')->with('[2]', '[3]');

Drag options to blanks, or click blank then click option'

Aroute

Bhome

Csuccess

DYou have registered successfully!

Attempts:

3 left

💡 Hint

Common Mistakes

Using redirect()->home() instead of route('home').

Passing the message as the key instead of the value.

After registration, redirect to a named route using route(). Use with() to flash a success message.

Practice

1. What is the main purpose of the registration flow in a Laravel application?

easy

A. To collect and save new user information securely

B. To display user profiles

C. To delete user accounts

D. To update existing user passwords

Solution

1. Step 1: Understand registration flow purpose

   The registration flow is designed to gather new user data and store it safely.

2. Step 2: Compare options with purpose

   Only To collect and save new user information securely matches the goal of collecting and saving new user info securely.

3. Final Answer:

   To collect and save new user information securely -> Option A

4. Quick Check:

   Registration flow = Collect and save user info [OK]

Hint: Registration means new user data collection and storage [OK]

Common Mistakes:

• Confusing registration with profile display
• Thinking registration deletes users
• Mixing registration with password update

2. Which Laravel method is used to securely hash a user's password during registration?

easy

A. Hash::make()

B. User::hashPassword()

C. bcrypt_password()

D. password_hash()

Solution

1. Step 1: Identify Laravel's password hashing method

   Laravel uses the Hash facade with the make() method to hash passwords securely.

2. Step 2: Verify options

   Only Hash::make() is the correct Laravel method; others are incorrect or not Laravel-specific.

3. Final Answer:

   Hash::make() -> Option A

4. Quick Check:

   Laravel password hashing = Hash::make() [OK]

Hint: Use Hash::make() to hash passwords in Laravel [OK]

Common Mistakes:

• Using non-Laravel functions for hashing
• Calling methods that don't exist in Laravel
• Confusing bcrypt_password() with Laravel's method

3. Given this Laravel controller code snippet for registration:

public function register(Request $request) {
  $validated = $request->validate([
    'email' => 'required|email|unique:users',
    'password' => 'required|min:8'
  ]);
  User::create([
    'email' => $validated['email'],
    'password' => Hash::make($validated['password'])
  ]);
  return redirect('/welcome');
}

What happens if the email already exists in the users table?

medium

A. The user is created with duplicate email

B. Validation fails and an error message is shown

C. The password is hashed twice

D. The app crashes with a database error

Solution

1. Step 1: Understand validation rules

   The 'unique:users' rule prevents duplicate emails by validating against the users table.

2. Step 2: Effect of validation failure

   If the email exists, validation fails and Laravel automatically returns an error message to the user.

3. Final Answer:

   Validation fails and an error message is shown -> Option B

4. Quick Check:

   Unique email validation = error on duplicate [OK]

Hint: unique:users stops duplicate emails during validation [OK]

Common Mistakes:

• Assuming duplicate users are created
• Thinking password hashes twice
• Expecting a crash instead of validation error

4. Identify the error in this Laravel registration code:

public function register(Request $request) {
  $data = $request->validate([
    'email' => 'required|email',
    'password' => 'required|min:8'
  ]);
  User::create([
    'email' => $data['email'],
    'password' => $data['password']
  ]);
  return redirect('/home');
}

medium

A. Validation rules are incorrect

B. Redirect URL is invalid

C. Missing password hashing before saving

D. Request object is not injected

Solution

1. Step 1: Check password handling

   The password is saved directly without hashing, which is insecure and incorrect.

2. Step 2: Confirm validation and redirect

   Validation rules and redirect URL are valid; request injection is correct.

3. Final Answer:

   Missing password hashing before saving -> Option C

4. Quick Check:

   Password must be hashed before saving [OK]

Hint: Always hash passwords before saving to database [OK]

Common Mistakes:

• Saving plain text passwords
• Ignoring validation rules
• Incorrect redirect paths

5. You want to customize the Laravel registration flow to send a welcome email after successful registration. Which is the best way to implement this?

hard

A. Add email sending code directly after User::create() in the controller

B. Override the User model's save() method to send email

C. Send the email from the registration form view

D. Use Laravel events to listen for user registration and send email

Solution

1. Step 1: Understand Laravel best practices

   Using events decouples email sending from registration logic, improving maintainability.

2. Step 2: Evaluate options

   Directly sending email in the controller mixes concerns; overriding the User model's save() method is risky; sending the email from the registration form view breaks MVC pattern.

3. Final Answer:

   Use Laravel events to listen for user registration and send email -> Option D

4. Quick Check:

   Events handle post-registration tasks cleanly [OK]

Hint: Use events for post-registration actions like emails [OK]

Common Mistakes:

• Mixing email logic in controller
• Modifying model save() for side effects
• Placing logic in views