Ever since I have ran a composer update none of my pages on my application are able to be accessed, I just keep getting the spinning loading wheel.
I have checked the apache access and error logs but can't see anything. Has anyone experienced this before?
Any help greatly appreciated and if I'm missing a key bit of information to help anyone help me please let me know.
Make sure your php version is suitable. Use 7 if possible.
Optimize again and Clear cache
composer install --optimize-autoloader
bin/console cache:clear
thank you for your answer, however restarting the laptop worked. I'm guessing restarting apache might have solved the issue.
Related
I am upgrading my drupal project from 8.9 to 9.3.5 but after the upgrade while hitting website one error occur i.e
The website encountered an unexpected error. Please try again later.
I followed the steps mentioned in the drupal site for upgrading drupal from 8 to 9 or (later) click here for steps but didn't work for me.
Will anyone please help me or provide proper steps to upgrade drupal from 8.9 to 9.3.5?
You should try to get more information about the error.
Add to your settings.php file:
$config['system.logging']['error_level'] = 'verbose';
and check the output on your screen again.
You may also try drush to take a look at selecting the option errors from the terminal.
drush watchdog:list
I've run into this same issue multiple times. If you haven't already done so, try going to /update.php multiple times. (It seems to clear out the update process junk/leftovers and let it work.)
Other than that, it's always some kind of file issue. (I still update manually due to my server setup.) Sometimes it was a folder/sub folder that didn't upload fully or other times it was that some module simply refused to work with the new upgrade until that was updated.
Hosted by Namecheap
I'll provide any details that can help to resolve the issue
That was something in Namecheap's EasyWP plan - some stuff was disabled/not installed.
After switching to non-Managed WordPress plan those errors got fixed
my Symfony 3 app works flawless on my local webserver. Since it´s been installed on the remote web server it produces a blank page, even the routing doesn't work. After editing web/app.php $kernel = new AppKernel('prod', false); and set it to true, the application works as expected and does not display any errors.
Why does the application behave different on the local and the remote webserver. Did I miss to configure something on the remote server?
Any suggestions?
Thanks in advance!
Finally I have a solution to solve the problem: after the composer update I have to clear the cache of the prod environment manually by executing rm -fr var/cache/prod/*. For whatever reason does the command php bin/console cache:clear --env=prod quit working immediately after the composer update without throwing any error messages. After removing the cache files manually both the application and the cache:clear command work as expected without modifying web/app.php.
1.check permission to cache and log dirs ( need to be 777 )
2.check (paste here) error in logs/prod.log
Since I couldn´t find out what´s the real cause of this problem I´ve made a fresh install of my application and updated Symfony and all dependencies with composer.
Although I did the same with the old installation, it does the trick this time. My guess is, something went wrong with the composer update before.
Thanks again for your help! If someone has a similar problem I would appreciate if you could post how you solved the problem (or why AppKernel['prod'] = 'true' did work).
I have plausible explanation, what might have been the problem.
I have encountered this problem earlier this year with Symfony3, while developing on Windows but deploying manually (copying project's files) to shared server with Linux.
As you say - blank page in prod environment.
To add to the mystery log files did not show any problems
So i enabled dev environment to check what is wrong
application worked as intended if i added app_dev.php in the URL
I overviewed all the files, more than once, but copy was done correctly.
The answer
After some time I "came across" the file: bootstrap.php.cache in var directory. It "felt suspicious".
As I had exhausted my options i just deleted it to test the result.
That solved it in my case.
Site was running again.
No more blank page!
I guess mixed development environment has its toll.
I am trying to install admob in my app which I built using spritekit.My os Sierra version is 10.12.3.This is my first time attempting so long story short, I inserted GoogleService-Info.plist into my project and managed to locate my project and it looks like so
"myNames"-MacBook-Pro:~ "firstandlastname"$ cd /Users/"firstlast"/Desktop/"myProject'sName"/
"myNames"-MacBook-Pro:"myProject'sName" "firstandlastname"$
my issue here is that whenever I am trying to insert pod init it gives me this error -bash: pod: command not found
Any ideas as to why? Thanks.
So after much research, I worked out my rookie mistake. I will leave this here just in case someone runs into the same issue as I did.
All I had to do was install cocoapods! There are plenty of tutorials that show you how. Again, rookie mistake of me.
I keep getting an error with the MonologBundle for Symfony2:
Monolog\Logger::DEBUGS in /foo/vendor/symfony/monolog-bundle/Symfony/Bundle/MonologBundle/DependencyInjection/MonologExtension.php on line 119
It only happens in prod and happens only once, right after deleting the cache. After a refresh everything is back to normal.
All other answers suggest updating composer, which I have done, or deleting the bundle and monolog and reinstalling, which I have also done.
It happens both on my local machine (mac) and during deployment to my ubuntu machine using capistrano 2.x with capifony. Composer is freshly downloaded during those deploys, so composer version probably isn't the issue here.
Does anyone know how to solve this? Thanks in advance!
Most likely you have a typo in config, where you defined a log level for one of your handlers as "debugs" instead of "debug". Check your config.