manelgavalda

What is StudentResource returning? Maybe it's returning an array so you need to do it like:

$studentInfos['firstname'];

Show us some code.

Maybe its a compilation problem:

composer dumpautoload

And

php artisan clear-compiled

How are you passing tripdetail to the view?

Hey, if you want to store the id of the user you select you need to provide a value attribute to the dropdown:

           <label for="formUsers"><b>User</b></label>
            <select class="form-control" id="formUsers" placeholder="Select Username">
             @foreach ($users as $user)
                    <option name="user_id" value="{{ $user->id }}">
                         {{ $user->name }}
                     </option>
             @endforeach
             </select>

Then you can access it in your controller and save it:

$attributes['user_id']= request('user_id');

I think the attribute name must be in the select tag, not in option:

           <label for="formUsers"><b>User</b></label>
            <select class="form-control" id="formUsers" placeholder="Select Username" name="user_id">
             @foreach ($users as $user)
                    <option value="{{ $user->id }}">
                         {{ $user->name }}
                     </option>
             @endforeach
             </select>

Hey, if you want to store the id of the user you select you need to provide a value attribute to the dropdown:

           <label for="formUsers"><b>User</b></label>
            <select class="form-control" id="formUsers" placeholder="Select Username">
             @foreach ($users as $user)
                    <option name="user_id" value="{{ $user->id }}">
                         {{ $user->name }}
                     </option>
             @endforeach
             </select>

Then you can access it in your controller and save it:

$attributes['user_id']= request('user_id');

Can you show us your composer.json? Looks like you are not loading the trait correctly.

Hey, looks like you are not importing the trait on the RepositoryCreatorTest class.

use Inz\Repository\Base\FakeStorageInitiator;

Yes,

In the first case you are always creating a User, even if you indicate a user_id when creating the User with the factory.

In the second case you are just creating the User if you don't indicate the user_id attribute. So you should use the closure way.

What you can do is this:

return [
        'user_id' => factory(User::class)
];

This way will work like the closure case, so if you want to simplify your code and at the same time be efficient you should use this way.

Hello, your namespace in your HondaMachine class has a typo:

namespace Ap\Car;

to

namespace App\Car;

Hello, your namespace in your HondaMachine class has a typo:

namespace Ap\Car;

to

namespace App\Car;

From docs ( https://laravel.com/docs/6.x/eloquent#eloquent-model-conventions ):

Note that we did not tell Eloquent which table to use for our Flight model. By convention, the "snake case", plural name of the class will be used as the table name unless another name is explicitly specified. So, in this case, Eloquent will assume the Flight model stores records in the flights table. You may specify a custom table by defining a table property on your model.

@THEBIGK - I think you need to load the relation with the events:

public function index()
{
    $events = Event::with('attendees')->where('start_date', '>', now())->paginate(30);

    return $events; // Testing
}

And maybe in your User model you will need to work with collections instead of the query builder:

    public function getAttendingAttribute()
    {
        return $this->attendees->where('user_id', '=', auth()->id()); // remove the () in attendees
    }

If the user can only have 1 role I don't think you need the user_roles table.

You can simply add a role_id column in your users table.

When the user gets redirected from the external server to your laravel server, you will have a new session, so before your laravel server redirects to the external server, you need "to pass" the session you had to the external server, and when the external server redirects you back to the laravel server you will have the session.

Finally, if you are redirecting to your laravel application from an external server, you should disable the csrf token validation: https://laravel.com/docs/5.8/csrf#csrf-excluding-uris

Hope this helps.

@FORTEIRP - Mm, if you are already displaying the data using {!! $post->body_html !!} it's weird that you still see the <p> tags, if the data is correctly saved in your database I don't understand what else can be wrong.

Hey, I tend to use franzliedke/studio, is pretty easy to use, you can see how it works here: https://github.com/franzliedke/studio

What you are showing in the screenshot and your code doesn't look the same thing.

In your create view you are using a class to create the textarea, so you don't need to use {!! !!}.

You probably want to show the unescaped text in your show view.

Hey, yep this is normal behavior.

When you use $request->user() you are getting an instance of User, so when you do $request->user()->first() you will get the first User.

This is not dangerous because if you are returning the $request->user() the user has no way of using ->first() after it.

Hey, I think you can use the not_in validation rule: https://laravel.com/docs/5.8/validation#rule-not-in

Maybe the different rule can also help you: https://laravel.com/docs/5.8/validation#rule-different

@MIHIRPATEL83 - Um, are you sure that you are hitting the Validator, in your controller, before creating the product?

Btw if you already have a custom request class to to do the validation, I think it will be just better to have the rules in your request class.

You can access the model from the request like this inside your ProductFromRequest:

$product = $this->route('product');

@RAVIAWASTI - Um, the easier thing will be for your android developer to access the first item of the array, or create a loop to show errors. If he doesn't know how to do it, then try something like:

    if ($validator->fails())
    {
        $errors = $validator->errors();

        if(array_key_exists('username', $errors)) {
            $errors['username'] = $errors['username'][0];  // Here you are getting the first item of the array and assigning it directly to "username" so it will be a string
        }

        if(array_key_exists('email', $errors) {
            $errors['email'] = $errors['email'][0]; //same as before.
        }

        return response()->json(['success'=>'0','post'=> $errors]);
    }

As I said that's a very ugly flx, but I suppose that something like this should work, in this specific case.

Hey, can you show us why do you want to do this? The reason why the username and email fields are returning and array, is because they can have more than 1 error, so I don't think it's a good practice to pass the array into a string.

What you can do in your blade is to access the first item on the array, so you will get the result you expect. If you have this:

{ "success": "0", "post": { "username": [ "The username has already been taken." ], "email": [ "The email has already been taken." ] } }

You can access the key accessing the first item on the array, so instead of accessing username to get the error, you will have to access username[0], and the same with the email.

Yeah , instead of defining the $class_template inside the command, you can create a stub with the customClass code and generate the class using that.

I think that's a good example of what you want to do: https://medium.com/@imfx/create-make-custom-commands-in-laravel-9fa002da582e

@RAVIAWASTI - They are surrended with curly braces {}, so they are both JSON objects https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Objects/JSON.

A JSON object can have nested JSON objects inside, that's why you have more {} inside.

And in the first case this JSON object has 2 arrays of 1 item inside:

[ "The username has already been taken." ] // First array
[ "The email has already been taken." ] // Second array

This format is called JSON, it's the most common format when working with apis.

If you want to see the data structured, you can use https://jsoneditoronline.org/ for example.

Hey, I'm not sure if I understand the question but maybe, instead of your app url being localhost:8080 you want something like your-app.test?

If that's the case you can use valet: https://cpriego.github.io/valet-linux/

Hey, this is not failing because $thread->slug is probably returning null, so your string looks like "/thread/1/" and your path() function doesn't even need to return the slug.

I think a better test for this would be something like:

public function a_thread_has_a_path()
{
    
    $thread = factory(Thread::class)->create([
        'slug' => 'your-slug'   // or fill the title column and get the slug from that, so you will know that the slug is generated correctly
    ]);

    $this->assertEquals('/thread/1/your-slug', $thread->path());
}

This way you will assure that the path you want is the expected.

You are having this error on your controller or in your blade? The code seems right so this may be a problem with cache or compilation. Try to run this commands:

php artisan cache:clear

composer du

Hey, there's not any convention on this, it's just a matter of your personal preference.

Personally i like to put the middleware on the route definition, so when i take a look at my routes file I can easly see which routes are protected by a middleware and I also like to wrap all the routes in a middleware group.

Taken from the docs https://laravel.com/docs/5.8/controllers#controller-middleware :

• Middleware may be assigned to the controller's routes in your route files.

• However, it is more convenient to specify middleware within your controller's constructor. Using the middleware method from your controller's constructor, you may easily assign middleware to the controller's action. You may even restrict the middleware to only certain methods on the controller class.

• Controllers also allow you to register middleware using a Closure. This provides a convenient way to define a middleware for a single controller without defining an entire middleware class.

Hey, this is actually another problem:

• PDOException::("SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES)"

The php-mysql driver is installed correctly, the problem now is that the credentials to connect to your mysql database are not correct.

Check out that your .env file is configured properly with your mysql credentials:

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE="your-database"
DB_USERNAME="your-user"
DB_PASSWORD="your-password"

@INDERSEIN

• Illuminate\Database\QueryException : could not find driver.

You are missing the mysql database driver now:

sudo apt-get install php7.2-mysql

@AFOYSAL - Hey, glad it worked, but it was @wobbie who provided the correct solution to your answer, so you can mark his answer as best, thanks.

• Problem 1 - phpunit/phpunit 7.5.x-dev requires ext-dom * -> the requested PHP extension dom is missing from your system.

You are missing the php xml-extension:

sudo apt-get install php7.2-xml

Here you can see the required extensions: https://laravel.com/docs/5.8/installation#server-requirements

@AFOYSAL - Here you are referencing the name of this relationship:

public function course()
{
    return $this->belongsTo(Course::class);
}

So you need to use the name of the relationship course, because a Semester belongs to one Course.

@AFOYSAL - The relationship name to retrieve the course of the semester is course, not courses:

public function index(Request $request, $domain) 
{ 
    $semesters = Semester::with('course')->get(); // change courses to course

    return response()->json(["semesters" => $semesters, "status"=>200]); 
}

If you want to check the redirect you need to have the exceptions enabled, so laravel can catch it and redirect you with a 302 response.

/** @test */
public function guests_cannot_manage_projects()
{
    $project = factory('App\Project')->create();

    $this->get('/projects')
        ->assertRedirect('login');
        
    ...
        
}

Hey, then the problem must be on the way you are calling the successPayment function. Looks like you are calling it multiple times, but just calling it correctly the first time. Can you show us the code you are using to call it?