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.
Related
Yesterday my site suddenly stopped working and after investigating I found out that Midphase upgraded the PHP to 8.1 and MariaDB (says from 10.3 to 10.5). I got them to roll back PHP to 7.4 for the time being, although it sounds like it was already on 7.4, which is good as they couldn't go back further.
My live site is on 3.10.1 (http://www.scifivision.com) and after running an upgrade on a backup, assuming I did it right I have a version on 3.10.11. (http://www.thejfiles.com/sfv2023). Both are giving me the same errors other than the database name is different.
The frontend gives me white page with the error "1146 - Table 'thejrub4_joomfin.joom_fields_values' doesn't exist" and backend gives me a warning "Error loading module Table 'thejrub4_joomfin.joom_modules_menu' doesn't exist" and it lets me log in but I can't do anything.
Just wanted to mention, in case it's relevant, I have an earlier backup (I'm at the point if anything is fixed I'll be happy) that is also giving me two warnings:
session_name(): Session name cannot be changed after headers have already been sent in /home/thejrub4/public_html/sfvclon/libraries/joomla/session/handler/native.php on line 128
ession_cache_limiter(): Session cache limiter cannot be changed after headers have already been sent in /home/thejrub4/public_html/sfvclon/libraries/joomla/session/handler/native.php on line 235
Error: Failed to start application: Failed to start the session because headers have already been sent by "/home/thejrub4/public_html/sfvclon/libraries/vendor/joomla/input/src/Input.php" at line 41.
Since I am not seeing them on the newer backup, I'm assuming that is probably not the issue and was something I previously fixed, as I do have maximum on for debug
I have used forum post assistance for joomla.org if that helps and I will post the code below. This is for the 3.10.11 install, as the FPA wouldn't work on the older one. It says it should work without any issues, but clearly that's not true. I didn't know if that would help on this forum, but if you need it please let me know.
I've been modifying a module and for some reason prestashop does not take into consideration the code modifications in module.php.
I've made modifications a while back and I need to modify it again due to an update that raises an error, the problem is that I get the error even if I remove said line.
I get this type of error: PHP message: PHP Notice: Undefined index: ordersorderFilter!active in /modules/module/module.php on line 104
I've commented first than removed that line but I still get the error.
It seems like there is a cache somewhere that I can't find, I've deactivated all possible cache in prestashop, activated debug mode, deleted the dev and prod folders in /var/cache/ but I still get the error.
I've used grep on the server to try to find that line, and when I delete it from the file I can not find it anywhere else on the server (but can find it if I add it).
Anybody has any idea?
Thanks a lot!
Prestashop does not perform any kind of caching on the modules PHP files so the problem lies elsewhere or at "lower level" (webserver / proxy ie.).
So check your environment for server-side caching, proxies or PHP accelerators such as opCache that may not serve changes from the source server.
Also try renaming or deleting the offending file altogether and see if the error changes, if not you might simply be looking at the wrong file :)
I'm trying to start with Hyperledger Composer Playground, but when I access into this link:
https://composer-playground.mybluemix.net/editor
I found this error:
Error: Object with ID 'undefined' in collection with ID 'chaincodes' does not exist
I tried to use another browser and I cleaned the cache, but the error occur in any case, also locally. Sometimes the error doesn't appear but when I click on getting started, the load is infinite.
How can I fix it?
Thank You in advance.
can you try below steps may help
Clear browser local storage by running localStorage.clear() on browser console
Clear the browser history and cookies
restart your browser
The first problem I'm running in to is that when installing I receive a mysql error stating that a table cannot be found. Of course it can't, I finished installing the dependencies much less run the migration. The error was being triggered by a Eloquent query in a view composer. After commenting out the entirety of my routes file Composer let me continue.
I proceed to uncomment out my route file - I get the error once again trying to run any artisan commands (can't migrate my database because I haven't migrated my database). Repeat the solution for step one and I've migrated my database.
Artisan serve is now serving me my layout file in the terminal and exiting. I'm at a bit of a loss to troubleshoot this. I assumed that it was possibly a plugin, trying to disable plugins one by one results in:
Script php artisan clear-compiled handling the pre-update-cmd event returned with an error
and being served up my layout file in the terminal.
It seems that the error is directly related to this function in my routes file:
View::composer('layouts.main', function($view) {
$things = Thing::where('stuff', 1)->orderBy('stuff')->get();
$view->with(compact('things'));
});
This isn't a new introduction to the application however so the underlying cause is coming from somewhere else.
As i said in the comment, if you are finding database errors in production server but not in local, then
check database credentials. if its ok then....
check the different configs in the environment.
using profilers(any) will let you know what environment you are in.
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.