siangboon

https://laravel.com/docs/8.x/eloquent-relationships#many-to-many

return $this->belongsToMany('App\Models\Role')->withTimestamps();

https://carbon.nesbot.com/docs/#api-timezone

have you installed php???

Suppose when install laravel and scaffold auth, it will generate this route in web.php

Auth::routes();

Inside this, it included the named route "login" unless you had remove or have some other route overriding…

Snappy was suggesting 'Route::redirect('/',route('login'));' so user hit the '/' will redirect to the route with name 'login', Your Route::redirect('/',route('KidsClub.test/login')) is suggesting user visit '/' will redirect to route named "KidsClub.test/login" which does not seem you have defined it and it's not a proper naming also…

Btw, do not use capital case for URL, in some system may hit issue…

Did the file naming missing or misspelled ".blade"?

Double check your form again whether any.error, such as the path, method, or missing enctype="multipart/form-data"…

you do not need to move any files but just change the route web.php, group all the route list and add the prefix...

https://laravel.com/docs/8.x/routing#route-groups

i think the simple way is to group all the route and add a prefix for it

Route::prefix('/demo/')->group(function () {
... // all your route here...
});

->select(DB::raw('RIGHT(column_name,10)'))

I think Laracasts is still using Vimeo...

you may check the typo error including the case sensitive for both namespace and class name...

i think it just mean the encryption process of the package had been completed. It may not related to your errors/issue not sending out....

perhaps, configure your database timezone accordingly, use the Carbon timezone api to display according to user respectively.

https://carbon.nesbot.com/docs/#api-timezone

You should able to access your site with IP Address of your site...

I'm not sure whether we are at the same page, I meant this Linode login page "https://login.linode.com/" should have nothing to do with your Cloudflare setting...

I don't think that is right to compare like that.... kernel is core and operation system and it involve a lot of stuffs which more than what you can imagine like application system...

In the application we building, we are focus on the functionalities of the application only, and there are a lot libraries and frameworks and even plugins to be used and the OS already built the foundation such as the display, inputs even the browse for us to work respectively, so we can easily split it into small module... but in lower level language it can't be easily split out, as a lot of task need to be triggered simultaneously....

I'm not so sure what the functions are inside the code shown, but it clearly show that the junk of codes already split into many functions, some of them are related and some may seem not related to each others...

I think neither the 100 lines nor 20 lines are always right for all application, it is just a suggestion and references... if you apply to assembly language it is totally insane....

basically you can use the flag to do the checking on both controller (back-end) and blade file (front-end).... however, it may be easier and flexible to use the policy to manage it....

check you laravel and system log, i didn't see there is a permission checking on search... i guess that it may whether the setup issue or folder permission issue...

i think the reason he uploaded the videos there is just to lead some new learners from youtube to Laracasts.... and even if one day he suddenly upload videos there again, all the contents will not be latest as in Laracasts...

from my experience, Cloudflare is quite reliable and stable even for the free plan also, perhaps you can try send email to the support to find out the issue... if your site is very critical, you can sign up their business plan which provide 100% uptime SLA....

btw, i'm not so sure why login to the linode related to cloudflare (would it be your site down due to linode service down?) , btw, you can by pass Cloudflare proxy for certain ip addresses also...

Did you hit any error while setting up the project?? I did encountered few errors while composer install and run the migration due to some extension and deprecated package... and fixed it and re-setup again and work fine...

few latest series in laracasts are covering Tailwind, and i saw there were a lot of copy and paste classes for every single elements.... make me less interests to practice the lessons.... hahaha...

the one thing i dislike the most is... by the time i finish the project, most likely the version bug/secuirty fixes are no longer supported..... hahahaha.....

i guess you may have multiple db instances in your system....

if it does not hit the controller, check the action "link" and method whether correct, if it hit the controller, then you can try to dd() something in each before and after action to identify where the error occurred.

however, i think you should include the display $errors in your blade, as it may because error due the validation failed...

if it does not hit the controller, check the action "link" and method whether correct, if it hit the controller, then you can try to dd() something in each before and after action to identify where the error occurred.

however, i think you should include the display $errors in your blade, as it may because error due the validation failed...

did you restart the tinker after migration?

perhaps, configure your database timezone accordingly, use the Carbon timezone api to display according to user respectively.

https://carbon.nesbot.com/docs/#api-timezone

are you copying version 7 route to version 8???

try

'App\Http\Controllers\Admin\[email protected]'
...

i guess that there may be typo error or tag does not closed / nested properly....

re-indent all the code and comment/uncomment the block of collapses part by part to test it out...

are you copying version 7 route to version 8???

try

'App\Http\Controllers\Admin\[email protected]'
...

common reasons are .htacess is not configure properly or case sensitivity... show more info will be helpful for other to help you...

why not leave the teams as it is and duplicate the code or create your own??? use the teams as the reference since you like it so...

modifying source code may be more hustle especially when version upgrade...

https://laravel.com/docs/8.x/helpers#method-preg-replace-array

hahaha, since few of you are complaining, i also want to hijack and complain (since there is no better place to feedback also, i starting feel frustrated with the upgrade pace)....

a framework have only 1 year lifespan time?? (most of my works still in version 6 because of the LTS...) release date - September 8th, 2020 bug fixes until - March 8th, 2021 security fixes until - September 8th, 2021

by the time we master it and build few projects and deploy... new version may already release and the version you just using already not supported.... i think that's why not seeing and "Learn laravel from scratch" series for 7, as by the time the series complete the new version may already half way release.... i guess...

can someone slow down the version upgrade???

This brings me to a side question: should I have an "Unapproved" or "Unassigned" role as a default role?

It depend, you can do so, or consider make a role as default, in your case, perhaps Parent is the default role and parent can create user with child role only...

should I just hardcode my list of roles somewhere within my models (or somewhere else) instead of storing this information in the database?

if you are pretty sure your application will NEVER change then you can hardcode it for simplicity, but if you want to manage it, store it in database is better choice so you can rename it, add new role...

just to clear up a few things with my User model, it sounds like I'd have a nullable parent_id field on all of my User models, is that correct?

I think it's nothing wrong to have a nullable or 0 parent_id to determine the user as parent, to database, it's just a value, but you are the brain on the system to decide how to do with this value...

the policy is usually functions as declaration of the rules/policies to determine what condition to allow on that MODEL, so that you can call the policy checking on your controller or blade file...

I had requested few times since years ago and still patiently waiting for the day come... Hahaha...

->intended()

https://laravel.com/docs/7.x/authentication#authenticating-users

use ``` before and after the code it will ease other to view

call $ParamData directly

'{{ $ParamData }}';

the code above did not seem so....

show your code with appends()...

This brings me to a side question: should I have an "Unapproved" or "Unassigned" role as a default role?

It depend, you can do so, or consider make a role as default, in your case, perhaps Parent is the default role and parent can create user with child role only...

should I just hardcode my list of roles somewhere within my models (or somewhere else) instead of storing this information in the database?

if you are pretty sure your application will NEVER change then you can hardcode it for simplicity, but if you want to manage it, store it in database is better choice so you can rename it, add new role...

just to clear up a few things with my User model, it sounds like I'd have a nullable parent_id field on all of my User models, is that correct?

I think it's nothing wrong to have a nullable or 0 parent_id to determine the user as parent, to database, it's just a value, but you are the brain on the system to decide how to do with this value...

the policy is usually functions as declaration of the rules/policies to determine what condition to allow on that MODEL, so that you can call the policy checking on your controller or blade file...

check out the appends()

https://laravel.com/docs/master/pagination#displaying-pagination-results

in .env file, declare the value

TOKEN_KEY=YOURKEYVALUE

in your config/services.php (or create your own file), append it before the last ];

	'yourservice' => [
		'key' => env('TOKEN_KEY'),
	],

in your application

$token = config('services.yourservice');

https://laravel.com/docs/7.x/configuration

most people store it in database, some store in .env file and configure and call from config file... in your case, i think database is better option.

check the error(s) on the console...

in version 7 and earlier, the documentation use PhotoController but in version 8, 'PhotoController::class' is in used. I think both are identical... you can print out the route list (php artisan route:list) to double check and compare... I guess the 404 may due to the "plural"

perhaps, put the script as partial file (since it's unlikely to change often) and store only the "id" or "key" in database, call the script when the "key" exist ....

https://laravel.com/docs/7.x/controllers#resource-controllers

Laravel resource routing assigns the typical "CRUD" routes to a controller with a single line of code.

it's just to simplify your works from repeating creating the same standard route list if your controller use all these method

perhaps double check the route name first

I tested your code, copy both model and blade that you shared and it's working as expected and even with the search filter as well. You may double check whether you key in the book and subject accordingly... by the way, putting the request() as the parameter in the query which by pass validation does not seem as an good idea in term of security and also calling the search filter for each book record at the blade will causing heavy performance issue if there are huge books records....

Out of the topic, from my understanding, usually there is a subject which may has many books instead of one book has many subjects, for example, Mathematics subject will have many books

subjects

	Schema::create('subjects', function (Blueprint $table) {
            $table->bigIncrements('id');
            $table->string('name');
            $table->bigInteger('book_id');
            $table->timestamps();
        });

id|name	|	book_id
'1', 'Subject 1', '1', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'2', 'Subject 2', '1', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'3', 'Subject 3', '2', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'4', 'Subject 4', '3', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'5', 'Subject 5', '4', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'6', 'Subject 6', '5', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'7', 'Subject 7', '2', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'8', 'Subject 8', '4', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'9', 'Subject 9', '5', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'10', 'Subject 10', '5', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'11', 'Subject 11', '4', '2020-09-08 04:37:05', '2020-09-08 04:37:05'
'12', 'Subject 12', '3', '2020-09-08 04:37:05', '2020-09-08 04:37:05'

books

	Schema::create('books', function (Blueprint $table) {
            $table->bigIncrements('id');
            $table->string('name');
            $table->timestamps();
        });

book model

    protected $fillable = [ 'name', 'subject_id'];

    public function subjects()
    {
        return $this->hasMany(Subject::class);
    }


    public function subjectsWithSearch()
    {
        // I need to filter this relationship , something like 
        return $this->hasMany(Subject::class)->where('name', 'like', '%' . request('keyword') . '%');
    }

blade

			<div class="row">
				@foreach ($books as $book)
					{{ $book->name }}
					<ul>
					@foreach ($book->subjectsWithSearch as $subject)
						<li> 
							{{ $subject->name }}
						</li>
					@endforeach
					</ul>
				@endforeach
			</div>

result for all

Book Title 1
Subject 1
Subject 2
Book Title 2
Subject 3
Subject 7
Book Title 3
Subject 4
Subject 12
Book Title 4
Subject 5
Subject 8
Subject 11
Book Title 5
Subject 6
Subject 9
Subject 10

result with keyword=1

Book Title 1
Subject 1
Book Title 2
Book Title 3
Subject 12
Book Title 4
Subject 11
Book Title 5
Subject 10

try coding first and paste the code (including the model, relationship, controller and blade) and result....

you can try with('subjects) when query the Book model if you have the relationship setup, return the $books results before pass it to blade...

try

->groupByRaw('MONTH(created_at)', 'YEAR(created_at)')

or simply use selectRaw with your SQL query statement