Was running Magento 2.0.0 CE on Nginx and PHP 7.0 without any apparent issues apart from the failing indexing due to memory leak which was a known issue. I've just tried to upgrade to 2.0.1 but the Update wizard failed which is also a known issue. So i tried a fresh installation of 2.0.1 CE and managed to install successfully. I can also confirm that the indexing problem is resolved. However, whenever I try to visit the Catalog/Customers pages in backend, I get an 'Attention - Something went wrong.' error. Using the browser's development tools I noticed that the Ajax call to "http://XXX.com/admin_cw/mui/index/render/key/2f135db323f1fb226c5db501df388b7c988d6bdda4132409b23450bc57d85d35/?namespace=customer_listing&search=&filters%5Bplaceholder%5D=true&paging%5BpageSize%5D=20&paging%5Bcurrent%5D=1&sorting%5Bfield%5D=entity_id&sorting%5Bdirection%5D=asc&isAjax=true"
is returning a 'Initialization error component, check the spelling of the name or the correctness of the call.' error (full stack below)
Can anyone help please?
`Initialization error component, check the spelling of the name or the correctness of the call.
A fresh install of 2.0.0 and problem is gone, re-installed 2.0.1 and the same issue occurs. I believe this is an issue related to just 2.0.1 on PHP7 maybe?
Did you find a solution about that ? I am using 2.0.2 CE with php7 and ran into the same issue ? ? ?
Yes, in our case it was a wrong nginx configuration. We were missing the part in bold
_location / {
try_files $uri $uri/ /index.php?$args;
}_
Hope it helps!
I am using apache 2.4 .... have no Idea what's wrong... maybe something with the .htaccess of magento or.... I don't know. Not exactly a server guy
Could be... I'm not a server guy either but I noticed that when a request was hitting our server, the query string part (the parameters after the '?') were being truncated which cause the symptoms above. Make sure there isn't any apache configuration which eliminates querystrings
Yeah, problem was that I made a reference class for controller that extended a Module_UI controller and at the end of my execute method of the reference class I made
parent::execute()
which apparently is wrong. Thanks for the replay though
@cgrechcw Thanks for reporting, it looks like a bug in Ui
Hello, I have same problem, on nginx and php 7?
location / {
try_files $uri $uri/ /index.php?$args;
}
this not helped me.
Hi @atomixstar ,
Looks like guys (@cgrechcw and @ barbala4o) fixed their issues.
If you faced with similar issue could you describe what exact problem you faced with?
Please, note:
According to contributor guide, tickets without response for two weeks should be closed.
If this issue still reproducible please feel free to create the new one: format new issue according to the Issue reporting guidelines: with steps to reproduce, actual result and expected result and specify Magento version.