So I decided to do upgrades on my framework and the working environment. I upgraded my laravel version from 5.7 to 5.8. Upgraded my vagrant, virtual box and homestead to the latest versions. Since this update, i've been getting this error:
Now whenever I destroy the vagrant box and create another one, everything works fine. But the minute I do a vagrant reload again, this exception is thrown. I've searched through google and StackOverflow for days now but I don't get anything relating to what's causing my error. Any help will be truly appreciated.
Also anytime I try to run the php:artisan command, i'm getting the following error:
In LoadConfiguration.php line 68:
Unable to load the "app" configuration file.
Related
I have a Laravel 5.1 install that I am upgrading. I meticulously followed the instructions available at https://laravel.com/docs/5.3/upgrade#upgrade-5.2.0 for the upgrade, including removing Illuminate\Foundation\Providers\ArtisanServiceProvider and Illuminate\Routing\ControllerServiceProvider from the config/app.php file (I am stressing this point, as googling for this issue has suggested this in every response).
Despite this, I am still getting this error when I run composer cache:clear
[Symfony\Component\Debug\Exception\FatalThrowableError]
Class 'Illuminate\Routing\ControllerServiceProvider' not found error
and see this error in my browser:
FatalThrowableError in ProviderRepository.php line 146:
Class 'Illuminate\Routing\ControllerServiceProvider' not found
Thinking that perhaps references to these classes were being cached, I checked bootstrap/cache/services.json and removed the references from there as well and then ran composer dump-autoload but I am still getting this error.
I also made sure to copy over example config/app.php from Laravel 5.2 clean install example here: https://raw.githubusercontent.com/ziyed/Laravel-5.2/master/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php
I have read through the similar threads on StackOverflow and Laracast and tried tried to use the advice contained inside, but nothing seems to work.
Any help would be greatly appreciated. For reference, my dev setup is running on a local XAMPP stack under a Windows 10 OS. The other environments are remote, using a traditional LAMP stack with Amazon Linux 2. I was trying to do the upgrade locally.
Illuminate\Routing\ControllerServiceProvider is not present anymore.
When I recently had to upgrade the same versions as you, I had to run composer update before and after removing Illuminate\Routing\ControllerServiceProvider::class and Illuminate\Foundation\Providers\ArtisanServiceProvider::class to make it work. Also worth to mention you need to clear bootstrap/cache. It worked for me.
Edit: i noticed now you tried the last step partially as well. You can remove all php files from cache.
I am closing this question, not because I found an answer, but because continuing down this path just didn't pass a cost/benefit analysis. After upgrading to 5.2, the next upgrade would be 5.3, and the breaking changes between 5.2 to 5.3 is a lot higher than between 5.1 to 5.2. After some thought, it was obvious that the better approach would be a fresh install on my target version, and then start porting over each module in my project by copying over the views, updating the routing, and making changes to the controllers and middleware as needed.
Or just using Laravel Shift.
Thank you to everyone who chimed in with suggestions!
I am stuck on this little problem, hoping that you can help me, I followed all the asset compiling steps from the docs. The app is working totally fine on the local environment as soon as I deployed it causing the /livewire/livewire.js not found.
i have ddev running locally on my windows machine.
I worked all the time on my TYPO3 installation, it was working fine and the only thing i did yesterday was to patch it from 9.5.18 to 9.5.19. Even after that, it worked fine.
As i wanted to start today, i get the message
The requested resource "" was not found
, when I want to get to the backend (/typo3). The installtool is working but has no styling at all.
The Front End is working fine.
here is an image of the error
Any idea where i can could take a look at? I already restarted my machine, ddev, docker and went back to an older composer.lock, composer dumpautoload and cleared typo3temp but nothing worked.
I had this on a previous update a few weeks ago on 1 installation while I was updating a few dozen. What fixed it was deleting typo3conf/PackageStates.php. I did have to turn on all the extensions again after that of course, but it still worked after I'd done that. As this was only in 1 installation and the others were fine I didn't investigate it further so I don't know what caused it or if there's a better solution. Not a real answer, but perhaps it will help you.
I have been running a pretty old version of Homestead for years. At various times, I have tried updating a few times. I always got an error about being unable to resolve a package. Since the version of Homestead that I was running was technically working, I probably left my old version of Homestead running a bit longer than I should have.
I finally buckled down and worked through updating it. Everything appears to be back like it was except for one frustrating difference. Many of the projects in my Homestead interact with one another, oAuth, API integrations, etc., and while I can visit any project in my browser like before, none of the projects can resolve one another.
I always receive a curl error:
cURL error 6: Could not resolve host:
So, for example, one project that relies on an API call to another project for a dropdown list in a form, the API call never resolves and I can't populate the form.
Has anyone experienced anything similar? Any thoughts on what may be causing this? I have Googled around without much luck.
The problem initially started when I updated my laravel/homestead box. So, I thought that maybe the update corrupted the box somehow. I have run vagrant destroy and then vagrant add laravel/homestead to reinstall the newest version and the issue is still there. I noticed that the newest version that installs is 8.0.0-alpha2, so I tried specifying vagrant add --box-version 7.3.1 (the latest stable that doesn't have alpha or beta in the name) and again I am getting the same issue.
GuzzleHttp \ Exception \ ConnectException
cURL error 6: Could not resolve host: outside-project.local (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
If I make the exact same API call that the project is trying to make, it resolves as expected in Postman. I can also visit the project and all projects as expected in the browser.
If I make the exact same API call that the project is trying to make, it resolves as expected in Postman. I can also visit the project and all projects as expected in the browser. I would expect that projects can resolve each other just like they did before I tried updating Homestead.
If any one else is experiencing this, here is how I got it working:
vagrant ssh and add any projects that need to communicate with one another to the /etc/hosts file.
I just discovered Laravel Dusk, and I was excited to use it in my project. However, it can't seem to get it to work. I followed the Laravel Documentation to install Dusk. When I run php artisan dusk in the terminal, I get
[Symfony\Component\Process\Exception\RuntimeException]
TTY mode is not supported on Windows platform.
I found this (https://github.com/laravel/dusk/pull/13/files) which is supposed to fix it I think, but I still get the error.
Also, I attempted to run the Dusk tests through PhpStorm following the accepted answer here (https://laracasts.com/discuss/channels/testing/dusk-via-phpstorm), but I get a Class config does not exist error. Many people said that this caused by a space in the .env file, but that is not my issue.
Can anyone help me figure out what is going on with Laravel Dusk in my setup? My Laravel project is 5.4 and I'm using Laravel Dusk 1.0 and PhpStorm is 2017.2.1
You can install chromedriver into windows on your own, and try not to use the version that is shipped with laravel dusk. Remember that, your chromedriver version needs to match your currently installed Chrome version, and when Chrome gets updated, then you need to update/reinstall chromedriver manually again. Hopefully it does not happen too often, and when there are updates, you benefit from using latest versions, which I find really nice :)
Download it here.
After installing chromedriver, you need to start it from command line (just issue command in your download/install directory chromedriver) or add it as service (which I do not prefer, cause I want to have control of which service is running on 9515 port).
Finally you need to comment out // static::startChromeDriver(); in your DuskTestCase.php, which tries to start laravel dusk included chromedriver, cause in this case, you are already running one.
Run dusk tests again and all should be working fine.
I don't know what your system setup is, but I am using this workaround on windows 10 with Laravel 5.5, dusk 2.0, which still causes problems, when chrome gets updated.
BTW. Just to mention. This also works with CI workflows using docker. You can read more about it here