Asked  7 Months ago    Answers:  5   Viewed   37 times

I am currently working on my first laravel project and I am facing a problem.

If you have experience with laravel you probably know that by calling php artisan make:auth you will get a predefined mechanism that handles login and registration.

This mechanism is set to understand a couple of commonly used words in order to automate the whole procedure.

The problem that occurs in my case is that I am using oracle db and it won't let me have a table column with the name of password because its a system keyword and it throws errors when trying to insert a user.

So far, I have tried to change my password column to passwd and it worked in my registration form as expected. The User row was successfully inserted and my page was redirected to /home.



But when I try to logout and then relogin, I get this error telling me that my credentials are not correct:

enter image description here

As for my code, I have changed my RegisterController.php so that it takes username instead of email

protected function validator(array $data)
    return Validator::make($data, [
        'username' => 'required|max:50|unique:ECON_USERS',
        'passwd' => 'required|min:6|confirmed',

protected function create(array $data)
    return User::create([
        'username'   => $data['username'],
        'passwd'     => bcrypt($data['passwd'])

The User $fillable

protected $fillable = [
    'username', 'passwd'

I am guessing that Auth is trying to authenticate with email and not username or that Auth is searching for password and not passwd.



For having username instead of email, you can overwrite username() in your LoginController.php

 * Get the login username to be used by the controller.
 * @return string
public function username()
    return 'username';

And for passwd instead of password, you can do define an accessor in your AppUser.php

 * Get the password for the user.
 * @return string
public function getAuthPassword()
    return $this->passwd;

login.blade.php : Replace email input with username but do not change the name of the input for password.

Wednesday, March 31, 2021
answered 7 Months ago

Recommended approach if you put here only methods (not classes):

  1. Create file anywhere you want
  2. In composer.json make sure you add this file to files key inside autoload like this:

    "autoload": {
        // here other autoload things
        "files": ["app/Helpers/AnythingHelper.php"]
  3. Run composerdump-autoload`

For classes obviously you should use standard PSR-4 autoloading

Wednesday, March 31, 2021
answered 7 Months ago

After re-reading the docs, it is clear that this is intended behaviour. The docs say

As an alternative to mocking, you may use the Event facade's fake method to prevent all event listeners from executing.

As described in a comment, I have to create two tests. One for making sure that the event has been fired and contains the expected data and a second one for making sure that the event listeners get fired.

So, first Test:


$order = factory(Order::class)->make();

event(new PaymentWasCompleted($order));

Event::assertDispatched(PaymentWasCompleted::class, function ($e) use ($order) {
    return $e->order->id === $order->id;

Second test:


$order = factory(Order::class)->make();

event(new PaymentWasCompleted($order));

Queue::assertPushed(GenerateInvoiceJob::class, function ($job) use ($order) {
    return $job->order->id === $order->id;

As expected, this tests pass.

Saturday, May 29, 2021
answered 5 Months ago

Yes, it's possible.

TortoiseSVN and the svn command line client share the same settings location in your profile folder. So you may simply checkout one version using svn.exe:

$ svn co --username different_user_name file:///C:/path/to/your/repo

... and Subversion will happily replace the associated username for that repository. New commits from TortoiseSVN will then always use that username, no matter with what program you make the new checkouts.

The procedure should work with TortoiseSVN 1.5.5. If it doesn't, try emptying svn's authentication cache (%APPDATA%Subversionauthsvn.username) first.

Thursday, August 5, 2021
answered 3 Months ago
  1. Click Window > Preferences > Team > Git > Configuration
  2. Click Add Entry and enter the key value pairs:

    • Key:
    • Value: YourUsernameHere


    • Key:
    • Value: YourEmailHere
Sunday, August 8, 2021
answered 3 Months ago
Only authorized users can answer the question. Please sign in first, or register a free account.
Not the answer you're looking for? Browse other questions tagged :