Snapey

Well I don't know where your trait originated from and it seems quite complex, processing each of the files and returning some modified request object that contains the filenames of the uploaded videos.

This would seem to suggest that you don't need to put it in a loop, just call it and then process what you get back after it has saved the files.

Your trait is included in the controller.

It looks like this;

public function saveFiles(Request $request)

So you need to use it like this

$output = $this->saveFiles($request)

(passing in a request object)

What version were you expecting?

The linter will pick up syntax errors but it won't stop that code being executed when you actually use the data in a view or a form.

Routes in api.php are stateless

You need to be passing an identity token with every request in order to be associated with a user account. Are you doing this or are you expecting it to be handled with sessions (as per web.php)

Whats 'the linter'

Did you consider my suggestion to not use blade at all..?

Basically you are opening it up for a user to do ANYTHING on your server.

Suppose I put

here is some boring text <?php unlink(base_path(.env)) ?> and then your @include('template') 

I just deleted the env file

You could invent your own syntax that behaves differently to blade. For instance, you could use [ and ] to wrap the include name

This is a line of text in the database field
[terms_conditions2]
summary of what was proposed

the bracketed statement is easier to check, and won't blow up when processed if they leave off a bracket

In your code you can regex replace the bracketed term with the blade include. I have no idea of your use case, but I imagined something like a quote builder where you needed to include standard passages of text or form.

you can call View::make() passing in the string and will get back the compiled view.

How you tell that its 'valid', i cannot say

Laravel does not have a 'file upload path' you have to decide where to put the file. In your case it sounds like you want to put the file on the public disk.

This is the second parameter in the store command or third parameter in storeAs

https://laravel.com/docs/master/requests#storing-uploaded-files

eg

$path = $request->photo->storeAs('images', 'filename.jpg', 'public');

and what is in the addressbar when you request password reset

console log the data. Its all dependent on this var button = $(event.relatedTarget) picking up on the anchor link and getting access to the data attributes

 <form action="{{ route('directory.destroy',$directory->id) }}" method="POST" >
    @csrf
    @method('DELETE')

   <button type="submit" class="btn btn-danger" >
       <img src="../..(../../public/storage/admin/delete.png"/>
    </button>
</form>

unchecked checkboxes are not sent in the request

I stopped trying to use with in my models and have not looked back

What is in the address bar of the browser when you see this error

If you are really that lazy, you can put it in Controller.php

@wilk_randall is correct

Route says

Route::get('edit-recipient/{id}',

therefore parameter in the request is 'id' and NOT $rpt_id

change route;

Route::get('edit-recipient/{recipient}','[email protected]');

change controller;

public function editRecipient(Request $request, RecipientModel $recipient) {

        return view('pages.report.create_recipient')
                ->with('data', $recipient);
    }

and then the framework will perform route model binding and automatically inject the correct model into the controller

So when do you get the error, is it when creating the email or when clicking on the link in the email.

What does the error message say about the file and line number

Still cannot help without more code

This is not right

$url = url('password/reset/{token}'.$this->token);

it should be

url = url('password/reset/',$this->token);

or

url = url('password/reset/' . $this->token);

Answer my question then..

Is http://localhost where you are testing your site?

have you assigned all the data- properties in the blade loop?

Any console errors?

Does everyone use http ?

Your exclusion should be just the local part of the route, eg /payment/status, certainly not including your domain name as that should never be in code.

I'm not interested in the UI

You are using $setfield->code. This is not working properly perhaps causing Value to be null when inserting into the database.

Or, you are setting the name of the field correctly but then not processing it correctly in the controller.

old() is used when the form validation fails and means you dont have to reenter all the good values

the code is actually not very good since it prioritises data from the model so in the case of edit and a validation failure then the user has the make their changes again.

Better is

value="{{ ($data) ? old('nama', $data->nama): }}">

But I would go with

value="{{  old('nama', $data->nama) }}">

and pass an empty model into the create view from the controller

well, i guess we really need to see what creates $exists dont you think?

and the code you show for tinker is messed up

$i = App\courseInstructor::where('user_id','2')->where('course_id','6')->get()

ignore that

The callback url should be excluded from csrf checking

change Route('paytm-callback'); to be route('paytm-callback');

what package are you using to turn select boxes into a settings model?

There is more going off than you are showing here making it impossible to answer your question

because you miss the semicolon off the second line

why do you need to do any query? you are getting the id to assign, just use that?

Why do you want to put the users name in assigned_to? is it not a relation?

If you still have a question, please format your code by putting 3 backticks ``` on a line before and after each code block

Its a clue to the answer

Hopefully this is fixed now if you remove the with statements from your models

When defining a belongsTo relationship you only need define it with a foreign key in one table. Eloquent will workout the right key to use for hasMany or hasOne

As your employees table has user_id column then the Employee model belongs to the User

Employee.php

public function user()
{
    return $this->belongsTo(User::class);
}

and the reverse is hasOne (or hasMany)

User.php

public function employee()
{
    return $this->hasOne(Employee::class);
}

or, if many

public function employees()
{
    return $this->hasMany(Employee::class);
}

mnzxbcm

Its dangerous to use, and will ALWAYS break if you try to load related models

User loads Employee loads User loads Employee loads User etc etc until you run out of memory.

Do it one way only or not at all.

Show your Home model?

what you want to do is possible, but with the following tips

• target the view you want the code only
• create a composer and put your code in the compose method. This will be called later in the request cycle than a service provider boot method
• wrap your code in an if(Auth::check())
• provide a better relationship between the two models

this contains an example of calling the compose method of a view composer class

https://scotch.io/tutorials/sharing-data-between-views-using-laravel-view-composers

just an observation

if its common then you should have a relationship between camper and user so that you don't have to search using the email address

you have to allow for not being logged in else you wond be able to render the login page

be careful with this approach, your queries will be run for every view partial rendered (because of *)

From the docs;

Just before the view is rendered, the composer's compose method is called with the Illuminate\View\View instance. You may use the with method to bind data to the view.

so, you should be able to move your code to a compose() method

I suggest that you install Laravel debugbar so that you can check what queries are being run.

neither of those use the login, unless referenced in your login controller?

ok. Do you have those routes using the middleware?

i mean, how do you expect it to be used. It has nothing to do with the login process?

it should be fairly easy to exclude bits of code to find what is causing the issue?

Do ypu have the right concept for redirectIfAuthenticated? its purpose is to keep logged in users away from login and register routes

do you have any with() statements in your models?

Sorry, you need to specify user

eg,

$items = Auth::user()->homes()->rooms()->boxes()->items();

or if you have user

$items = $user->homes()->rooms()->boxes()->items();