Snapey

so everything else is pretty much irrelevant apart from

$results = $results->sortByDesc(function ($result, $key) {
	return $result -> xyz;
});

You have a collection of models. You add an extra value to each model? then sort.

What does $results look like before and after this function

back is not some magic method that whisks you off somewhere else.

Your return goes back to whatever called checkStripe()

If that caller is not expecting a redirect as a response, then it will just ignore it.

when you get() from the model, you can specify the attributes you want?

->get(['id','user'])

or use makeHidden https://laravel.com/docs/7.x/eloquent-collections#method-makeHidden

can you use this https://laravel.com/docs/7.x/eloquent-resources#concept-overview

Maybe not all attributes have pizzaIngredients, or not all items have attributes?

try

@foreach($item->attributes->pizzaIngredients ?? [] as $ingredient)

@endforeach

start by considering WHAT you are trying to put in that table cell.

You cannot call Auth::user() if they are not logged in (well you can but you will just get null).

A user that cannot remember their password cannot be logged in.

Therefore you need to use a different layout file, or wrap your use of Auth::user with a check to see if they are logged in.

See Authentication Directives on this page https://laravel.com/docs/7.x/blade

eg

@auth
	Welcome {{ Auth::user()->name }}
@endauth

Sort this out first, then you can concentrate on fixing password reset

and also no # characters - easier and safer to just quote the string

I have a blog post for this

http://novate.co.uk/dynamic-cascading-dropdown-with-livewire/

Mark Tray2's answer correct, not your own

Your error message provides vital information about WHERE the error is occuring

Its in the layouts.blade.php file - not any of the code you show here.

You are probably trying to display something about the user - perhaps their name - in the page header, but they are not logged in.

Also, in the code you do show, you have this line

$user = User::first();

Just gets the very first user in the system. Are you expecting to only have one user?

You should find the user by their email address and then get rid of the later check

$user = User::where('email', $request->email)->first();

You need to make sure that the hash is suitable for encoding in a URL (only uses url safe characters)

Or, use a long random token, or signed URLs

use a signed URL then you don't need a hash at all, and it is automatically checked for you

https://laravel.com/docs/7.x/urls#signed-urls

Yes, depending on if you want public visibility of the file, as per your other question.

@donclemenzo doesn't work for YOU? Why not start a question with your own circumstances and explain what 'doesn't work' means

If you don't need to access the PDF from a web page, then yes, put it in storage/app and not storage/app/public

You are overlooking the effect of multiple relations

if item has orders (plural) then you cannot chain items or product from there because there are many of them

I did it in a Laravel 6 project and posted the code above.

I did find it was difficult to get the string to match. I had to put it all on one line.

Make sure you start with the string in the notification email of the version you are using.

You can create an observer that acts on model creating and updating

https://laravel.com/docs/7.x/eloquent#observers

You can do this in the database, but if you don't want to do this, use reduce not map.

whenever you have more than one arrow in an expression, should defend against one of the objects being null.

so, if $item has no orders then your code will blow up

It may not be the first item, or the second, but could be the fourth, the tenth or the last. Any of them null and the page blows up and you don't see any.

Don't dismiss @burimb advice because it is good.

Personally, I always use the null coalesce operator, so write the line as

<td >{{$item->orders->items->product->parentProduct->id ?? ''}}</td>

even if this does not fix your problem, its still better code.

I have to say though that this chain is extremely fragile, and unless they are all one to one then your code will break.

if item has orders then this implies a 1:many relationship so you cannot get items from orders since there are many of them to choose from. Which order do you want to use?

You should write the file to storage/app/public, and then symlink it to the public/storage folder.

This is because your webserver should have permission to write to the storage folder and not the public folder

Please format your code by putting 3 backticks ``` on a line before and after each code block

are you looking in;

storage/app/public/storage/documents/invoice

This assumes that in config/filesystems, that default disk is 'local', and this resolves to storage/app

You can confirm this by opening tinker and typing config('filesystems')

one way is to leverage relationships

  $origin = Auth::user()->origins()->create(request()->validate([
            'name' => 'required',
            'url' => 'required|url',
        ]));

Eloquent will automatically apply the user_id to the origin record (this assumes that user model has a origins function

clarification

this

Auth::user()->origins()

is the same as

auth()->user()->origins()

is the same as

$request->user()->origins()

The most likely problem is a mismatch in the number of times the password is hashed.

Its either twice when registering (thus destroying the password), or

its hashed twice when logging in so does not match the database.

This can be caused by one of the following being the case;

• The User model has an accessor that automatically hashes the password, but you are doing it outside of the model also
• The User model has an observer on creating that automatically hashes the password, but you are doing it outside of the model also
• Your login script is hashing the password then passing it to the check function (when it is not required to hash first)

None of the above should be a problem when using out of the box authentication - it just works.

So, it must be something you have changed.

But first things first, you should check that your credentials are correctly being passed to the login controller.

You need to pass the ID into the modal. Not the simplest solution, so I would avoid this if you are not comfortable with Javascript.

good. Glad you were able to sort it out. Sorry, I had gone for dinner.

Hi

You have two options.

1.Publish the email templates. php artisan vendor:publish and select Notifications

review the template that is now in resources/views/vendor/notifications/email.blade.php

You will see lines

@lang('Regards')

and

@lang(
    "If you’re having trouble clicking the \":actionText\" button, copy and paste the URL below\n".
    'into your web browser: [:actionURL](:actionURL)',
    [
        'actionText' => $actionText,
        'actionURL' => $actionUrl,
    ]
)

You can just delete these lines or change them for the exact wording that you want. Bear in mind that this email template is the default for all notifications.

2.Change the strings in the translation files. see https://laravel.com/docs/7.x/localization#using-translation-strings-as-keys

I'm assuming the only language you have is english ('en') If you are using other or multiple languages, adapt to suit.

create a file en.json in the lang folder

add the translations, specifying the exact string that is in the email and its replacement

{
    "Regards": "Bestu kveðjur",

    "If you’re having trouble clicking the \":actionText\" button, copy and paste the URL below\ninto your web browser: [:actionURL](:actionURL)":
    "Open this email :actionText in your browser mate [:actionURL](:actionURL)"

}

You only need to use method 1 or method 2, but use both methods if you need to send out the email in the user's language.

Hi

You have two options.

1.Publish the email templates. php artisan vendor:publish and select Notifications

review the template that is now in resources/views/vendor/notifications/email.blade.php

You will see lines

@lang('Regards')

and

@lang(
    "If you’re having trouble clicking the \":actionText\" button, copy and paste the URL below\n".
    'into your web browser: [:actionURL](:actionURL)',
    [
        'actionText' => $actionText,
        'actionURL' => $actionUrl,
    ]
)

You can just delete these lines or change them for the exact wording that you want. Bear in mind that this email template is the default for all notifications.

2.Change the strings in the translation files. see https://laravel.com/docs/7.x/localization#using-translation-strings-as-keys

I'm assuming the only language you have is english ('en') If you are using other or multiple languages, adapt to suit.

create a file en.json in the lang folder

add the translations, specifying the exact string that is in the email and its replacement

{
    "Regards": "Bestu kveðjur",

    "If you’re having trouble clicking the \":actionText\" button, copy and paste the URL below\ninto your web browser: [:actionURL](:actionURL)":
    "Open this email :actionText in your browser mate [:actionURL](:actionURL)"

}

You only need to use method 1 or method 2, but use both methods if you need to send out the email in the user's language.

If the user can only be employee or admin then don't have a roles relationship. Have a single role.

If someone can be both employee and admin then these could be in either order, so roles[0] could be admin or employee, depending on the order they were created in.

If user can have multiple roles, then get the roles and see if they 'contain' the role you are looking for.

so if the user can only have a single role, why have you set it up with a roles() relationship

sounds like the user model should have a role() method, which is a belongsTo the role model and requires a 'role_id` column on the user.

Then you don't need to use role[0] and hope its correct.

models make it very easy to use a pivot table since you can ignore them.

Suppose you have a model User and a model Role. Since user can have many roles, and role can have many users, a Many to Many condition exists, which requires the use of a Pivot table.

A table role_user is created with user_id and role_id columns pointing to the relevant models

Each model has a relationship, belongsToMany to tell eloquent to find related models through the pivot

Assuming both $user and $role exist, one way to join them and create an entry in the pivot table would be for instance

$user->roles()->attach($role);

They are probably failing because of the dns element of the check. You cannot have an email address @ a top level domain

I don't think you will pick it up first go. You have to take information from multiple sources and then gradually the pieces fall into place. You may need to go over the videos again at a later date because then things make more sense.

The only real way to learn php (or any language) is to write code and read code, over and over.

Sorry if you expected a perfect solution.

Also look at tutorials on youtube; Academind, Coder's Tape, The Net Ninja, Andre Madarang to name a few

in your observer you need to import App\Activity

use App\Activity;

at the moment it is looking for the class in its own namespace

edit: I see you have done this, but you have a typo

in your observer you need to import App\Activity

use App\Activity;

at the moment it is looking for the class in its own namespace

edit: I see you have done this, but you have a typo

use $request->only() and pass the function just the relevant fields

in your form, you don't say what you want to delete

<form method="POST" >
          @csrf
          @method('delete')

you should set an action and the id of the thing being deleted

its not about how many roles you have, its about how many roles a user can have

open tinker

>>> $u = App\User::find(1)     //insert valid user number

>>> $u->profile_picture;

>>> asset($u->profile_picture);

what do you get

The other thing I thought of was a courses relationship on Location which is a hasManyThough passing through entrees, you could then simply do $location->load('courses.entrees') and not bother with the grouping

personally, I would probably have course as an attribute of entree, not a separate model, bit I admit, I dont have the full knowledge of what you need to do.

this code should not do this, as your entrees are related to a single location?

do the query in tinker, and count the results to check its as expected

hmm, tricky

So you want to group entrees by the course?

Its hard to visualise, it seems a bit back to front. I would probably get location with eager load entrees.course and then group entrees by its course using a collection method.

    $entrees = $location->entrees()->with('course')->get();

    $grouped = $entrees->groupBy(function($entree){
                   return $entree->course->name;
               });

similar to yours, but loading the course.

can you explain the relationships between the models?

sort or group?

If the user can only be employee or admin then don't have a roles relationship. Have a single role.

If someone can be both employee and admin then these could be in either order, so roles[0] could be admin or employee, depending on the order they were created in.

If user can have multiple roles, then get the roles and see if they 'contain' the role you are looking for.

Sorry to complicate things, but this breaks when the user has two tabs open. One they are working in, with 45 minutes of session left, and another tab which is saying that their session is/has expired. The timers in your pages are not linked in any way so one can be counting down and the other reset with each interaction.

everytime you hit the back-end (for whatever reason) reset the timer back to 45 minutes, and of course when the page is reloaded.

I don't understand why you are showing server code. You cannot do anything at the server to get the session duration because as I said, it will always be reset to 45 minutes in response to a request.

The only way you can push anything different from the server is to have a websocket based presence channel and a backend job that checks for users approaching session end and sends them a notification.