Nakov

@siewlon6093

Is your route auth protected?

If it is not then it means that $request->user() is equal to null hence the error.

@siewlon6093

Is your route auth protected?

If it is not then it means that $request->user() is equal to null hence the error.

You should use use instead of with to pass a variable to a closure.

->editColumn('id', function ($storageSpace) use ($colorsCollection){

If it is just a view without a controller, you can use it like this:

Route::view('legals/cookie', 'legals.cookie');

https://laravel.com/docs/master/routing#view-routes

If it is just a view without a controller, you can use it like this:

Route::view('legals/cookie', 'legals.cookie');

https://laravel.com/docs/master/routing#view-routes

Here is the documentation: https://laravel.com/docs/7.x/validation#rule-unique

Take a look where it says : Forcing A Unique Rule To Ignore A Given ID.

And here is an example: https://stackoverflow.com/a/33553894/1457270

@akmadhwa just add this one to your model:

public function getCreatedAtAttribute($value)
{
    return Carbon::parse($value)->format('Y-m-d H:i');
}

And then use it:

$user = User::first();
$user->created_at; // 2020-03-27 12:20

@james_bhatta seems like you have a route named for the role, so wouldn't this be enough?

public function authenticated(Request $request, User $user)
{
    $role = $user->role;

    return redirect()->route($role);
}

And do the same one line in the controller. I don't see a route for a customer but. I guess you should have one.

@akmadhwa is your table called customer or customers?

Why do you need to specify it?

Just this does not work:

 $query = $this->model::selectRaw('DATE_FORMAT(created_at, "%Y-%m-%d %H:%i"));

What is your model instance here?

Unfortunately I don't know how to help you based on your message that it is not working.

Check the documentation: https://laravel.com/docs/master/mix#browsersync-reloading

@jaycarter watch just watches for changes in the files and recompiles them, but in order to let the browser know that you've changed something you need to swap those. So that's what hot reload does. You should read the blog post.

You should have a line like this in your package.json in the scripts:

"hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",

try running npm run hot instead.

Maybe read this https://www.itwonders-web.com.sg/blog/hot-reload-laravel-vue-js

And you shoud be using Laravel Mix to take advantage of the Hot reload

https://github.com/JeffreyWay/laravel-mix/blob/master/docs/hot-module-replacement.md

https://wordpress.stackexchange.com/a/261597

make sure you restart XAMPP after the change.

@heimdall what type of field is your category_id? If it is an integer, you might need to loop through the array and persist a row for each of the categories:

foreach(request("categorybox") as $category_id)
{
    $category_dish = new category_dish();
    $category_dish->category_id = $category_id;
    $category_dish->dish_id = $Dishs->id;
    $category_dish->save();
}

And I would guess that you are validating that at least one checkbox is selected, otherwise nothing will be saved here.

@heimdall what type of field is your category_id? If it is an integer, you might need to loop through the array and persist a row for each of the categories:

foreach(request("categorybox") as $category_id)
{
    $category_dish = new category_dish();
    $category_dish->category_id = $category_id;
    $category_dish->dish_id = $Dishs->id;
    $category_dish->save();
}

And I would guess that you are validating that at least one checkbox is selected, otherwise nothing will be saved here.

@dostogir I would guess that you have a name for the user, and you are missing it here to add, so add:

$user->name = 'Some name';

somewhere before you do $user->save();.

@james_bhatta all of those methods are parts of AuthenticatesUsers trait. And LoginController uses it, so check how the LoginController works and make your adjustments.

@moshemo you cannot do it in one go, or rather it will look ugly, you can do it this way:

$validated = request()->validate(['title' => 'required']);

Article::create(request()->only('excerpt', 'body') + $validated);

or just add them as nullable and not required

Article::create(request()->validate([
 'title' => 'required',
 'excerpt' => 'nullable',
 'body' => 'nullable'
]));

@moshemo you cannot do it in one go, or rather it will look ugly, you can do it this way:

$validated = request()->validate(['title' => 'required']);

Article::create(request()->only('excerpt', 'body') + $validated);

or just add them as nullable and not required

Article::create(request()->validate([
 'title' => 'required',
 'excerpt' => 'nullable',
 'body' => 'nullable'
]));

@james_bhatta seems like you have a route named for the role, so wouldn't this be enough?

public function authenticated(Request $request, User $user)
{
    $role = $user->role;

    return redirect()->route($role);
}

And do the same one line in the controller. I don't see a route for a customer but. I guess you should have one.

There is. You can just create Policies, and authorize the users for the access in the controller, instead of the middleware.

@mattb what about something like this: https://laravel.com/docs/7.x/passport

@ezrab_ here is a tutorial that you might find useful: https://medium.com/@godilite/using-laravel-airlock-with-vuejs-1d343ee6f10

And no you should not check for each request if the cookie is set, this is done only on login/registration.

And once you have successfully registered the user, you should not be required to login again. You will need to create a token for the registered user, and then use that token to authenticate/authorize the user.

@benitto_raj try using: ?? instead of or as it was deleted I believe.

Your name{{$name ?? 'Brendonbeni'}}

https://laravel-news.com/blade-templates-null-coalesce-operator

@benitto_raj try using: ?? instead of or as it was deleted I believe.

Your name{{$name ?? 'Brendonbeni'}}

https://laravel-news.com/blade-templates-null-coalesce-operator

@splendidkeen Unfortunately I don't have your project to look on this for you, you will have to find why it returns an array in some cases and an Object in another case. Because clearly you get the error when you response from the controller is an Object instead of an Array like the getUsers returns.

So once again make sure that you return the same response both times. I am out now my friend, sorry but I have work to do.

@splendidkeen try putting a console.log within the computed method to make sure that always the result of this.users is an array as some is a function on an Array in Javascript. If it somehow happens to not be, then add a guard based on the result that you get, to avoid calling some on undefined for example, in case this.users can be undefined at some point. Or make sure that you have initialized it to an [] array at least.

@splendidkeen no it is not crazy.. You are getting data with Array of data, and data is not an object in your case which has a users key.

Does just this do the trick:

this.users = data;

instead of data.users

Well, that's what I suggested as well :) based on your first question above.

@splendidkeen no it is not crazy.. You are getting data with Array of data, and data is not an object in your case which has a users key.

Does just this do the trick:

this.users = data;

instead of data.users

@paddelboot I assume you read the documentation for Sanctum. I don't understand how is Sanctum a 3d party client authorization.

@splendidkeen that's why I said you should log the results in order to ensure that you get same data type back..

try this :

$.ajax({
    context: this,
    type : 'get',
    url : "/search",
    data:{ 'search': this.search },
    success: function (data) {
        console.log(data);
        this.users = data.users;
    }
});

Using context here.

And make sure that the browser console spits out an array of objects.

@palla451 because you cannot use Laravel helpers within a JS file:

ajax: "{{ route('inputs.index') }}",

this can be used in .blade.php but not in .js file.. You should change the URL's.

You should use use instead of with to pass a variable to a closure.

->editColumn('id', function ($storageSpace) use ($colorsCollection){

And no error in the browser console? I doubt that..

Check your Hero.vue file and make sure you are following the correct syntax for a Vue file, and you don't have any syntax errors in there.

Also if you do this:

Vue.component('Hero', require('./components/Hero.vue'));

You don't have to do this:

import Hero from './components/Hero';

nor adding it to the components object of the app Vue instance.

@sinon nothing happened is not a helpful answer at all.

You make sure that you include the .js file in which you added the components.

And try to register them this way instead:

Vue.component('navbar', require('./components/Navbar.vue'));

and use it in your #app element as:

<navbar></navbar>

@sinon nothing happened is not a helpful answer at all.

You make sure that you include the .js file in which you added the components.

And try to register them this way instead:

Vue.component('navbar', require('./components/Navbar.vue'));

and use it in your #app element as:

<navbar></navbar>

And you recompiled the assets? npm run dev ?

@palla451 because you cannot use Laravel helpers within a JS file:

ajax: "{{ route('inputs.index') }}",

this can be used in .blade.php but not in .js file.. You should change the URL's.

Steps that I will try is delete the lines that I doubt that don't work while doing a search and putting them back one by one until I find what causes the problem exactly.

Check the response from both getUsers and doSearch and make sure that the data returned has the same structure and same data type ie, array of objects.

Don't know how else to help here.

Does your collection contains empty items? And is each item an object?

As it is undefined than you should check if there are any users before you do the logic, maybe this will do it:

atLeastOneOpened() {
      return this.users !== undefined && this.users.some(friend => friend.session && friend.session.open);
},

@splendidkeen you keep using the old way.. but you said this:

which lacks the information structured in the UserResource

So I am saying that you need to return the UserResource with the filtered collection, so you get the same response as with the one that works.

Try adding this:

success: function (data) {
    console.log(data);
    self.users = data.users;
}

when you do the search, and make sure you get the data correctly.

@splendidkeen for some reason your this.users is undefined. So in your Vue component do you set the result from the response to the this.users the same way as when you call the getUsers() method?

@splendidkeen and why not returning the same UserResource from the doSearch method?

$filteredUsers = // perform the filter based on the search


return UserResource::collection($filteredUsers); 

This does not work?

@ezrab_ here is a tutorial that you might find useful: https://medium.com/@godilite/using-laravel-airlock-with-vuejs-1d343ee6f10

And no you should not check for each request if the cookie is set, this is done only on login/registration.

And once you have successfully registered the user, you should not be required to login again. You will need to create a token for the registered user, and then use that token to authenticate/authorize the user.

@floatinghero105

this is probably because this request("email") contains the same mail that you are hard-coding..

So in your controller, before you send the email, try debugging that using :

dd(request("email"));

And you probably want the ->from() to be set to an email from which you want the receiver of the email to get the message from and not set it dynamically as you do.

I would put it in a custom form request: https://laravel.com/docs/7.x/validation#form-request-validation

so the controller passes already validated data to the service layer.

@konstruktionsplan share the code which you use to send an email.

you have MAIL_FROM_ADDRESS set to null. Are you setting ->from('email address here') explicitly while sending an email?