I have older project on Symfony 2.8. Now i am moving / upgrading it to 3.4 framework on php version 8.
I have installed new framework of symfony 3.4 and copying old files into new and making changes as required like syntax changes, format changes etc.
I am facing an issue where i have to clear the cache of the project everytime. Like if i load the project in the browser first time it will show. But if without any change in code , if i refresh the page it goes into loading state, and does not return the result. Nothing is shown in log files. But once i clear the cache "php bin/console cache:clear" it works again.
Project is on Xampp : 3.3.0
Thank you
Related
I updated PHP to 8.1 and the site from 2.4.3-p1 to 2.4.4, first on a test server and everything went well, but when I did in production the frontend is working correctly, but the backend comes in but the only link in the menu that works is the control panel itself, the others do not open (store, system, ...).
I compiled and deployed several times and it didn't work.
Files in pub/static are generated normally.
Has anyone been through this situation? Do you have any idea?
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.
im currently working on an update from laravel 4.1.24 to 5.6 The problem is i got nearly no experience with laravel. My question is now, how do i properly upgrade. Should i first upgrade to 4.2 and then to 5.0 and so on or would it be better to upgrade directly to 5.6 and how should i do this? I mean there are so many changes that i think i could miss something.
Also the project is just in a github repository, so it's hard to check if it's still working after an upgrade because i dont got the old modules. Or would it be enough to go on laravelshift. com and just upload it there to go from 4.1 to 4.2, 4.2 to 5.0 and so on.
Best regards!
The Laravel documentation contains a whole list of breaking changes that can help you to upgrade your application to a newer version. Laravel Shift is a service that checks and updates these changes in your project.
However, there is no way of being sure that your project will still work after these upgrades. Especially if you are using external modules its very risky.
If it is not required, I would not recommend upgrading from 4.1.x to 5.6 unless you have a lot of time on your hands. A solution could be to set up a completely new 5.6 project and add the project code file by file and test the implementations.
Start from here and follow instructions to upgrade it to 4.2. Then go through your packages and update their versions accordingly. When done use dropdown list in the top-right corner to select next version (5.0) and repeat it until you are at 5.6.
You definitely need to be able to run your code and test it somehow after each step because there will be problems. From 4.1 to 5.6 is a big leap and a lot of packages might have breaking changes etc. I only migrated as far as from 5.1 to 5.6 and it took me whole day to fix everything.
As for automated upgrade you can try it as well, but as I already mentioned you need to be able to test your work because all packages need to be updated as well.
I've recently installed a fresh copy of Laravel 4.2 for a new project.
I've turned on debugging in app/config/app.php, set up my local environment in bootstrap/start.php and turned debugging on in app/local/app.php.
For some reason, my stack trace pages have changed. I can't find anything about them having officially changed, there's nothing in the upgrade guide...
Here's a screenshot of what it looks like. It's almost like an addition onto the normal "something went wrong" page, not like the orange/grey stack traces I've become used to.
To check, I created a whole new test project and the proper stack trace (albeit a different colour) is displayed, like so.
What's going on?
Just run following artisan command from your command prompt:
php artisan clear-compiled
It supposed to ran after installation (I had same problem).
I'm surprised you two were able to get the problem solved with artisan clear-compiled and composer update alone. Neither of those work for me.
After some troubleshooting, I found there are changes made in Laravel 4.2.2 and 4.2.3 that cause the Whoops page to go wonky. I've opened an issue at github.
Changes introduced in 4.2.2 make the stack traces look like the first #sanaco screenshot...
Laravel 4.2.2:
...then additional changes made in 4.2.3 make it look the second one:
Laravel 4.2.3
I am using netbeans 8.0 it shows auto-complete for zend framework but not for codeigniter. How can I use it with codeigniter for auto-complete support???
Thanks
Copy the code in the answer here: Netbeans code completion for CodeIgniter
into a php file in your project.
I used CI_Autocomplete2.0.php in the root of the project. It's a hack, but it does work. Since I'm familiarizing myself with CI's syntax & naming conventions it does what I want.
I successfully installed one of the Kenai 7.3 modules in 7.4, but the other one they show on the webpage wasn't listed in the plugin options, so I uninstalled it and now I can't get it to re-install again. I haven't tried it in my NetBeans 8 yet though.
Edit: Sorry, I just figured out that the Kenai modules were both listed. The "PHP CI Framework Repository" installed ok (don't know what, if anything, it did yet). It's the "PHP CI Framework" that won't install and lists out a bunch of module dependencies. I'll update again if there's anything to add when I try with Nb8.
You can do this using Project Kenai. Hope that's what you're looking for.
use sublime text editor 2 or 3 and install CI:snippets you will get dropdown for the codeigniter or check this link
http://ellislab.com/forums/viewthread/184716/