bobbybouwmann

You need to install two default packages! You can find them in the upgrade guide on the master branch: https://laravel.com/docs/master/upgrade#upgrade-5.8.0

It's a relationship on the user model.

However you should watch the full series to get to know everything you saw in the first free video ;)

Is this a question or a notice?

Anyway, you probably need to configure recaptcha in the admin panel to use the correct url if you switch to https! You have to put in your url there, if that is still http it might not work ;)

Are you sure Storage::disk('public')->readStream($path); is returning anything for you? This should work as far as I can see!

The token guard doens't have an attempt method because the token itself is the authentication method and is used everytime during the request. That is different than session authentication.

If you use the api guard you also need a way to authorize the user itself. Laravel offers passport as a package for you to do this. However you can also build it yourself. Check this for more information: https://laravel.com/docs/5.7/authentication

Another option is this: https://gistlog.co/JacobBennett/090369fbab0b31130b51

I think you want the last option!

Well it's a front-end thing right? So you can do what even you want with in your web app :D

I reported it to Jeffrey ;) He will probably take it down!

Yeah, you can make a package with a command! Then you should be able to reuse it everywhere. Take a look at this: https://laravel.com/docs/5.7/packages#commands

Like the examples suggest you can get around the CloudFlare network because they also send the origin IP-address. A normal proxy doesn't do that for you, unless you tell them to do so!

So you can read another IP-address from some header from the request if it's available, but by default you can only get the host of the requester. In this case is that your proxy!

When then are using a proxy or a vpn you can't get the original IP-address, because that's why we have a proxies or a vpn :tada:

When you get a request from a browser you only their current IP-address and not everything else that was before that. The only way to get around this is either controlling the full internet or asking your users not to use a proxy or vpn ;)

You get this error when one of your variables is an array and you try to output it. For example

{{ ['one', 'two'] }}

Comment out some parts of your template to see where the error is ;)

@ABDULAZIZ - You can't! Because Laravel is caching the connection between the route and the controller that belongs to it. It can't cache a closure for you, because it's not executed code.

So you either can use callbacks or route caching, not both at the same time!

Documentation: https://laravel.com/docs/5.7/controllers#route-caching

Normally you would indeed register something in Laravel so the class is loaded for Laravel. However in this case this is a stand alone solution without specific Laravel support. So you can either create your own service provider for it register it properly in Laravel or you can use a third-party package that is doing this for you!

Laravel Ratchet Package: https://github.com/Askedio/laravel-ratchet

@abdulaziz It's never recommened to use route caching in your local environment! It might give you strange results. Also if you want to cache your routes in the future you should use closure based routes ;)

You need authorization for that. Laravel offers you policies and gates. They are perfect for this!

Documentation: https://laravel.com/docs/5.7/authorization

Jeffrey also made a tutorial about it! You should check that one out as well: https://laracasts.com/series/whip-monstrous-code-into-shape/episodes/7

This should put you in the right direction ;) Let me know if you have more questions or need examples

Auth::attempt will already log you in when you pass the validation. So if everything is correct and you call this method you will instantly be logged in. You can see the code here: https://github.com/laravel/framework/blob/5.7/src/Illuminate/Auth/SessionGuard.php#L347

A few lines below you can see that the $this->login call is made!

Now, the reason why you get this error is because you pass the id of the user to the method, but it's actually expecting a User object. So an object that has the interface \Illuminate\Contracts\Auth\Authenticatable. The User model has this interface by default in Laravel.

It's already not right to do login after auth attempt in this case. If you look closely to your code. You use Auth::user() in the login method. This means that you're already logged in otherwise Auth::user() would return null.

Let me know if this is clear for you now!

In the footer at the bottom of the page you can find a "support" button. From there you can contact Jeffrey and he will take care of it ;)

You can't write this as a non closure based route. A route group is not seen as a closure route!

You can however put everything in one line if you wish

Route::resource('admin/posts','PostController')->middleware('auth');

Note: I'm not sure if the admin/ prefix is going to work here though, haven't tested it! Otherwise you would still need to use the group callback ;)

So Cronix typed it all out, but that is exactly what I meant. You can't use the same route and expect a different output. Based on the given value (route name) you always get the same result back. So if you want different results per route in one method you need to provide different parameters.

Cool

@thebigk Awesome! Let us know if you have more questions ;)

\x indicates hexadecimal notation. Have a look at an ASCII table to see what 0x00 and 0x04 represent.

0x00 = NULL

This should help you to convert it: https://stackoverflow.com/questions/14674834/php-convert-string-to-hex-and-hex-to-string

I though todo_list_id was your primary key of the table.. Anyway, the reason why your example is working is because you're ignoring the primary key of your table and use a different column for the unique statement.

You can achieve the same with this

Rule::unique('todo_items')->where(function ($query) use ($list_id) {
    return $query->where('todo_list_id', $list_id);
}),

Documentation: https://laravel.com/docs/5.7/validation#rule-unique

@CALDICOT - Yeah, never send plain passwords over the internet! Use some hashing that can be done on both client and server. This way it's already more secure! You can even hash it with the JWT token if you like.

First of all you're using the primary method here. However the incrementing id is already the primary key here, so you don't need another.

So indexes should be used based on your search behaviour. If you're only quering results based the user_id and not on the other field you should only index the user_id column.

In the case of a polymorphic relationship you can even set two different indexes. One to get everything from a certain object. Like retrieving all the likes of post. You don't need the user for that

$table->index([''content_id', 'content_type']);

You can also retrieve all likes from a certain user. In that case you can add an extra key for that

$table->index([''content_id', 'content_type', 'user_id']);

You can put both of them in a migration. It's totally fine to have multiple indexes.

Just one more thing! I see that you write your own migration here. Laravel has some helper methods for generating the correct column structure for polymorphic relationships. You can find that in the documentation:

Documentation: https://laravel.com/docs/5.7/migrations#columns (scroll down to morphs

Yes I understand! However you always pass the same value to the method 3 times. So for all three methods it's going to give you the same response!

Well it's not working because you need to specify which todo-list can be ignored for being unique. Right now the validation is always failing because it needs to be unique at all times

If you take a close look at the documentation you can see you need to provide an extra parameter with the id of the resource you want to ignore. In your case that is the if the of todo list

Documentation: https://laravel.com/docs/5.7/validation#rule-unique

In your case that might look like this

$request->validate([
    'content' => 'required|unique:todo_items,content,' . $list_id . ',todo_list_id',
]);

As of Laravel 5.4 Rule classes where introducest. They make it more readable to write validation rules. If you have Laravel 5.4 or higher I highly recommend you to use this syntax

$request->validate([
    'content' => [
        'required',
        Rule::unique('todo_items')->ignore($list_id, 'todo_list_id'),
    ],
]);

Let me know if that works for you ;)

@ohffs Do you have a specific question?

Throttling does not exist for notifications. Since you're the one creating the notification you should either check if you can notify the user or not before sending the notification. Basically you need to build your own throttling for this!

Throttling with queues is possible with Redis because you read the amount of prepared jobs and so on. However with notifications you don't know that, because the medium you're sending over can be different per notification (slack, database, nexmo, etc.).

The problem is that they are all having the same result here right? You always pass the same values to the same method which will always return you the same result.

Instead you should pass in one unique parameter. For example the route name. Right now you pass the currentRouteName, but that will always be the same for all method calls.

So instead you need to check if the currentRouteName matches the actual route. In your case that can be reports.alluser or reports.categorystatic.

It's probably a bad provision. You should just contact the team behind forge using the contact options. Or you can just provision a new server and see if everything is working fine there ;)

You should be able to generate reports with the jimmy-js package, because it's Laravel 5.6 compatible. See the composer.json of the project: https://github.com/Jimmy-JS/laravel-report-generator/blob/master/composer.json#L14

Do you get any error installing the package? If so it might be another package that is not working for you!

Alternatively you can use https://packagist.org/packages/samuelterra22/laravel-report-generator

Also building this yourself is not hard at all ;)

I don't see usuarios being used in any of the controller methods as data for the view. Because of that there is also not pagination right? Or am I missing something?

All the information you need can be found here: https://getbootstrap.com/docs/4.1/components/forms/#how-it-works

However you need to write some javascript to make this work. For example on submit it will check if the field is filled whenever it is required. If not it will give it the :invalid pseudo element.

The best way to implement this is simply copying the the form examples from bootstrap and using that format. I see that you use {!! $input !!} which means the HTML for this comes from somewhere else?

@elijahpaul Yeah, not all types are supported yet! A raw query always does the job ;) You will also get problems whenever you use enums with doctrine/dbal. In those cases I use database statements as well ;)

Your approach for filling the data using a migration is fine! So nothing on that!

Back to the error! You get that error because you use DB::table. It's not returning Eloquent objects, but plain stdClass objects. Because of that you can't call the save method on it.

Instead you can do this to get all users

$users = User::all();

Now you can call the save method!

Here you go for MariaDB: https://www.stuartellis.name/articles/solus-setup/#installing-mariadb

Laravel relationships are awesome when you need to show all the related data in one view. Then you don't have to use the wheres and so on. However in your case you try to get a specific set of data. Instead it might be easier to use a raw or join query to get the latest post ids and then retrieve those posts based on the ids. This way your query is much faster!

HasManyThrough is a nice feature, but it also performs multiple queries for you to get the correct results. This is indeed slower when you have a lot of data.

I guess it's only used for statistics right now! But you're right, in previous designs the flag was used!

You have to build this yourself! Laravel doesn't support this feature at the moment. You can however create your own authentication provider that works with Laravel!

Documentation: https://laravel.com/docs/5.7/authentication#adding-custom-user-providers

You should give this a read: https://medium.com/@aslrousta/pessimistic-vs-optimistic-locking-in-laravel-264ec0b1ba2

You can also find more in the documentation: https://laravel.com/docs/5.7/queries#pessimistic-locking

When you use axios for example for your requests you can use interceptors to check for any 401 Unauthorized responses. Whenever you get a 401 Unauthorized you should be redirected to the login page. Your setup might look like this

const api = axios.create({
  baseURL: `${config.host}`,
  timeout: 10000,
  headers: {
    'X-Requested-With': 'XMLHttpRequest',
    'Content-Type': 'application/json',
  },
  responseType: 'json'
});

api.interceptors.request.use((config) => {
  config.headers.Authorization = `Bearer ${auth.getToken()}`;

  return config;
}, error => Promise.reject(error));

api.interceptors.response.use(response => response, (error) => {
  const statusCode = error.response.status

  if (statusCode === 401) {
    auth.deleteToken();

    routes.push({ name: 'login' });

    return Promise.reject(error);
  }
});

Well this is the basic gist of it! Note that I'm using the vue-router here as well. So the only thing you need to do is make sure that your api return a response with 401 ;)

$user_id = Auth::user()->id; Below code is already returning a collection of Pigeons. This basically means that you won't be able to perform any query specific calls on it like the select you try to do.

$ownPigeons = Pigeon::all()->where('user_id', $user_id);

So you have to options here. Either fetch all the data using a where user_id and then apply the like query or fetch the pigeons from your user. Also note that you should be able to perform both where statements! It might not return anything, but it should work!

// The simple way

$query = $request->input('query');
$userId = Auth::user()->id;
$pigeons = Pigeon::where('user_id', $userId)
    ->where('name', 'LIKE' , '%' . $query . '%')
    ->get(); // Now we have a collection of all pigeons

return $pigeons->pluck('name'); // Only return the name of the pigeons (basic collections method).


// The relationship way
$user = Auth()->user();

$query = $request->input('query');
$pigeons = $user->pigeons()->where('name', 'LIKE' , '%' . $query . '%')->get();

return $pigeons->pluck('name');

Note that the relationship way only works when you have defined the relationship.

Collections pluck method: https://laravel.com/docs/5.7/collections#method-pluck

You get this error because moment is now a variable and not a method anymore! Instead it's better to import moment js on the component itself. This way it will only be loaded where you use it!

For example

// show.vue

<template>

    <div>
        {{ moment.format('Y-m-d') }}
    </div>

</template>

<script>

import moment from 'moment';

export default {

    data () {
        return {
            variable: 'data'
            }
    }

}

</script>

Well you probably get the idea ;)

Yeah it's amazingly good! Jeffrey has done it again!

You are using Schema::create('posts', function () { });. However you're not creating a new table, but updating the table.

So instead you need to use ::table, just like you do with the down method.

Schema::table('posts', function (Blueprint $table) {
    $table->string('slug')->unique()->after('body');
});

Well the error is pretty clear to me. You have the wrong version of the stripe/stripe-php package currently in your project. So you need to check your composer.json and see what version is being used there.

laravel/cashier requires stripe/stripe-php to be at least v5.0.0 or higher. You probably have an older version in your project!

Are you sure $files has any values? You can check that by just doing dd($files) before return view(). It will die and dump the given variable. If that is empty, then that is the reason you don't see anything ;)

@fabioi I see it more a chosen approach. In general when for example your redis is down you have bigger issues! In that case you should be monitoring your redis server ;)

Perfect test!