If I already have an existing Laravel Jetstream (Inertia) project which was installed without the --teams option is there a way to go back and install support for teams given that I have already created multiple controllers, models, migrations and other customizations within the app?
AS A TEST, I did it here on my Jetstream LIVEWIRE project, by reinstalling Jetstream with --teams. It's doable, but beware of some side effects.
What I did:
Publish Jetstream view files, if you haven't already:
php artisan vendor:publish --tag=jetstream-views
Update Jetstream to version 2.0 (upgrade guide)
Reinstall Jetstream with options --teams:
php artisan jetstream:install livewire --teams
Warning: This will install the remaining actions, models, factories, and tests and will update several files, among those some view files, including on the layout views folder, so be careful and have them in source control or in a backup BEFORE trying this. Some view files will change entirely, so you will have to manually merge the changes with your old ones.
Run the migrations that were created
Related
I am new to laravel and I am wondering how all these default templates are upgraded when a new minor(!) laravel version was released.
Let's say I've installed laravel via:
composer create-project laravel/laravel example-app
This pulls in a lot of files with basic templates to get started.
Now when I run composer outdated it shows me which versions are currently out of date. I guess that composer update will only update the vendor files, but not the files inside my project itself. But what if those template files were changed on an update? How do I get to know this change?
The same question applies to packages like sanctum, fortify and jetstream. How do I manage those updates? Or aren't the template files ever being corrected between minor versions?
I am working on a project which is in Laravel 5.8, and recently, I upgraded it to Laravel 6.0 with its packages dependencies versions too. The project was running fine. But, today, I update the composer via composer update, and it upgraded to Laravel 6.2. After that, I faced an error:
App\Http\Controllers\Auth\ConfirmPasswordController does not exist
Then I installed a fresh Laravel-6.2 and generated basic scaffolding via php artisan ui vue, then, generated login/registration scaffolding via php artisan ui vue --auth. After that, I found ConfirmPasswordController.Then, I manually created ConfirmPasswordController in my running project and copied all of the codes from ConfirmPasswordController to my manually created ConfirmPasswordController. Then, the error has gone. Although I did not face any error related to this. But, I am confused about my approach. Is it right way what I did? Or it has a better way to solve this problem. I am confused about, If I face many issues for php artisan ui vue --auth in the next time. Would someone suggest me the right process, what should I do?
Laravel made the following additions and modifications from versions v6.0.0 to v6.2.0.
A app/Http/Controllers/Auth/ConfirmPasswordController.php
M app/Http/Controllers/Auth/ForgotPasswordController.php
M app/Http/Controllers/Auth/ResetPasswordController.php
M app/Http/Kernel.php
M config/auth.php
M resources/lang/en/validation.php
Please make sure these changes are in your Laravel instance though it sounds like they now are. You can see the diff of v6.0.0 to v6.2.0 here. If you need to see v5.8.0 changes through 6.2.0, please go here.
When upgrading, you will need to copy it from https://github.com/laravel/laravel/blob/master/app/Http/Controllers/Auth/ConfirmPasswordController.php
This is known, reference https://github.com/laravel/ui/pull/36#issuecomment-539921924.
i have download a laravel project from github, When i run the project i got an debugger menu.
I am very new to laravel.
How do i get this debugger menu in my other projects
Add laravel-debugbar in composer.json, like "barryvdh/laravel-debugbar": "^2.0#dev",
Add Barryvdh\Debugbar\ServiceProvider::class,, 'Debugbar' => Barryvdh\Debugbar\Facade::class, to providers and aliases in your config\app.php.
Please don't forget run: composer update
What you have shown is the debug bar from the barryvdh/laravel-debugbar package. This is the package you want to use if you have other Laravel projects.
If you have other non-Laravel projects, you want the maximebf/php-debugbar package. The barryvdh/laravel-debugbar is a nice Laravel wrapper around the base maximebf/php-debugbar package.
You can view the linked packages for installation instructions.
I need to install an admin panel theme in laravel. Please share any ideas.
Look like there is a project for it.
-> https://github.com/harryxu/laravel-theme
and see "Usage". (only for themes, sorry)
There are packages such as "cartalyst/themes": "3.0.*"
You can insall them by including this in your composer.json
"cartalyst/themes": "3.0.*"
and do
composer update
Here is the link about that.
Also you shall use this and many such are available over github and other resources.
But i would recommend you to put the css and js files in your assets folder and simply use the html in your blades
Recommendation : Still why Laravel 4.2, why not 5.1
https://cartalyst.com/manual/themes/3.0#installation
install composer before. Site to composer is too obvious to put it here
When I'm working in my Laravel project it won't change anymore. I've already
restarted wamp and updated with php laravel, but it keeps loading my stuff from a couple of days ago?
What am I doing wrong here?
Run composer dump-autoload
It regenerates the list of all classes that need to be included in the project.
This sort of problem caught me out early on when I added classes into my laravel applications.