How can i solve this issue ? it is weird
{{{System Messages}}{{System Messages}}{{System Messages}}{{themeMagento/backend}}}
This issue is appearing/ visible every where in the admin almost
adminnotificationmagento2messages
How can i solve this issue ? it is weird
{{{System Messages}}{{System Messages}}{{System Messages}}{{themeMagento/backend}}}
This issue is appearing/ visible every where in the admin almost
Messages aren't actually deleted from the database when removing them in admin. It works this way because when a new notification comes in the title of this notification is compared against the titles of existing notifications and if a notification with the same title already exists the notification is considered to already have been received and so is discarded.
Each notification has a 'read' and 'removed' flag and this is all that gets set when reading or removing in admin. This should however successfully stop the notifications from showing in admin again. An interesting point here however is that if the notifications are actually removed from the database (by clearing the adminnotification_inbox
table) then Magento will consider none of the notifications to have been received before as there are no titles to compare to. The result is that all notifications are pulled in again - it sounds like you could have customisations to your store which actually remove the relevant database entries rather than just flagging them when you remove them from admin.
You can either:
system -> configuration -> advanced -> disable modules output -> disable Mage_AdminNotification
)Your class name is not correct
Change
class Bbs_Core_Block_Messages extends Mage_Core_Block_Messages
to
class Bbs_Messages_Block_Messages extends Mage_Core_Block_Messages
In your config.xml also change
<blocks>
<core>
<rewrite>
<messages>
Bbs_Core_Block_Messages
</messages>
To (Please note : the class name and all on one line)
<blocks>
<core>
<rewrite>
<messages>Bbs_Messages_Block_Messages</messages>
Best Answer
This is usually caused by a corrupted js-translation.json file in these two locations:
You should first of all try to delete these two files and then flush cache and execute
php bin/magento setup:static-content:deploy -f [locale] -a adminhtml
If the file still gets generated containing curly braces maybe you're having an issue I also had and in database table
core_config_data
there are records that make the system think inline translate is on. It happened to me via the migration tool. Try setting those values to 0 and retry deploying static content.Notice here the 3rd row contains a row that doesn't exist in a default installation of magento 2 but appeared after migrating data. The value was 1 and I set it to 0 and it instantly generated the proper translations.
Hope it helps you