ftiersch

"newerThan" would be a >=, not a <= :) You accidentally programmed "olderThan"

Generally it would be okay but you need to use caching in a meaningful way. Otherwise all you're doing is remove all the load from your database and move it to the cache system which then becomes the "slow factor". So I would use caching more for especially slow things.

Like if you need to calculate something and you know the calculation takes a couple seconds but the result only changes every 15 minutes -> cache the result for 15 minutes.

If results don't need to be live cache the results for a while instead of recalculating them every time.

Yeah, I'm not sure how the Middleware that converts empty strings to null behaves with "empty arrays". Maybe you need another middleware that checks for this case end removes empty arrays from the request.

A scope is not a relation, only a "named" chunk of query basically :) You could use it like this:

Product::type()->get();

But it wouldn't work the way you have it setup because in a scope you usually don't even have the actual eloquent model yet. I'm not a hundred percent sure what you are trying to achieve but maybe polymorphic relations would be what you are looking for?

A scope is not a relation, only a "named" chunk of query basically :) You could use it like this:

Product::type()->get();

But it wouldn't work the way you have it setup because in a scope you usually don't even have the actual eloquent model yet. I'm not a hundred percent sure what you are trying to achieve but maybe polymorphic relations would be what you are looking for?

It could be one of a million of reasons but "slow" is just not something we can help you fix unless we know the correct definition :)

A cache can absolutely make websites load faster. If a browser caches an image it doesn't have to download it when the user goes on the page again (but it won't help for the first visit because then the cache is empty). If calculating something (or getting a large result set from the database) takes 10 seconds and you cache it into redis it will absolutely be faster but also the data won't be "live" anymore. So if it changes you need to take care of invalidating that cache to get the update to the user again.

VueJS doesn't necessarily optimize stuff. But if you use npm run production to build your JS it will automatically be minified and uglified, yes.

First of all that depends on what you mean by "slow"...

Slow until the page starts loading? Then images probably don't have anything to do with it but the most likely thing are slow database queries.

Slow until all the JS and images are loaded, but the title for example loads fast? Then you need to optimize those by making them as small as they appear, optimize them and minify / uglify the JavaScript code.

That depends on the format you want to give it to him in.

If you want to create a PDF you could use something like https://github.com/barryvdh/laravel-snappy or (more convenient but a little harder to host) https://github.com/spatie/browsershot :)

Literally the first result when you google "laravel fill"

https://laravel.com/docs/5.8/eloquent#mass-assignment

You can use a Login Event. There is a part of the documentation that describes this:

https://laravel.com/docs/5.7/events#writing-event-subscribers

So you write a Listener class, go to EventServiceProvider and make that Listener listen to the Login Event and in that Listener you can execute your code :)

It's not depending on the fieldset, only on the field names.

It is a little tricky though because you have multiple values for every fieldset.

You could either do something like this:

<input type="text" name="comment[]">
<input type="text" name="title[]">

And then work with the numeric keys of an array. Or you do something like this:

<input type="text" name="data[1][comment]">
<input type="text" name="data[1][title]">

Then you can work with a single array that has your values.

foreach (request('data') as $values) {
    Log::create($values);
}

Just an example of course :)

1. If you want to send an array to the server you need to call the variable comment[] for example. Then PHP will understand it's actually multiple values. Otherwise it will just use the last one because that overwrites all the previous ones.

2. You need to have a loop in your backend if you want to create multiple Log entries.

foreach (request('comment') as $comment) {
    Log::create([
        'comment' => $comment,
    ]);
}

Something like this :)

You can just get all of them and then group them later in the collection.

For example like this:

$data = CustomerScan::get()->groupBy(function ($scan) {
    return $scan->created_at->toDateString();
});

(of course you will have to add all your where methods and stuff, just remove the group by from the query and move it to the end :))

Edit: I just noticed you did that already. So yes, @sinnbeck is right. Just remove the groupBy from the query (not the last one) and you should get your result.

I think you have to fetch the row first before you can call value() on it.

$email = User::where('id', $applicantId)->first()->value('email');

Before you think about Laravel itself think about all the other things that are easy wins...

1. Optimize your images and display them in the correct size (don't display full size images as a thumbnail)
2. Possibly lazyload images
3. Minify, uglify and gzip JavaScript

Those are usually the biggest "offenders".

The next one is probably not on Laravel itself but on Database queries. Optimize those.

After all of that you can work on smaller stuff. Caching etc.

@foreach ($list as $listItem)
{
        "label": {{ $listItem->menu }},
        "value": {{ $listItem->view }}
    }
@endforeach

In the PageSeen table but you are getting multiple records from the pageseen table in a collection. You need to select one of them.

For example

$list->first()->menu

You can't decode hashes. That's the point. What are you trying to achieve?

Nah, I think he means imagining it as a timeline :) Left is 0 so if you point the arrow to the left < you check for "older"

"newerThan" would be a >=, not a <= :) You accidentally programmed "olderThan"

Can you show an example?

Possibly the method runs before the data is actually there. In the template that's not a problem because it's reactive and just changes as soon as the data is there but a method doesn't do that.

I think that exception is thrown before your session is even started (but not totally sure) because it happens while Laravel tries to determine which route to send the user to. And because it can't find a route with the given method it throws an exception.

Could absolutely be a bot, yes. If you're sure you're only sending POST requests to that route that's probably very likely. But remember if you redirect to that route it will also be a GET request - maybe that's the problem. (a redirect()->back() or something like that).

Basically it's (part of) what you do with UnitTests and so on.

You develop feature A and test it so it works.

Now you develop feature B but while developing it you accidentally break feature A. That would be a regression. To avoid that you would have to test every feature on your site everytime after creating a new feature. That are regression tests.

And to make that process easier there are automated tests like UnitTests so you don't actually have to do it yourself. :)

Source: German Wikipedia.

Well yeah, because your "endTime" is the start of today so the diff in seconds would be quite large.

$refresh = now()->addDay()->startOfDay()->diffInSeconds(now());

This should give you the seconds until midnight if I'm thinking correctly.

The accessors and mutators are only called when you use the variable explicitly.

You could use a Resource for your Patient and inside there it would be called explicitly and decrypted automatically. Also with that you will have finer control what values are actually returned (if you are using an API here).

Another possibility would be to use Eloquent events (saving and retrieved maybe?) to only encrypt the values while writing them to the database because I guess in your code you don't need the encrypted values?

Well yeah, because your "endTime" is the start of today so the diff in seconds would be quite large.

$refresh = now()->addDay()->startOfDay()->diffInSeconds(now());

This should give you the seconds until midnight if I'm thinking correctly.

Just change @lostdreamer_nl 's answer a little to use arrays instead of objects:

$data = collect(json_decode($jsonData, true));

$emails = $data->filter(function($object) { return $object['fiador'] == 1; })
    ->map(function($object) { return $object['eMail']; })
->toArray();

That depends on the format you want to give it to him in.

If you want to create a PDF you could use something like https://github.com/barryvdh/laravel-snappy or (more convenient but a little harder to host) https://github.com/spatie/browsershot :)

value.filter(object => {
    return object.fiador == 1;
}).map(object => {
    return object.eMail;
});

this gives you an array with all the emails. Now you can do with them what you like. For example filter empty ones or just get the first one :)

Did you reload your page before you tried the method('put')?

Happens to me all the time that I change HTML stuff, click on "submit" in the form and wonder why it doesn't work and the next time it works because I actually refreshed my HTML with that submit and forgot before.

The accessors and mutators are only called when you use the variable explicitly.

You could use a Resource for your Patient and inside there it would be called explicitly and decrypted automatically. Also with that you will have finer control what values are actually returned (if you are using an API here).

Another possibility would be to use Eloquent events (saving and retrieved maybe?) to only encrypt the values while writing them to the database because I guess in your code you don't need the encrypted values?

Sure, the Laravel Collective doesn't do any magic. You just have to program the logic yourself :)

You basically create a foreach loop for your countries like that:

<select name="country">
    @foreach ($countries as $country)
        <option value="{{ $country }}" @if(old('country', 'default country') == $country) selected="selected" @endif>{{ $country }}</option>
    @endforeach
</select>

Sure, the Laravel Collective doesn't do any magic. You just have to program the logic yourself :)

You basically create a foreach loop for your countries like that:

<select name="country">
    @foreach ($countries as $country)
        <option value="{{ $country }}" @if(old('country', 'default country') == $country) selected="selected" @endif>{{ $country }}</option>
    @endforeach
</select>

You could do something like this:

'pendingTasks' => $project->tasks->filter(function ($task) {
    return !$task->completed;
}),
'completeTasks' => $project->tasks->filter(function ($task) {
    return $task->completed;
}),

You could do something like this:

'pendingTasks' => $project->tasks->filter(function ($task) {
    return !$task->completed;
}),
'completeTasks' => $project->tasks->filter(function ($task) {
    return $task->completed;
}),

What do you mean exactly "control the routes via vue.js"? I'm not really sure what you are trying to accomplish.

Auth::routes() defines the default laravel authentication routes if you have them installed. There should actually be a 'login' route in there already.

And the default logic is it will redirect you to a route named "login" if you try to access a route thats protected while you are not logged in. You can check the Authenticate middleware and change that name.

No you can't do that. Laravel looks through your routes one by one and calls the first one that matches the given URL. Everything else will be ignored. So if you rename one of them your problem should go away :)

Your service route is protected by authentication. So if you click it and you are not authenticated it will automatically redirect you to the login page.

You're a genius! Man... No idea why I haven't tried that before.

I'm not quite sure what kind of data is coming into the responseAdapter method.

Have you tried console.logging the data variable to check if data.teamLeaderOfWithDescendants exists?

Only the MAIL FROM part. DKIM is verified and working. Also the emails are working but they are currently being sent from some AWS subdomain which is the default and I think that's triggering some Spam filters which is why I'd like to set the MAIL FROM domain.

I'm just not sure how to get around that problem :)

Well, I changed the DNS setting also a couple weeks ago (same time as DKIM which was recognized in minutes) so I hope it's not that :D

Sure.

The TLD is baufragen.de and the FROM domain is mail.baufragen.de

Thanks!

Hey,

I have a problem with AWS. I have setup a SES domain to send emails (which works flawlessly) but sometimes mails bounce because of spam. So a couple weeks ago I activated DKIM which also works great.

Now I'm trying to change the MAIL FROM domain and have setup a subdomain to use (mail.thedomain.com) and added the necessary MX and SPF records to the DNS but Amazon is not able to pick it up.

I tried a lookup with mxtoolbox.com and the values are shown there just the way it's supposed to be but the status in the AWS console doesn't change from "pending".

Any hints why this might be the case?

Cheers!

@fortran001 Your code got truncated, can you post it again? :)

Is there an error message?

But I think @nakov meant Arr::get(), not Array::get() :)

Where does your "zipcode" variable come from? and you are passing "oldZipcode" but never use it.

You have a URL parameter {mechanic_service_station_info} in your URL but your Add() method expects $mechanic_id

Didn't even read the error message, did you @munazzil ?

array_get has been deprecated. If you have upgraded your Laravel version check out the upgrade guide. :)