Laracasts Member Profile

Jan

5 months ago

Replied to Adding Props On Component Won't Pass It Down

Not 100% sure as I have been working with a different Javascript library recently and am a bit rusty on Vue, but does the below work for the class?

<button class="'btn btn-'" :class="button_class" @click="submit">{{button_title}}

Replied to Recursive Select Option Dropdownlist

@noblemfd

I think you would need to do something like this since it is loaded via this relation $managers = Staff::all();

               @if($managers->managers->count() > 0 )
                 @foreach($managers->mangers as $manager)
                   <option value="{{$manager->id}}">{{$manager->fullName}}</option>
                 @endforeach
               @endif
          </select>

To make it more readable, you may want to just load the managers directly like: $managers = Manger::all(), then it should work as you originally expected.

Awarded Best Reply on How Can I Set The Default Value Laravel <select> Element?

@oxbir

Since the Product can have many Categories per your relationship and the pivot table implication, you would have to use an in_array method (or something similar) like:

            @foreach($categories as $category)
                <option value="{{ $category->id }}" {{ (in_array($category->id, $product->categories->pluck('id')->toArray()) ? 'selected' : '' }}>{{ $category->name }}</option>
            @endforeach

Does each Product possibly belong to many different Categories? Or does each Product belong to one Category? Because if the later is true, then you would have to adjust your relationship to a oneToMany as opposed to the current manyToMany with the pivot table.

Replied to How Can I Set The Default Value Laravel <select> Element?

@oxbir

Since the Product can have many Categories per your relationship and the pivot table implication, you would have to use an in_array method (or something similar) like:

            @foreach($categories as $category)
                <option value="{{ $category->id }}" {{ (in_array($category->id, $product->categories->pluck('id')->toArray()) ? 'selected' : '' }}>{{ $category->name }}</option>
            @endforeach

Jan

5 months ago

Replied to Hashing And Storing Large Data In MySQL Database,

@gouseferoz

You said:

I am trying to hash my data before saving it to the database mainly to: 1) Save the size of the data being saved - If you are going to save large lines of data 2) Security.

Only point two (2) really makes sense. As @tray2 said, encrypting is not a space saving mechanism, it is for security purposes only. If you are trying to be storage-conscious, which is always a good idea, maybe you can only encrypt the sensitive data, as opposed to encrypting the whole DB. To do so, consider using an Encyptable Trait. It's not too difficult to set up on your own but if you prefer a package, here is one that looks pretty straightforward:

https://github.com/gregoryduckworth/Encryptable

Jan

6 months ago

Replied to Passing Hidden Field Value Back To Livewire Component Is Null

Sorry, I missed that line in your original reply.

Did you include the below@livewireAssets in the head of your base layout template?

<head>
 // other stuff... 


    @livewireAssets
</head>

Replied to Passing Hidden Field Value Back To Livewire Component Is Null

@wallyj

Did you also change the property on your class?

public $deal_id;

public $dealId;

Awarded Best Reply on Data Is Not Deleted ?

@neeraj1005

You may have to tweak this a bit, but something like:

                      <td>

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

                        <button type='submit' class="btn btn-primary btn-block"><b>Delete</b></a>

</form>
                      </td>

Replied to Data Is Not Deleted ?

@neeraj1005

You may have to tweak this a bit, but something like:

                      <td>

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

                        <button type='submit' class="btn btn-primary btn-block"><b>Delete</b></a>

</form>
                      </td>

Replied to Data Is Not Deleted ?

@neeraj1005

You usually have to use a form (or an AJAX request) with a spoofed Delete method as opposed to an anchor tag, because the anchor will use a Get method.

The Route Resource expects the following per the docs:

Verb    Path    Action  Route Name
GET /photo  index   avatar.index
GET /photo/create   create  avatar.create
POST    /photo  store   avatar.store
GET /photo/{photo}  show    avatar.show
GET /photo/{photo}/edit edit    avatar.edit
PUT/PATCH   /photo/{photo}  update  avatar.update
**DELETE    /photo/{photo}  destroy avatar.destroy**

Replied to Passing Hidden Field Value Back To Livewire Component Is Null

@wallyj

Oh, sorry about that. I see what you're saying. Perhaps it has something to do with the snake_case? In the examples I have seen, and it my own Livewire test apps, I have always used camelCase

Replied to Passing Hidden Field Value Back To Livewire Component Is Null

@wallyj

In the hidden field, it appears you are using the incorrect variable name:

<input type="hidden" name="deal_id" id="deal_id" value="{{ $deal['id'] }}" wire:model="dealid">

Try changing it to:

<input type="hidden" name="deal_id" id="deal_id" value="{{ $deal['id'] }}" wire:model="deal_id">

Replied to Model Static Events On Boot Slow Together When Update Slug

@kris99

Does the updated, below, work by itself?

        static::updated(function ($model) {

            $model->generateSlug();

        });

I would think it would cause an endless loop because it would, of course, be called when a model is updated. But then, in the generateSlug method, when you call $this->save() the static::updated method would be called again, leading to an infinite loop.

Replied to Laravel 5.0 To 5.5 Upgrade, Session Flash Messages Not Working

I may have been barking up the wrong tree in my prior answer. I'm actually thinking it's an issue with how you are sharing the view, i.e. below in your Base controller:

if (Session::has('flash_warning')) {
        View::share('flash_warning', Session::get('flash_warning'));
    }

Try this instead (from the docs):

Occasionally, you may need to share a piece of data with all views that are rendered by your application. You may do so using the view facade's share method. Typically, you should place calls to share within a service provider's boot method. You are free to add them to the AppServiceProvider or generate a separate service provider to house them:

<?php

namespace App\Providers;

use Illuminate\Support\Facades\View;

class AppServiceProvider extends ServiceProvider
{
    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        View::share('key', 'value');
    }

    /**
     * Register the service provider.
     *
     * @return void
     */
    public function register()
    {
        //
    }
}

Replied to Laravel 5.0 To 5.5 Upgrade, Session Flash Messages Not Working

@lauriek

The docs from 5.0 state the below (which is what you have)

Sometimes you may wish to store items in the session only for the next request. You may do so using the Session::flash method:

Session::flash('key', 'value');

But the 5.5 docs display it slightly differently, see below:

Sometimes you may wish to store items in the session only for the next request. You may do so using the flash method. Data stored in the session using this method will only be available during the subsequent HTTP request, and then will be deleted. Flash data is primarily useful for short-lived status messages:

$request->session()->flash('status', 'Task was successful!');

While they appear to be equivalent, just using a helper versus a Facade, try replacing your flash message creation in the controller with the above ^^^

Replied to WhereIn In Query Doesn't Work For Array, Any Solution?

Hi @manjumjn

A couple of things I noticed. First, I don't see any return statements. Second, shouldn't the fallback value of your null coalescing operator be false as opposed to null? Or, just use the PHPissetfunction as, per the docs it will:

isset — Determine if a variable is declared and is different than NULL

I actually haven't seen null coalescing operator used in conjunction with the when clause before. Traditionally, you see a more direct comparison like below:

$query->when($filters['subjects'] === true, function ($query) {
    return $query->...
});

Below is my suggestion:

public function scopeFilter($query, array $filters)
    {
        $query->when(isset($filters['subjects']), function ($query, $data) {
            //Subjects ids will be comma seperated string eg : 127,125
            $subject_array = explode(',', htmlspecialchars_decode($data));
            return $query->where(function ($query) use ($subject_array) {
                $query->whereIn('subjects_ids', $subject_array);
            });
        })->when(isset($filters['topics']), function ($query, $data) {
            //topics ids will be comma seperated string eg : 127,125
            $topic_array = explode(',', htmlspecialchars_decode($data));
            return $query->where(function ($query) use ($topic_array) {
                $query->whereIn('topics_ids', $topic_array);
            });
        })->when(isset($filters['search']), function ($query, $search) {
            return $query->where(function ($query) use ($search) {
                $query->where('name', 'like', '%'.$search.'%');
            });
        });

    }

Awarded Best Reply on Laravel Policies

@glenuk

Ah, I see what you are saying. Per the docs

As previously discussed, some actions like create may not require a model instance. In these situations, you should pass a class name to the authorize method. The class name will be used to determine which policy to use when authorizing the action:

Try the below:

public function export(Request $request)
{

    // pass class name
    $this->authorize('export', PurchaseOrder::class);

    $data = $request->validate([
       'dateFrom' => 'required|date',
       'dateTo' => 'required|date',
        'statuses' => 'required|array',
    ]);

    return (new PurchaseOrdersExport($request->dateFrom, $request->dateTo, $request->statuses))->download('PurchaseOrders.'.$request->file_format);
}

Replied to Laravel Policies

@glenuk

Ah, I see what you are saying. Per the docs

As previously discussed, some actions like create may not require a model instance. In these situations, you should pass a class name to the authorize method. The class name will be used to determine which policy to use when authorizing the action:

Try the below:

public function export(Request $request)
{

    // pass class name
    $this->authorize('export', PurchaseOrder::class);

    $data = $request->validate([
       'dateFrom' => 'required|date',
       'dateTo' => 'required|date',
        'statuses' => 'required|array',
    ]);

    return (new PurchaseOrdersExport($request->dateFrom, $request->dateTo, $request->statuses))->download('PurchaseOrders.'.$request->file_format);
}

Replied to Laravel FirstOrCreate With Multiple Attributes

@phoenix5

@tykus answer above is right. So in your case, you would include all necessary items to check for the existence of the the models in the first argument and then, if a model cannot be found with those details, a new model will be created with them. So something like the below:

$log_pn = Log_panne::firstOrCreate(['n_s' => $request->get('n_serie'),'panne_id' => $panne_id]);

And then you wouldn't really need the balance of the below code as the model would already be saved to the DB with the items:

// don't need... 
$log_pn->n_s = $request->get('n_serie');
$log_pn->panne_id = $panne_id;
$log_pn->save();

Jan

6 months ago

Replied to Laravel Policies

Hi @glenuk

I'm with @kevinbui on this. Double check the Array Intersect function info from the PHP manual, below:

array_intersect() returns an array containing all the values of array1 that are present in all the arguments.

Because you are passing an empty array as the second parameter, array_intersect will always return an empty array, whose count will always be zero (0).

Replied to Get Lastest Rows Of Duplicates

@drissboumlik

Sorry, I should be testing these things but I have been quite but lately. The above code is calling the only method on a "non-collection". Try this instead:

App\Stat::all()->only('Id_Externe', 'Date_Heure_Note')->duplicates('Date_Heure_Note');

Jan

6 months ago

Replied to Get Lastest Rows Of Duplicates

@drissboumlik

Yep, I should have probably used only not get. See below. That doesn't quite explain the error you're getting, but it may resolve it.

App\Stat::only('Id_Externe', 'Date_Heure_Note')->duplicates('Date_Heure_Note');

Replied to Group Collection Info

Oh, sorry, perhaps it's weekOfYear and not just week. Also no need for the method parentheses (). Check out the docs: https://carbon.nesbot.com/docs/#api-getters


$groupedCollection = $payed->only('quantity', 'DueDate', 'TotalValue')->groupBy(function ($item){
    return Carbon::parse($item->DueDate)->weekOfYear;
});

Replied to Group Collection Info

How about something like the below? Just a heads up, this will not take into account the Year of the DueDate but per your requested format above, that doesn't seem to matter.



$groupedCollection = $payed->only('quantity', 'DueDate', 'TotalValue')->groupBy(function ($item){
    return Carbon::parse($item->DueDate)->week();
});

Replied to Group Collection Info

@conixs

What were the results when you tried the above groupBy collection method? And don't forget that the groupBy collection method, like most other collection methods, does not affect the original collection, so you have to assign it to a new var, like below:

$groupedCollection = $payed->groupBy(function ($item){
    return Carbon::parse($item->DueDate)->format('Y-m');
});

Replied to How To Solve This Error; Invalid Argument Supplied For For Each()

@icelander

My guess is that it is this line:

@foreach($order->cart->items as $item)

I didn't see $items assigned in the controller method. Try the below instead:

@foreach($order->cart as $item)

Awarded Best Reply on Laravel Blade Directives Auth

I like @emadiga solution. But I think it would be an or statement as opposed to an &&

@if(Auth::guard('web')->check() || Auth::guard('student')->check())
// Your logic here
@endif

mstrauss

Start Your Engines

First Thousand

One Year Member

Two Year Member

Three Year Member

Four Year Member

Five Year Member

School In Session

Welcome To The Community

Full Time Learner

Pay It Forward

Subscriber

Lifer

Laracasts Evangelist

Chatty Cathy

Laracasts Veteran

Ten Thousand Strong

Laracasts Master

Laracasts Tutor

Laracasts Sensei

Top 50

Want us to email you occasionally with Laracasts news?