manelgavalda

Hey, If you are already familiar with Vue devtools, you can actually use livewire-devtools: https://github.com/beyondcode/livewire-devtools , as they have the same functionallity

You can also use $this->post->refresh() to re-hydrate the Post model using fresh data from the database.

Docs: https://laravel.com/docs/8.x/eloquent#retrieving-models

I think the /{user} route is overwriting your /create route, you need to change the order:

Route::prefix('users')->group(function () {
        Route::get('/', '[email protected]')->name('admin.users');
        Route::get('/{user}', '[email protected]_user')->name('admin.users.view');
        Route::post('/create', '[email protected]_user')->name('admin.users.create');
        Route::post('/{user}/edit', '[email protected]_user')->name('admin.users.edit');
        Route::post('/{user}/delete', '[email protected]_user')->name('admin.users.delete');
});

• You can create another model class with your method inside.
• Then extend the eloquent model class from it.
• And finally let all your models extend your custom model class.

// Your custom model.
<?php

namespace App;

use Illuminate\Database\Eloquent\Model as EloquentModel;

class Model extends EloquentModel
{
    public function customMethod()
    {
        //
    }
}

Your models

<?php

namespace App;

class ExampleModel extends Model
{
}

I would create 2 categories, and then just make sure that you can only see the first one (because the pagination):

$category1 = factory(Category::class)->create();

$category2 = factory(Category::class)->create();

$response = $this->get(route('categories.index'));

$response
	->assertSee($category1->name)
        ->assertDontSee($category2->name);

Just updated the example with categories.

I think you just need to install the dbaldriver now:

composer update
composer require doctrine/dbal

That's weird. I just copied the code, and it's working for me, which MySql version are you using?

You changed the 2 lines and you still have the same problem?

Hey, you have a typo on ->refrences in the 2 foreign lines:

 $table->foreign('contact_user_id')->references('id')->on('contact_users');

Hey, If you want to eager load the relationships everywhere, I would suggest using the $with property in your User model:

<?php

namespace App;

use Illuminate\Database\Eloquent\Model;

class User extends Model
{
    /**
     * The relationships that should always be loaded.
     *
     * @var array
     */
    protected $with = ['author'];

    /**
     * Get the author that wrote the book.
     */
    public function author()
    {
        return $this->belongsTo('App\Author');
    }
}

Docs: https://laravel.com/docs/7.x/eloquent-relationships#eager-loading

I think you just need to install the dbaldriver now:

composer update
composer require doctrine/dbal

Are you sure you have the mysql_pdo driver installed? Check your extensions file and make sure that it isn't commented and that it's installed. In your php.ini:

extension=php_pdo_mysql.dll

Is the configuration inside .env.testing/.env correct?

Hey, maybe you are missing the dbal driver:

composer require doctrine/dbal

I understand now. The redirect with and the view with, don't do the same.

• The redirect with puts the variable in the session.
• The view with passes the variable to the view.

You have some options here. Instead of passing the variable to the view, you can put it in the session, so the redirect and the view will work :

// Passing to session and returning the view.
session(['param1' => $param1]);

return view('Page1');

// Passing to session and redirecting.
return Redirect::back()->with('Param1', $Param1);

Then in your javascript access it like:

var Param1={!! Session::get("Param1") ?? '' !!};

You keep the access for the rest of the month.

I understand now. The redirect with and the view with, don't do the same.

• The redirect with puts the variable in the session.
• The view with passes the variable to the view.

You have some options here. Instead of passing the variable to the view, you can put it in the session, so the redirect and the view will work :

// Passing to session and returning the view.
session(['param1' => $param1]);

return view('Page1');

// Passing to session and redirecting.
return Redirect::back()->with('Param1', $Param1);

Then in your javascript access it like:

var Param1={!! Session::get("Param1") ?? '' !!};

Hey, with passes the variable to the view, not to the session, that's why the first option works.

You can also use this to access the variable in your javascript:

var Param1 = @json($Param1);

That's weird, I don't really know what else to do then, sorry.

You should put the name of the attribute in this array. In case you don't want to trim the name of the user:

protected $except = [
    'name'
];

Hey, in the TrimStringsmiddleware there's a property $exceptwhere you can add all the fields you want to save without being trimmed. If you want to do this for all the fields you can remove the TrimStrings middleware from Http/Kernel.

Hey skino, Yeah sure, you have a Download button on the episode link page, just right to the Watchlist button.

Hey skino, Yeah sure, you have a Download button on the episode link page, just right to the Watchlist button.

One option is to use View Composers, so you only need to define the variable you want to share once.

public function compose(View $view)
{
    $view->with('categories', $this->categories);
}

Docs: https://laravel.com/docs/7.x/views#view-composers

One option is to use View Composers, so you only need to define the variable you want to share once.

public function compose(View $view)
{
    $view->with('categories', $this->categories);
}

Docs: https://laravel.com/docs/7.x/views#view-composers

Normally you would use the web.php file. If you just want api routes (to use with axios for example) you can use the api.php file. It's just a matter of organizing routes you can visit the RouteServiceProvider to see the differences between the files.

Normally you would use the web.php file. If you just want api routes (to use with axios for example) you can use the api.php file. It's just a matter of organizing routes you can visit the RouteServiceProvider to see the differences between the files.