ftiersch

Probably it's running into a webserver limitation (either an nginx/apache setting or a php setting) that doesn't allow files larger than 10mb to be uploaded at all. So the validation doesn't get a file to validate basically.

Part of that is correct, yes.

It will not automatically update component B but it will update the store. And if component B uses that store to get the client name it will automatically have the correct one too.

The store is supposed to be the single "source of truth". So what's in the store is reality and every component is supposed to tell the store "hey, I want to make change x!" so everyone knows whats up :)

"Reactive magic" is also something else though - the two way data binding. If you use v-model with an input field for example you can either type something in the input field and it changes the data variable in the component or you can change the data variable and it changes the value of the input field. That's also reactivity :)

Straight from the docs :)

return $this->belongsToMany('App\Podcast')
                ->as('subscription')
                ->withTimestamps();

Straight from the docs :)

return $this->belongsToMany('App\Podcast')
                ->as('subscription')
                ->withTimestamps();

Instead of

$getCartQuantity->where('user_id', $user->id)->quantity->get();

Use

$getCartQuantity->where('user_id', $user->id)->first()->quantity;

But that will throw an error if there is no cart with that user ID, be mindful of that.

If you have data that a view needs every time (no matter where it is rendered from) then yes, that would call for a view composer :)

What do you mean by "call pages by name"? If I understand you correctly I think you're looking for @include, not @yield

@yield would change the name of the section the inheriting template needs to overwrite

If you have data that a view needs every time (no matter where it is rendered from) then yes, that would call for a view composer :)

The JSON is handled automatically but you can transform the data.

Quick example... Let's say you have a blogpost and sometimes you want only certain parts of the posts (title + shortened text for a list view for example) and on the details view you need the whole post.

You could have a ListBlogPostResource and a BlogPostResource to handle that transformation of data from the same BlogPost model. That way the transformation is always the same if you need to do it in multiple places (for example a search endpoint or something like that).

The endpoints are still handled by controllers though, that is correct :)

JSON and XML are both simply text. What the other side makes of the text depends on the header you send with it.

Just use the header "Content-Type" with "application/xml" (I think) and if the endpoint can handle XML it should be okay.

make:resource will create an API resource. Not the same thing as resource controllers!

API Resources are used to transform the responses of APIs in a uniform value, you still need a controller to return them.

Don't render the view inside of the config. Save the path to the view and then include it.

return [
	'views' => [
		'example' => 'test.example',
	]
];

@include(config('test.views.example'))

Something like that

Don't render the view inside of the config. Save the path to the view and then include it.

return [
	'views' => [
		'example' => 'test.example',
	]
];

@include(config('test.views.example'))

Something like that

How and where are you using that resource? can you show the code in the controller (I presume)?

1. If you need to call another method I'd say that sounds like you might need to think about restructuring some of your code
2. Controllers are just objects. You can instantiate it and call it.

Well, now it works because you've basically turned off the CSRF middleware alltogether which causes the 419 error ;-)

Does it happen during the login? Or on a different request? Do sessions work in general?

What SESSION_DRIVER are you using in your .env file?

Sounds to me like a Middleware would be appropriate here and then you can add a Route group with that middleware attached to it.

Sounds to me like a Middleware would be appropriate here and then you can add a Route group with that middleware attached to it.

'hello' => "Hello at <img src='" . asset('/images/logo.jpg') . "'>"

Does this work?

'hello' => "Hello at <img src='" . asset('/images/logo.jpg') . "'>"

Does this work?

Either in your Role model or in your User model you have a relationship user() (or role()) with a belongsToMany. If your junction table is called different you can pass that name as a second parameter to belongsToMany.

Either in your Role model or in your User model you have a relationship user() (or role()) with a belongsToMany. If your junction table is called different you can pass that name as a second parameter to belongsToMany.

https://laravel.com/docs/5.8/eloquent-resources#conditional-attributes

Use "when" instead of "whenLoaded". whenLoaded checks if the given relationship was already loaded and then includes it.

And where is the problem?

How about setting up subdomains for each project and every subdomain points into the respective project folder?

like: http://project1.myserver.com points to /var/www/html/project1/public

And so on

How do you delete it? If this.$el contains the whole table you need to find the correct row inside it.

But if you use VueJS you should use a data driven approach. So your table is rendered from a dataset (probably an array) and if you delete an element of that array it should automatically disappear from view.

That's correct. Migrate and possibly seed the database if you have data that needs to be preseeded.

No problem, instead of

$request->all()

use

$request->except('_token')

:)

{{ $dps->appends([$request->toarray()])->links() }}

You've added two array hierarchies here... "toArray" already returns an array so you don't need the brackets around it.

{{ $dps->appends($request->all())->links() }}

Does this work?

{{ $dps->appends([$request->toarray()])->links() }}

You've added two array hierarchies here... "toArray" already returns an array so you don't need the brackets around it.

{{ $dps->appends($request->all())->links() }}

Does this work?

You can group your result by the isbn :) Should have the same result.

Book::latest('year')->groupBy('isbn')->paginate()

You can group your result by the isbn :) Should have the same result.

Book::latest('year')->groupBy('isbn')->paginate()

Same thing. Just give the column and relationship a different name. "user_updated_id" for example.

Well, it is clear...

Your "workflow" attribute is an integer, not an object like you expect it to be :)

So you need to find out where this attribute is set and why it is an integer and not an object.

And you would reload the page every time someone changes the selection of the first drop down or what is your plan?

->whereRaw('categories.ProductID='.$data.'')

->where('categories.ProductID=' . $request->get('productid'))

Change the first one to the second one, that should at least get rid of your SQL error. But I think there is more wrong with that plan.

->whereRaw('categories.ProductID='.$data.'')

where categories.ProductID={"ProductID":null})

I'm not sure what you are trying to accomplish here exactly?! But an Eloquent Model will automatically be converted to JSON if you force it to a string (which you are doing in that where) and the result is what you see in the error which is not MySQL

Seems like you don't have a RouteFactory? :)

Read up on "props" in vuejs :)

Basically you define a prop on your component and then you can fill it from "outside" like this:

<component :prop-name='@json($someData)'></component>

if ($item->isDirty('status') && $item->status === 'Loaded') {

I think that should work

if ($item->isDirty('status') && $item->status === 'Loaded') {

I think that should work

$item->isDirty('status' === 'Loaded')

This line would check if "false" is dirty... 'status' === 'Loaded' is always false because it compares two strings.

If you still want to save the query object you can use

User::query()

But as the other guys said - usually you don't need it :)

If you still want to save the query object you can use

User::query()

But as the other guys said - usually you don't need it :)

It's a normal php function :-)

nl2br()

https://www.php.net/manual/de/function.nl2br.php

It's a normal php function :-)

nl2br()

https://www.php.net/manual/de/function.nl2br.php

"hasRole" sounds to me like you check if the user "has a role"...

Have you read the documentation?

Says there the method is $user->assignRole('writer');

Reload your page and try again. If it still doesn't work your sessions aren't setup properly - that's why your CSRF doesn't work.

Yeah as long as the pharmacy isn't run by a programmer I think what @jlrdw meant is that it looks like a bug in your code could easily lead to people taking the wrong / wrong amount of medication ;-)

$amount = $records->sum(function ($record) {
	return $record->prescriptions->sum(function ($prescription) {
		return $prescription->prescriptionPayment->amount;
	});
});

If I understand your structure correctly this might work.

Use different variables...

$sum = $records->sum();

$groups = $records->groupBy('type');