After installing laravel I get the following message when run the project:
Whoops, looks like something went wrong.
You can have a look at your laravel log, located at app/storage/logs/laravel.log.
Whilst your application is in development mode, you can make your life a lot easier by enabling detailed error reporting. Just change false to true here:
In this file (app/config/app.php) - first line:
Nobody will be able to help you with above posted error message, but it will be very easy to help yourself with detailed error reporting enabled
Set 'debug' to true in app/config/app.php.
If it's already to true, set it to false, refresh, then set it again to true.
Related
Until recently everything was working well. Now, when I try to save (create or update) any page or post I get error message at top of the form "Error - There was an error when trying to save the form".
In error log I see this error:
“Uncaught PHP Exception Sulu\Component\Rest\Exception\InvalidHashException: “The given hash for the entity of type “Sulu\Bundle\ArticleBundle\Document\ArticleDocument” with the id “9e0720a7-5565-4a6f-a735-8a186b8fef9b” does not match the current hash. The entity has probably been edited in the mean time.” at /var/www/html/vendor/sulu/sulu/src/Sulu/Component/Hash/RequestHashChecker.php line 53"
Tried clearing symfony cache, website cache from admin, restarting docker containers.
I'm totally unaware that I did something to cause this error. Please help.
Update: strange thing I just noticed. When I try to save some article and I get that error and go back to overview page (where i.e. all articles of that type are listed) then I see unchanged article title. But when I click to edit it I see changed title?!? Like title on overview page and title on edit page are not used from the same place? How is that possible?
Update:
Now even I setup once more project from scratch saving articles causes that error. Some more info:
In stack trace last command executed is:
in vendor/elasticsearch/elasticsearch/src/Elasticsearch/ConnectionPool/StaticNoPingConnectionPool.php (line 64)
an it shoots out “No alive nodes found in your cluster”.
And while I'm setting up the project when executing:
php bin/console ongr:es:index:create
I get error:
{"error":{"root_cause":[{"type":"resource_already_exists_exception","reason
":"index [su_articles/sWs5F1uzSFO8bFiZqF1Egw] already exists","index_uuid":
"sWs5F1uzSFO8bFiZqF1Egw","index":"su_articles"}],"type":"resource_already_e
xists_exception","reason":"index [su_articles/sWs5F1uzSFO8bFiZqF1Egw] alrea
dy exists","index_uuid":"sWs5F1uzSFO8bFiZqF1Egw","index":"su_articles"},"st
atus":400}
And when I run:
php bin/console ongr:es:index:create --manager=live
I get similar:
In Connection.php line 675:
{"error":{"root_cause":[{"type":"resource_already_exists_exception","reason":"index [su_articles_live/Pissm9ycRj-o79K4wrrD
AA] already exists","index_uuid":"Pissm9ycRj-o79K4wrrDAA","index":"su_articles_live"}],"type":"resource_already_exists_exc
eption","reason":"index [su_articles_live/Pissm9ycRj-o79K4wrrDAA] already exists","index_uuid":"Pissm9ycRj-o79K4wrrDAA","i
ndex":"su_articles_live"},"status":400}
Also to mention that now saving pages works, but saving articles doesn't.
This solved the issue on ElasticSearch index creation for me:
php bin/console ongr:es:index:drop --force
The error can happen in the following cases.
Expected Case somebody else did edit the same article like you and did save it
Unexpected Case your phpcr cache is not in sync
Unexpected Case you have a multi server setup but your cache.app is not configured to use a central cache
So if its one of the unexpected cases first you should clear your cache.pools with:
bin/console cache:pool:prune
If you have a multi server setup make sure you configure a central cache. Most use in this case a redis-server which you configure in your cache.yaml e.g.:
# config/packages/prod/cache.yaml
framework:
cache:
default_redis_provider: "%env(resolve:REDIS_DSN)%"
app: cache.adapter.redis
Also make sure that you use the latest version and maybe update your phpcr cache configuration based on the sulu/skeleton: https://github.com/sulu/skeleton/blob/2.x/config/packages/prod/sulu_document_manager.yaml, there you could when performance doesn't matter in your case disable the phpcr cache, I would not recommend that.
I am trying to make a child theme for 'Moove' in moodle 3.6! But as soon as I update my database and click on theme selector button, I get an HTTP 500 error!
I follow the instruction from the blog below, but apparently, I am doing something wrong. Can sb help me please?
https://edwiser.org/blog/create-child-theme-moodle/
Error 500 usually means there is something wrong in your scripts/configuration.
First thing to do would be to enable debugging messages to see what exactly is wrong.
Here you can find how to enable debug output to get more detailed error messages: https://docs.moodle.org/36/en/Debugging#In_config.php
I don't seem to be getting the familiar symfony error messages I used to when I wasn't running on a VM. The error message I get when there is a Laravel related issue is a "Whoops, looks like something went wrong" in a white background.
Is there a common solution to this/others run into this problem who can help out?
thanks
You need to turn $debug to true in app/config/app.php
I am installing SugarCRM Portal on my local host. In installation wizard it says that I must turn on Allow Call Time Pass Reference and I did at php.ini and stopped my apache server. When I started it back again an error occurred saying there was a fatal error.
Here is the error on my logs
"Fatal error: Directive 'allow_call_time_pass_reference' is no longer
available in PHP"
I cannot continue my installation if all settings are all green. This is the only thing that is blocking me. Help Please.
It says in the PHP documentation that this configuration option has been removed from PHP 5.4.0 onwards.
http://php.net/manual/en/ini.core.php
If your php version is above PHP 5.4.0, try downgrading PHP.
I've got it
air4x's comment is correct but not detailed so I am here to give the detailed one.
All you have to do is go to sugarportal_dir/install/ then open checkSystem.php. There is a if statement that looks like this.
if('0' == ini_get('allow_call_time_pass_reference')) {
}
All you have to do is change 0 to 1:
if('1' == ini_get('allow_call_time_pass_reference')) {
}
That's it. Hope that helps others. And thanks for the reply air4x your logic is correct.
I'm using Symfony2 RC3 and I have a NewsBundle that has an Article entity.
I generated crud for it using the command: $ php app/console doctrine:generate:crud (with 'write' set to yes).
Now, every page on my site throws this error:
Fatal error: Label 'not_admin_article_create' already defined in /usr/local/zend/apache2/htdocs/AIEF/app/cache/prod/appprodUrlMatcher.php on line 260
If i get rid of
requirements: { _method: post }
for admin_article_create, admin_article_update and admin_article_delete in the generated routing yml file, everything works fine. Any idea why ?
I came across a similar issue recently, Google search wasn't much help but give me ideas of where to look, anyways enough blah blah.
The error I was getting was as follows:
enter code here`Fatal error: Label 'not _ offering management' already defined in /...
Whats I noticed was that there was a duplicate entry in routing_dev.yml and routing.yml, so basically the issue pops up when you happen to have multiple configurations. I think Symfony2 bundle generation adds mapping, but user probably accidental re-configures mapping else where.