piljac1

Use double quotes for string interpolation

@component('mail::button', ['url' => "http://serviceac.test/requests/payment/{$permintaan->id}"])

No problem :) ! Can you try the second solution I proposed ? (Just curious to see if that was the issue with string type lat/long haha)

Why is it important to get the numbers (IDs) "right" when outputting different types of user ? In which context will it be used ? Couldn't you simply use your collection's keys (+ 1) to achieve what you're trying to obtain such as :

foreach (User::where('role', 'admin')->get() as $key => $admin) {
    // Do stuff
}

Edit: if you need a solution in Blade, see @siangboon answer

Also, have you tried like this ?

 ->whereGeoDistance('location_latlon', "{$request->longitude},{$request->latitude}", '100km')

According to the Geo-distance query doc, only numbers are passed in an array. Lat/long of string type are passed as a single string, like the following :

"40,-70"

Have you tried casting ?

 ->whereGeoDistance('location_latlon', [floatval($request->longitude), floatval($request->latitude)], '100km')

@movepixels Alright !

It's a bit hard to help you without any code sample to start from, but I would do something along those lines (get rid of your current after_or_equal validator) :

// In your validation
$request->validate([
...

    'start_date' => [
        'required', // Whatever your other validations are
        'date',
        function ($attribute, $value, $fail) {
            try {
                $date = Carbon::parse($value);

                // If the date is not equal to the model's start date
                // ($model here would be the model being updated)
                if ($date->ne($model->start_date)) {

                    // If the date is before the current date, make the validation fail
                    if ($date->lt(now())) {
                        $fail($attribute . ' must be a date after or equal to today.');
                    }
                }
            } catch (\Exception $err) {
                $fail($attribute . ' is not a valid date.');
            }
        },  
    ],

...
]);

Use a similar logic for the end_date.

If you want to avoid using a try catch, you can use the bail validator to make the validation stop if the date validation fails.

// In your validation
$request->validate([
...

    'start_date' => [
        'bail',
        'required', // Whatever your other validations are
        'date',
        function ($attribute, $value, $fail) {
            $date = Carbon::parse($value);

            // If the date is not equal to the model's start date
            // ($model here would be the model being updated)
            if ($date->ne($model->start_date)) {

                // If the date is before current date, make the validation fail
                if ($date->lt(now())) {
                    $fail($attribute . ' must be a date after or equal to today.');
                }
            }
        },  
    ],

...
]);

Let me know if it works !

Why is that line commented out ?

'App\Model' => 'App\Policies\ModelPolicy'

When using $request->attribute, Laravel will first look for the parameter's value in the request payload. If it is not present, Laravel will search for the field in the route parameters*.

$request->input('attribute') is pretty much the same, but it will also accept array inputs with the dot syntax: $request->input('attribute.0.name') or $request->input('attribute.*.name'). You can set a default value as well with: $request->input('attribute', 'defaultValue')

*From Laravel's docs

@jlrdw That's what I said in the next sentence :P I edited my post to avoid confusion.

Eloquent is technically slower, because it has to build the actual SQL query, but I wouldn't say that the difference is noticeable (except if Eloquent is not used correctly in the context). For example, the following code example will run two separate SQL queries :

Book::with('author')->where('title', 'like', '%a%')->get();

The following one only runs one query and is multiple times faster than the one above :

DB::table('books')->join('authors', 'books.author_id', 'authors.id')->where('title', 'like', '%a%')->get();

An entirely raw query equivalent to the one above is performed practically (I can almost say equally) as fast as the one above :

DB::select("select * from books join authors on books.author_id = authors.id where title like '%a%'");

As for safety, Eloquent is safer than a raw SQL query because it uses PDO out of the box (which prevents SQL injection with parametered queries). You can still use bindings with raw SQL queries though.

The Laravel functionality of being able to retrieve the ID of a created element only works if the ID is set as autoincrement.

In your case, you'll need to generate a new UUID (returning the generated value in a variable) and then use this variable moving on.

Or you can try the solution depicted here : https://stackoverflow.com/questions/17280616/laravel-lastinsertid-with-uuid-pk

Oh. I just saw you updated your post and it really is returning your current page's HTML. At the same time, I just realized what your error is. In your AJAX params you wrote URL instead of url. JavaScript is case sensitive so your URL property is not considered the same as url.

You AJAX call is sent after your view is already loaded and when you click the delete button, so don't expect your current view to "die". You'll be able to see your die (if you output something of course) in your browser's network tab.

As for the returned HTML code you mentioned, are you sure it is the exact same HTML code ? Because it sounds like it might be a Laravel error view.

An array in an ID field ? Can you elaborate on your database structure ?

What @ftiersch said. If you want to avoid this issue, you can use optional such as :

return optional($feature)->name;

That way it won't crash but will return null if no Feature model matching the $metaId is found.

You wrote

deafult(false);

Instead of

default(false);

Did you run your queue ?

php artisan queue:work

// or queue:listen if you want to continuously process jobs on the queue

php artisan queue:listen

Broadcasting uses the default queue (except if you stated otherwise in your broadcasting settings) and doesn't work if the queue is not listening.

I do not know much about Mix since I started using it a couple of weeks ago, but I would personally try the following:

1. Create a custom console command (php artisan) that would upload compiled files to the desired server
2. Add it to your npm run dev / npm run watch commands in your package.json file (perhaps your command would have a param to indicate the destination site - dev or prod)

"scripts": {
    // "uploadToServer" would be the command name you choose of course

    "dev": "npm run development && php artisan uploadToServer dev",

    // other npm commands

    "prod": "npm run production && php artisan uploadToServer prod",

    // other npm commands
},

1. Call "npm run dev" or "npm run prod" as usual, but now it will execute the command you created afterwards

Is it the best way to accomplish what you're trying to do ? I couldn't answer due to my limited Mix knowledge. Would it work ? There are pretty good chances that it would.

Simple question: are you running your broadcast queue (default queue is the default setting) ?

Have you checked your network tab in your browser to get more info ? It sounds like it could be an error 500.

@atfinho No problem ! Please mark it as best answer if it was the solution you were looking for so others searching for the same issue can see it on top :) Thank you and have a good day of programming !

You can use onDelete('SET NULL') on your foreign key declaration, such as :

$table->foreign('zipcode_id')->references('id')->on('zipcodes')->onDelete('SET NULL');

Don't forget to to set your foreign key id ("zipcode_id") as nullable

$table->integer('zipcode_id')->unsigned()->nullable();

If you're trying to have a different style for each individual component, you can add a style tag inside your Vue component with the "scoped" attribute.

Example:

<style scoped>
    .round-sorting {
       color: red;
    }
</style>

View this link for more detail : https://vue-loader.vuejs.org/guide/scoped-css.html#mixing-local-and-global-styles

Hi guys ! I'm questionning myself to know what is the best way to implement an extra dynamic attribute in a default validation message (validation.php).

I know it is possible to redefine specific attribute rules (which overide the generic rules) with the following:

// validation.php

'custom' => [
    'refund_amount.*' => [
        'min' => "The :attribute must be at least :min.",
    ],
],

But at the same time, it only implies that you can change the sentence, but not the actual dynamic attributes themselves.

I would like to add a dynamic ":field" attribute in the above code snippet:

// validation.php

...
        'min' => "The :field :attribute must be at least :min.",
...

I was wondering if there was a "standardized" way to do so, because I found a workaround (in the FormRequest itself), by looping through my refund_amount inputs (array of inputs with a key containing their IDs) and set each specific validation messages for the array (ex.: refund_amount.1.min, refund_amount.2.min, etc.). To do so, I'm calling a slightly modified version of the above translation and assign the :field attribute value. But it doesn't seem that natural of a solution:

// app/Http/Requests/ProcessRefund.php

/**
     * Get custom messages for validator errors.
     *
     * @return array
     */
    public function messages()
    {
        $messages = [];

        if (!is_null($this->input('refund_amount'))) {
            foreach ($this->input('refund_amount') as $id => $refundAmount) {
                $field = Field::find($id);

                if (!is_null($field))
                    $messages["refund_amount.{$id}.min"] = __('validation.custom.refund_amount.min', ['field' => $field->value]);
            }
        }

        return $messages;
    }
        

Here's the slightly modified translation hierarchy (no more .* after refund_amount, because it was considered as an other array level by the __() translation function):

// validation.php

'custom' => [
    'refund_amount' => [
        'min' => "The :field :attribute must be at least :min.",
    ],
],

Can anyone point me to a more "native" way to accomplish what I'm doing, or there's no other way at the moment ?

Thanks in advance,

• Jacob