manelgavalda

@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?

Hey, i don't quite understand what you are trying to do, can you show us more code?

The problem is that $this references a collection instance, not an item inside the collection.

For example in case you want to work with the first item:

return parent::toArray([
    'name' => $this->first()->name,
    'industry' => $this->first()->industry
]);

Hey, you can create the class path before the new. So something like this should work:

    $class = "Database\Seeds\\{$request->seederFile()}"; // notice the \\ before the variable

    $wSeeder = new $class;

    $wSeeder->run($request->page_id, $wSorting);

Hey, looks like auth()->user() is returning null on the view, are you sure that you have are authenticated in the application?

If it's not getting the configuration from your .env, maybe the configuration cached, try this:

php artisan config:clear

Hey, I'm also using laravel 5.8 and I don't think the way of executing tests has changed.

What is the error you are having when executing vendor/phpunit/phpunit/phpunit?

I suppose that you just need to check if po is null in order to know if $po_item has po:

<td>{{$po_item->vendor_company->name}}
   @if($po_item->po) //remove ->id
     <a href="{{route('employee.po.show', $po_item->po->id)}}"> PO No : {{$po_item->po->id}}</a> 
    @endif
</td> 

If you go to the main page you can see this 2 courses for new users:

• https://laracasts.com/series/object-oriented-bootcamp-in-php
• https://laracasts.com/series/laravel-from-scratch-2018

The first one is PHP from 0, so I suggest you to start it first, the second one is laravel from 0, because laravel is a PHP language you will need to know the PHP basics so if you know nothing about PHP start with the first course.

@CHRISGRIM - You can pass a closure to the loaded class, and maybe this will work for you:

$category = $category->load(['events' => function ($query) {
    $query->whereNotNull('approved');
}])->get();

Does it work?

You can use whereHas for this:

$category->whereHas('events', function($query) {
    $query->where('approved', Null);
})->get();

Docs: https://laravel.com/docs/5.8/eloquent-relationships#querying-relationship-existence

@AGILASADI - Glad it worked!

@AGILASADI - Yes, nice. Are you sure that now you are getting the same error as before?

@AGILASADI - Do you see the extension if you use php --ini?

• moontoast/math 1.1.2 requires ext-bcmath * -> the requested PHP extension bcmath is missing from your system.

You need to install the php bcmath extension. If you are on linux you can do this:

sudo apt-get install php7.2-bcmath

Maybe I got the question wrong, if you just want a way to create a record in the table, you can do this:

Foo::create([
    'field' = 'value',
    'field2' = 'value'
])

Hey, yep you can use the keyword self or static to reference the own class, so this will be the same:

$foo = new self;
$foo = new static;
$foo = new Foo;

In your example self, static and Foo will be the same, but static and self, have some differences, you can see the differences in the exemples in the docs: https://www.php.net/manual/en/language.oop5.static.php

@BEHNAMPMDG3 - You can inject the request or not, so it doesn't need to be a parameter in the method.

For example, In the first exemple you are injecting the request in the method, so it gets automatically resolved on your controller without looking the parameters you are passing in your route, so your route will just add the parameters that aren't injected ($slug):

public function login(Request $request, $slug)
    {
        dd($request); // the request with the data

        return view('login');
    }

If you are not injecting the request in the method you can also use the request() helper, so you don't need to import the Request class, or inject it in the controller, but the functionallity is the same:

public function login($slug)
    {
        dd(request()); // the request with the data

        return view('login');
    }

I suggest you to read the docs, you can see the same example with the request, and how method injection works: https://laravel.com/docs/5.8/controllers#dependency-injection-and-controllers

Show us the code, what kind of problem do you have? If your relationship are properly defined you can do this i suppose: Eager load the relation so you won't have a n+1 problem:

// controller
$posts->with('user');

// view
@foreach($posts as $post)
    {{ $post->user->name }}
@endforeach

I use this package, it creates the laravel migrations from an existing DB, it works pretty well: https://github.com/Xethron/migrations-generator

The request is automatically injected to the controller (Request $request), you need to also pass the slug as another parameter in order to see it:

public function login(Request $request, $slug)
    {
        dd($slug);

        return view('login');
    }

Or if you are not using the $request just remove it:

public function login($slug)
    {
        dd($slug);

        return view('login');
    }

I guess you can use has in order to check if the relation has items:

$articles = App\Article::has('categories')->get();

Or if you want to specify the categories yourself you can use whereHas:

$articles = App\Article::whereHas('categories', function ($query) use ($categoriesIds) {
    $query->findMany($categoriesIds);
})->get();

Docs: https://laravel.com/docs/5.8/eloquent-relationships#querying-relationship-existence

Hey, you are not passing the data to the view properly:

public function index()
{
    $file = new files();
    $file = $file->get()->toArray();
    return view('imgBlade.imgPage', ['file' => $file]);
}

Docs: https://laravel.com/docs/5.8/views#passing-data-to-views

Hey,

• The first one {{ }} renders the data and scapes it in your html file to prevent XSS attacks:

Hello, {!! $name !!}. // $name can be "<b>Jhon</b>" and it will be rendered as the same (<b>Jhon</b>)

• By default, Blade {{ }} statements are automatically sent through PHP's htmlspecialchars function to prevent XSS attacks. If you do not want your data to be escaped, you may use the following syntax. So the {!! !!} it is usefull when you want to render html for example:

Hello, {!! $name !!}. // $name can be "<b>Jhon</b> and it will be rendered as Jhon (with bold text)"

From docs: https://laravel.com/docs/5.8/blade#displaying-data

Hey, this is PHPStorm functionallity. In your image you can see that he is using PHPStorm in the top left corner.