manelgavalda

Just use where 2 times:

DB::table($this->tablex)->where('user_id', '=', Auth::user()->id)->where('product_id', '=', $slug)->delete();

In case you are overwriting a method, in your LoginController make sure that you are using the correct Request class,. On the top:

use Illuminate\Http\Request;

In case you are overwriting a method, in your LoginController make sure that you are using the correct Request class,. On the top:

use Illuminate\Http\Request;

Which problem do you have?

I don't think there's a command to actually remove it.

What you can actually do is to use git to track the changes that php artisan ui vue --auth does. So next time commit the changes before running the artisan ui command, and you will exactly know the changes.

So as for a solution to your problem you can actually create a new laravel project and commit the changes before running the artisan ui comand, this way you can see all the changes and remove them in your main project.

What problem do you have when doing it?

return response()->json([
    'error'=>false,
    'offers'=> serialize($newData)
]);

I don't know the error you are getting, but If you are getting a 500 error what do you want to see instead?

Hey, to make things easy I suggest you to just try with the first field, if it works we will add the last.

• First make sure that the name field is casted to json with the casts attribute in your normal model.

• Then do this directly in your nova Model:

Text::make('Name', function () {
    return optional($this->resource->name)->first;
})

This just works, if it doesnt, paste the code of your nova model, your migration and your normal model to see what's wrong.

I recommend you to use just a package. There's plenty of packages that do this, for example this one: https://github.com/Xethron/migrations-generator

If you need laravel 6 compatibility: https://github.com/oscarafdev/migrations-generator

I recommend you to use just a package. There's plenty of packages that do this, for example this one: https://github.com/Xethron/migrations-generator

If you need laravel 6 compatibility: https://github.com/oscarafdev/migrations-generator

You can use a normal where with carbon. I think something like this should do the job:

Order::with('users')
        ->where('created_at', '<=', now()->subMonth())
        ->get()

Edit: As @snapey pointed out you don't need the ->toDateTimeString() on the carbon instance.

I don't know if I understand it properly, but when you say that you want the records that the created_at + 1 month is less (older) than the date of today,

it's not the same thing as saying the records which the created_at is at least 1 month older than now?

You can use a normal where with carbon. I think something like this should do the job:

Order::with('users')
        ->where('created_at', '<=', now()->subMonth())
        ->get()

Edit: As @snapey pointed out you don't need the ->toDateTimeString() on the carbon instance.

Sure, you can use multiple databases on your laravel app, docs: https://laravel.com/docs/6.x/database#using-multiple-database-connections

There's a closed github issue about this on the package, so it will probably be worth it to take a look as there are many solutions: https://github.com/yajra/laravel-oci8/issues/506

If you are getting this error is probably because one of your db record doesnt have a correct name field.

If it's a collection you can use the optional operator for example, to avoid the error:

    return optional($this->name)->first . ' ' . optional($this->name)->last;

Is your json field correctly casted? Something like, in your model:

protected $casts = [
     "name" => "array"
];

Then access it like an array (using my way or @musa11971 way):

    return $this->name['first'] . ' ' . $this->name['last'];

If you are still getting this error make sure that the json field is not null or not correctly formatted.

I suggest you to use a custom accessor.

Firstly add this in your app model:

getFullNameAttribute() {
    return $this->name->first . ' ' . $this->name->last;
}

Then in your laravel nova model access it like this:

Text::make('FullName', 'full_name')
    ->exceptOnForms(),

That's the problem, that companyId is an array. Then it retrieves a collection with 2 items. So you need to do ->section() on a item in the collection not in the collection itself.

For example if you want to get the section from the first item use first():

echo($this->find($companyId)->first()->section);

That's the problem, that companyId is an array. Then it retrieves a collection with 2 items. So you need to do ->section() on a item in the collection not in the collection itself.

For example if you want to get the section from the first item use first():

echo($this->find($companyId)->first()->section);

Your relationship seems correct. What is the value of $companyId? If you are not passing an integer to find it will return a collection, so companyIdis not a company id.

$this->find($companyId) is returning you a collection not a single Company instance:

echo($this->find($companyId)->first()->section()->get());

Show the result of dd($companyId) to see what it is

He defines the foreign key using Sequel Pro before going to laravel but the normal thing will be to define it in the laravel migration.

First of all add the field relation on your people model:

<?php

namespace App;

use Illuminate\Database\Eloquent\Model;

class People extends Model
{
    protected $fillable = [
        'name', 'address', 'phone', 'email'
    ];

    public function fields()
    {
        return $this->hasMany(Field::class);
    }
}

Create a Field model (and the migration) with your field title, your type, value of the field, and person_id :

<?php

namespace App;

use Illuminate\Database\Eloquent\Model;

class Field extends Model
{
    protected $fillable = [
        'name', 'type', 'value', 'person_id'
    ];
}

Then when you are going to save the values, you can do this:

        $fields = [
            new Field(['name' => 'field_1', 'type' => 'string']),
            new Field(['name' => 'field_2', 'type' => 'text']),
            new Field(['name' => 'field_3', 'type' => 'integer']),
            new Field(['name' => 'field_4', 'type' => 'longText']
        ];

        $person->fields()->saveMany($fields);

Then you can update the values or acces them via the relationship

$person->fields()->where('name', 'field_1')->update('value', 'yourvalue');
$person->fields->firstWhere('name', 'field_1') // yourvalue

You can add an erorr bag property on your request classes.

 protected $errorBag = 'firstForm';

Because what you are trying to do it's not possible.

If you want dynamic fields for your model you need to have one table with the model, another with the fields and a relation between them, so each model can have many fields, and you can create them on the fly.

$model -> hasMany -> fields

That's 2 tables minimum, then the fields table will be something like this:

• title
• value

so in your model you can acces the fields relation to see your dynamic fields value.

$model->fields->yourDynamicField

Then you can use the excel or whatever you want to create the dynamic fields.

From docs https://laravel.com/docs/5.8/validation#named-error-bags :

return redirect('register')
            ->withErrors($validator, 'login');

{{ $errors->login->first('email') }}

What do you mean by dynamic fields? If you want to set all table fields as fillable without adding it to the fillable attribute, you can use the guarded attribute instead:

protected $guarded = [];

There's a closed github issue about this on the package, so it will probably be worth it to take a look as there are many solutions: https://github.com/yajra/laravel-oci8/issues/506

Same error using phpmyadmin. In my case I used the terminal:

mysql -u root -proot tutorial < sakila-db/sakila-schema.sql

Then do the same when importing the data, but change the use sakila database statement in the beginning of the file first, and then import the data:

mysql -u root -proot tutorial < sakila-db/sakila-data.sql

If nobody changed the default views path, it should be the file resources/views/partials/input.blade.php

If you want to update the last_login value just if it doesnt have one, you can do something like this:

protected function authenticated(Request $request, $user)
{
        if (is_null($user->last_login_at)) {
            $user->update(['last_login_at' => now()]);

            return redirect('admin/customers/create');
            // and laravel will then handle the redirect
        }
}

You can do it like this, for example:

DB::table('visitor_count')->get()->groupBy('user_ip')->count()

If you don't want the user to select options of the dropdown, you can use the disabled attribute. Open your partials.input partial to see the best way to implement it.

Can you show the whole Vue component and see how you added the sweet alert modal.

Mm, I tried the example above and it should work. The checkboxValue should be null because it's initialized to null, but the checkboxChecked property should return a boolean if the chekbox is checked or not, so I'm not quite sure what the problem is.

You can take a look at the docs also: https://fr.vuejs.org/v2/guide/forms.html#Checkbox

What problem are you having?

One way would be to add a v-model attribute and then use a watcher on it if you want to do something when the value changes:

...
<input type="checkbox" class="form-check-input" id="exampleCheck1" :value="checkboxValue" v-model="checkboxChecked"> </td>
...
data: () => ({
    checkboxValue: null,
    checkboxChecked: null
})
...
watch: {
    checkboxChecked(checkboxChecked) 
    {
        console.log(checkboxChecked)
        console.log(this.checkboxValue)
    }
},

I want to see the storemethod for your ProfileController, and also the html where you are calling the documentmodal_store route.

You are showing the destroy method not the store method. And also show you blade to see how are you calling this route.

I don't understand what you are trying to do, if you need to store an arrayinto a integer field, it would not work.

If you want to save an array into the database you can use a string field, and then making use of data casting so you can retrieve it as an array easly.

When you are doing this:

$dispatch->sub_jobs()->attach($sub_job_ids, ['qty' => $sub_job_qtys, 'description' => $sub_job_descriptions]);

What do you expect to save, 1 row, or many rows depending on the length of the array?

Show us your store controller method, and your view to see how are you calling it.

This problem is saying that your controller expects 1 parameter and you are not passing it, so your route definition and controller are good. If you are doing something like this:

<a href="{{route('documentmodal_store',$list->pg_id)}}"></a>

Make sure that $list->pg_id is not null.

When you do this:

$sub_job_qtys = $job->sub_jobs->pluck('qty');

You are getting an array with the plucked values, so you are trying to insert an array on an integer field. What are you trying to do?

The resource routes will automatically create the route pattern with the variables in place, so you don't need to add the $id in the route:

Route::resource('pg/document', 'pages\DocumentController')
->names(['store'=>'documentmodal_store','destroy'=>'document_delete']);

$bookings is a collection, so you need to encode it to json in order to pass it to your Vue component:

<booking :bookings="{{ json_encode($bookings) }}"></booking>

Show us some code please.

The laravel versions depends on the project, so if you are working on the same project in your house and office the version won't change, the only problem will be the PHP version. If you are actually working with the laravel 6.2 you will have problems when you try to work with the same project at home, but if you work with the 5.8 version, you can work in both places without a problem.

Hey, $accounts its a collection so you need to first pull one account to get the property. What are you trying to do?

You can chose between the implode or the foreach, not both at the same time:

• If you want to show all the roles separated by commas you can use this:

    {{ $user->getRoles()->implode(', ')  }}

This will actually convert your collection ([ "RoleName1", "RoleName2" ]) to a string separated by commas (RoleName1, RoleName2).

• The other option is to use the foreach, so you will list each individual role:

@foreach($users as $user)

    {{ $user->name }}

    @foreach($user->getRoles() as $roleName) // If you use this method remove the `implode`
          {{ $roleName}}
    @endforeach

@endforeach

Cool, glad it worked! Please mark it as solved, so other people will know.