Magento2: Magento 2.1.0 Fresh Install: Toolbar broken and errors

[toweringmedia]

On a fresh install of 2.1.0 after logging into admin navigating to the cms pages. The tool bar is broken at the top and I am getting the following in the debugger.

/~magento2/pub/static/adminhtml/Magento/backend/en_US/knockoutjs/knockout.js:3012 Uncaught ReferenceError: Unable to process binding "scope: function (){return bulk }"
Message: Unable to process binding "template: function (){return getTemplate() }"
Message: Unable to process binding "if: function (){return $parent.isActionsColumn($col) }"
Message: $col is not defined
toolbar.js:357 Uncaught TypeError: Cannot read property 'offsetLeft' of undefined

[toweringmedia]

updated title, I reinstalled and still have the same issue. Any help is appreciated.

[veloraven]

@toweringmedia , thank you for your report.
Unfortunately I was not able to reproduce this issue.
Could you please provide us details about your environment: versions of PHP, MySQL and web server?
Please also describe all steps you have done in more detailed way.
And if you can attach screenshot or some logs it may help as well.

[Melvin-de-Jong]

Hi,

We are having the same issue on a server. We did a clean install from Plesk 12.5 applications menu, we are running PHP 7.0.8 as FPM application served by Apache, MariaDB 10.1.14, on centos7 and Plesk 12.5.

We find the problem in the admin area of Magento 2.1.0 in pages and blocks overview.

I have tried:
-switching from developer to production mode,
-clearing cache with command bin/magento cache:clean
-running command rm -rf var/cache/* var/page_cache/* var/generation/*
-clean installing from plesk

none of these have worked.
I hope this helps in any way.

Kind regards,
Melvin de Jong
Vuyani Software

[ElliotGage]

Same issue... getting grid header formatting problems in product and pages admin with a javascript error:
toolbar.js:357 Uncaught TypeError: Cannot read property 'offsetLeft' of undefined

Version 2.1.0 command line installation. Older installs have gone fine.
CENTOS 7.2 x86_64
php 5.6
apache 2.4
5.6.30 - MySQL Community Server (GPL)

[ElliotGage]

I figured out why my site was having the above issue.
I had enabled mod_pagespeed long ago on my server. It was including javascript which interfered with the magento js includes.

Simple disable in .htaccess killed the problem.

[Melvin-de-Jong]

@ElliotGage I can confirm that this fixed the issue. Add ModPagespeed off in your .htaccess file and the problem is solved.

[clementbeudot]

Very nice guys, thank you for the solution. It helped me a lot.
Maybe we should write a warning note in the README.md about this ?

[PRAKASHSIVASANKAR]

Amazing Guys this awesome...

this issue fixed...

[bery]

Hi guys,

I would not call turning pagespeed of either in server config or .htaccess file a solution when it can be disabled for admin pages and kept on for frontend. Sample nginx pagespeed config that works for our use cases

pagespeed On;
pagespeed RewriteLevel CoreFilters;
...
pagespeed Disallow "*/admin/*"; ##your admin URL
pagespeed Disallow "*/backend/*";
pagespeed Disallow "*/adminhtml/*";

Please note that we are updating the config as we go and keep finding affected URLs

[ubedarab]

Thanks, your solution Fixed My issue, I had same issue, :) :+1:

[dmitriyprime]

Thanks for reporting this issue. Is it actual for you or we can close it?

[jcsgithub]

Hello guys,

Did a fresh install of Magento v2.1.7.
Saw that Catalog page is still broken so I added "ModPagespeed off" in the .htaccess file.
Then I also saw that Customer page is also broken, and the above fix didn't work the same.

Anyone having the same problem?

[magento-engcom-team]

@toweringmedia, thank you for your report.
This seems to be correct Magento behavior. Please refer to the Community Forums or the Magento Stack Exchange site for advice or general discussion about this.
Otherwise you may submit Pull Request with the suggested changes.

[okorshenko]

we will retest this again

[magento-engcom-team]

@toweringmedia, thank you for your report.
This seems to be correct Magento behavior. Please refer to the Community Forums or the Magento Stack Exchange site for advice or general discussion about this.
Otherwise you may submit Pull Request with the suggested changes.

[magento-engcom-team]

Closing as non-issue. Please see previous comment