Sign up to access "Build an E-Commerce Platform" right now.

and one user who was signed in and it's been associated. So our goal now is when we are over on that order confirmation page or even if we just hit register at a later date, if the email matches that order,

we're going to go ahead and associate the orders with that user. Now we have to be really careful here because technically if I go and check out with an email address and someone else signs up with that email address within Laravel by default, particularly with Laravel Fortify,

we are already signed in. So we will automatically be signed in. Particularly with Laravel Breeze, we're automatically signed in once we've registered. So what I would recommend we do, and we can do this a little bit later on,

is taking advantage of verifying our email address. So what we would do is register, receive an email, verify that we actually own that email address before we start to attach any orders. So we'll look at that later, but we'll get this base functionality working first of all.

So the goal is I'm going to register with the email of mable at codecourse.com and that should hook up them two orders to my account. So let's start out by going over to our event service provider. Now when we register over in the registered user controller just here,

this will fire an event for us, this registered event. And of course, as we've already seen, log the user in. So what we want to do is tap into this and create a new listener in here to this registered event and attach some orders.

So let's go ahead and say attach orders class. Now the reason I'm defining this out here first of all is within Laravel rather than having to say make listener, what we can actually do is say event generate.

And that's going to go ahead and look at any of the listeners that you defined here that don't already exist and it will create them for you. So let's go ahead and run that. And you can see that events and listeners have been generated successfully.

So if we go ahead and look for this attach orders, what you'll actually notice is it's within app and providers. That is just because we didn't define a namespace to this and that's been created at the namespace that we define this,

which is within app providers. So just be careful with this. Let's go over and delete attach orders from providers. And then within our event service provider,

we'll actually go ahead and namespace this manually at the top. So use app and this is going to be in listeners and attach orders like so. So now when we rerun this event generate command, if we go over to attach orders, that is now in app and listeners.

If we just head over here, there we go. Great. Okay. So within attach orders, what kind of information do we need to use inside of here?

Well, we've got this registered event. Let's just die dump on this event here and just see what information we get. Now, of course, what we're going to have to do is actually go through and register. So let's just create an account out in here.

And let's create Mabel and just see what we get. We'll just delete this from the database as we go. So let's create this out in here and register. And there we go.

So we get this registered event and we get this public user property on here. You can check this out by actually going over to the registered event. So let's find that under auth events that's in the base framework. And you can see that into the constructor, sure enough, we get the user.

And that's pretty much all of the information that we need. So let's head over to the database. Just delete that user because that's, of course, the user that we want to attach them orders to. So eventually, these will be set to that user's ID.

And let's just go ahead and do this in a kind of roundabout way, maybe creating a couple more queries than we need to. But let's go ahead and say where email is event user, which is that property that we've just seen in email.

We're going to go ahead and get all of them orders. So basically grab all the orders where that email matches. And then we're going to go through and just use the each method on a Laravel collection. And for each of them orders, we want to attach that order to that user.

So let's go ahead and bring our event into scope. And let's say order user associate and event user. That's going to be the user that's just been created. And then let's go ahead and say order and save.

So there are ways to do this with just one query. But let's leave this as it is for now. Get it working. And we can always refactor it later.

OK, let's see what happens when we now register with that user. So let's go ahead and create an account under Mabel with that email address. Choose a password. Hit register.

We're signed in automatically. If we can now come over, you can see that them two orders have been associated. That now means that when we create our orders page that we'll be able to click on from this dropdown, the user will see them two orders that they created earlier as a guest.