table liste whith laravel

@chagouani relations like this $intervention->technicien->user->nom or $intervention->client->user->nom are often causes this kinda errors . use the optional() helper. try like below

<td>{{optional($intervention->technicien->user)->nom}}</td>
<td>{{optional($intervention->client->user)->nom}}</td>  

docs http://laravel.test/docs/5.6/helpers#method-optional

thank you for your answer but the same problem

it should work @chagouani try to hard refresh the browser(ctrl+f5). why in foreach loop the same variable twice? $intervention as $interventionit should be $interventions as $intervention or $intervention as $item! it will not work with this $intervention as $intervention

first , this line is bad

@foreach($intervention as $intervention)

it should have dfferent variable names, line $interventions as $intervention ... check the S in the first one.

second ... probably one of this lines are giving you a "NULL value in the middle" making the relation to fail.

<td>{{$intervention->technicien->user->nom}}</td>
<td>{{$intervention->client->user->nom}}</td>

maybe the raltion fails on the first arrow (->), or the second, ... etc. , so ... start an old school debug process ... how? just try the different relations on them like so ...

One at the time, what you want to know is wich relation is failing and where so delete one of the items, and start with the first one only, if completed, ... continue with the next one.

in some point of this, you will see the NULL or empty value that is causing the failure, ... if is not in the first it will appear in the second.

do

<td>{{$intervention->technicien}}</td>
<td>$intervention->client->user->nom </td>

then

<td>{{$intervention->technicien->user}}</td>
<td>$intervention->client->user->nom </td>

then

<td>{{$intervention->technicien->user->nom}}</td>
<td>$intervention->client->user->nom </td>

did it show up? .. no ? ok move to the second

<td>{{$intervention->technicien->user->nom}}</td>
<td>{{$intervention->client }} </td>

<td>{{$intervention->technicien->user->nom}}</td>
<td>{{$intervention->client->user}}</td>

<td>{{$intervention->technicien->user->nom}}</td>
<td>{{$intervention->client->user->nom}} </td>

did you find the one that is making your relation to fail?

PD: there are more suitable ways to handle this, but .... this will help you understand a basic and horrible debugging workaround.

@rin4ik he always shows the same mistake whith changed $interventions as $intervention

@chagauni please try to clear everything from index file and see something changes? did you try these lines below ? you shouldn't see that error

<td>{{optional($intervention->technicien->user)->nom}}</td>
<td>{{optional($intervention->client->user)->nom}}</td>  

@jcmargentina the 2 works alone but when I put them together, I get the same error

@rin4ik where I find the index file .........................................

@chagouani , ... I am totally confused, how can they work separatly and when you put them together they crash? ... WTF? LOL LOL LOL, I really want to solve this puzzle.

intervention\index.blade.php

@rin4ik delete all the code in the page index.blade.php and I put the code it displays this error

Property [technicien] does not exist on this collection instance. (View: C:\xampp\htdocs\projet\resources\views\intervention\index.blade.php)"

@chagouani , just leave the ...

@foreach($interventions as $intervention)
                <tr>
                                    <td>{{$intervention->technicien->user->nom}}</td>
                                    <td>{{$intervention->client->user->nom}}</td>
                </tr>
 @endforeach 

@jcmargentina 1st thing I do not know why you laugh 2nd thing you want to check I can send you a picture or a video to help you to solve this puzzle

@jcmargentina

always the same

@chagouani do you have that relation technicien in your Intervention model?

what this gives you try please

@foreach($interventions as $intervention)
                <tr>
                                    <td>{{optional($intervention->technicien->user)->nom}}</td>
                                    <td>{{optional($intervention->client->user)->nom}}</td>
                </tr>
 @endforeach 

come on ... dont be so sensitive, I am not laughing at you my friend, I am laughing at the problem, dont take that expression personally :D

try this ... remove everything from your view ... leave it blank .

and check it again .

maybe the problem is in the controller ... maybe.

can you provide the controller code ?

@rin4ik I add the model and the controller in my code

@jcmargentina ok sorry I tried but still the same problem and I add the model and control in my code

can you please check this code ?

 public function index()
 {
    
    $Listintervention=intervention::with(['technicien','client','tarificationtache'])->get();
    
    return view('intervention.index',['interventions'=>$Listintervention]);

  }

should it be ...

//with capital i 
$Listintervention=Intervention::with(['technicien','client','tarificationtache'])->get();    

I assumed you added the Intervention model at the top your controller code first

here you should change them all. class name always should be with capital letter.

return $this->belongsTo(technicien::class);

to this

return $this->belongsTo(Technicien::class);

--

 $Listintervention=intervention::with(['technicien','client','tarificationtache'])->get();

++

 $Listintervention=Intervention::with(['technicien','client','tarificationtache'])->get();

--

    return $this->belongsTo(tarificationtache::class);

++

 return $this->belongsTo(Tarificationtache::class);

go 1 step at the time

@jcmargentina still the same problem

so .. is not in the view ... I already sent you a fix in the controller (keep it) and stil the same ... IS THE RELATION!!!!!

specify the fields in the realtionship ...

return $this->belongsTo(technicien::class, field_origin, field_destiny);

/*
or

return $this->belongsTo(Technicien::class, field_origin, field_destiny);

depending on your code

*/

can you please show your databse tables? for Intervention and Technicien?

did you follow the convention names when you named the fields? ... just in case explicitly name them in the relation

@rin4ik I dont know why he works each one alone and when I put them together, I dont think it's a model problem.

technicien and client model has this relation?

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

intervention table

<?php
use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class CreateInterventionsTable extends Migration
{
    /**
    * Run the migrations.
     *
    * @return void
     */
 public function up()
 {
    Schema::create('interventions', function (Blueprint $table) {
        $table->increments('id');
        $table->date('date_intervention');
        $table->string('description');
        $table->dateTime('duree_prevu');
        $table->boolean('statut');
        $table->integer('technicien_id')->unsigned();
        $table->foreign('technicien_id')->references('id')->on('techniciens');
        $table->integer('tarification_id')->unsigned();
        $table->integer('client_id')->unsigned();

        $table->timestamps();
    });
   }

    /**
     * Reverse the migrations.
     *
  * @return void
     */
 public function down()
    {
        Schema::dropIfExists('interventions');
    }   
}

technicientable

<?php

use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class CreateTechniciensTable extends Migration
{
/**
         * Run the migrations.
     *
     * @return void
    */
    public function up()
  {
    Schema::create('techniciens', function (Blueprint $table) {
        $table->increments('id');
        $table->boolean('actif')->default(1);
        $table->float('moyenne_avis');
        $table->integer('user_id')->unsigned();
        $table->foreign('user_id')->references('id')->on('users');
        $table->datetime('deleted_at')->nullable();
        $table->timestamps();
        
    });
 }

 /**
    * Reverse the migrations.
     *
     * @return void
     */
 public function down()
 {
    Schema::dropIfExists('techniciens');
    $table->dropColumn('deleted_at');
 }
}

client table

<?php

use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class CreateClientsTable extends Migration
{
  /**
    * Run the migrations.
    *
    * @return void
     */
    public function up()
    {
    Schema::create('clients', function (Blueprint $table) {
        $table->increments('id');
        $table->integer('user_id')->unsigned();
        $table->foreign('user_id')->references('id')->on('users');

        $table->timestamps();
    });

  }

    /**
  * Reverse the migrations.
     *
     * @return void
  */
 public function down()
 {
    Schema::dropIfExists('clients');
  }
}

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

@chagouani this one works

                                  <td>{{$intervention->client->user->nom}}</td>

this isn't?

                       <td>{{$intervention->technicien->user->nom}}</td>

edit every "belongsTo" relation in the models involved in this problem for example as this ...

 public function technicien()
    {
    return $this->belongsTo(technicien::class)->withDefault([]);

    }

see the withDefault() ??? add that to every "belongsTo" relation in the models involved and check again if we can mitigate the error ... at least