Magento 2 – Fixing ‘Attention Something Went Wrong’ on Backend Product Page

Regarding the debug file

So the messages like this main.DEBUG: cache_invalidate in Magento 2 are not errors, there are only debug messages to tell that the cache is invalidated (which is not a problem nor an error).

Regarding the system file

So the messages like this Broken reference: the 'block1' tries to reorder itself towards 'block2' is not a real error either. As you can see from this github issue:

Ok, guys. There is no bug here ) Really. There are two reasons, why you all see such a logs.

Reason 1 People keep forgetting remove "before" and "after" attributes for blocks which have been moved to another parent, so those are no longer relevant. Internal ticket in progress MAGETWO-53410 and we will clean up legacy references soon.

Reason 2 As an example, let's take Such references mostly (if not all) reside in default.xml files (so will be applied to all pages without exclusions), while the container "sidebar.additional” is added by 2columns-left.xml layout only. So, on pages where different page layout is used, the reference will lead to nowhere, and you will see CRITICAL error logged (while it is not critical at all).

The tricky thing is that sometimes that could be a normal case and developer understands why it happens (if want to add a block to specific container to all pages on which target container available, and don’t need that block to be added to the pages where target container is not available).

Short excerpt from internal ticket description: "Stop logging such cases at all, or at least stop marking them as CRITICAL (ensure that it’s not logged in production mode). Also it will be helpful if logged message will say the URL of the page where target container is missed".

So, as you see, we still think that logging such "broken" references is a right thing to do, since some of them are really could be caused by misspells in layout files.

I reckon there was a lot of errors like this in the logs in the early stable releases as you can see from those two issues:

• https://github.com/magento/magento2/issues/3075
• https://github.com/magento/magento2/issues/3224

So if you wanna get rid of them, I reckon you should update to the last version. Seems like Magento fixed it in the develop branch but I'm not sure if the bug fixes are part of 2.0.8/2.1.1 already.

This issue was reported many times on the versions before 2.1.5. Like this issues at the Github.

https://github.com/magento/magento2/issues/5418 https://github.com/magento/magento2/issues/6297

So try run these commands on the root of your installation, if don't resolve it, try to upgrade your Magento to the last version.

alias mage="php -d memory_limit=-1 -f bin/magento"

chmod -R 775 pub/static/ var/ pub/media/ && 
rm -rf var/view_preprocessed/ var/cache/ var/page_cache/ var/tmp/ var/generation/ pub/static/frontend/ vendor/* ; 
composer install && composer update -vvv && 
php -r "opcache_reset();" 
mage module:disable Magento_Review ; 
mage cache:flush && 
mage indexer:reindex && 
mage setup:upgrade && 
mage setup:static-content:deploy && 
mage setup:db-data:upgrade && 
mage dev:source-theme:deploy && 
chmod -R 775 pub/static/ pub/media/ var/