1

When I login to my backend I get a white screen and an Update Message for 2.0.3.

The message can't be removed. Backend ist not working anymore. Magento 2 was in a password protected folder. I removed the password protection now. But it is still not working.

Magento Community Edition 2.0.3 Includes Functional and Security Updates – 3/30/2016

1

This sounds like a problem with your deployment/cache. Try these steps;

  • clear/delete the /var/ folder
  • clear the cache (magento cache:clean via the CLI)
  • run the magento setup:di:compile command via CLI

Then refresh the page, it should be working again. Most of the time these errors seem due to invalidated/corrupted or incomplete deployment of JavaScript files.

Edit: I had another similar issue today, where there were no errors of any kind. At last I found permission-related issues in the serverlogs. When I fixed the permissions, all was working again!

  • Thanks, the second 2 didn't help. Can I delete the whole var folder? Will it be created again? – Oliver Schmid Mar 31 '16 at 8:20
  • But the first did the trick, or not? – Alex Timmer Mar 31 '16 at 8:20
  • No, I didn't try yet. Are you sure I can delete everithing in the var folder? – Oliver Schmid Mar 31 '16 at 8:34
  • Yes, absolutely. This has always been possible in Magento1 and also Magento2. I've been deleting my /var/ folders every day for weeks now during development to fix these kinds of errors :) All the /var/ container holds is session info, cacheing of files etc. Every time you delete this folder, you force Magento to regenerate all that stuff, fixing the most obvious errors like blank pages. Matter of fact, I had the same white-page a few minutes ago, – Alex Timmer Mar 31 '16 at 8:36
  • After that, if you still can't update, check this answer: magento.stackexchange.com/questions/108740/… – Alex Timmer Mar 31 '16 at 8:42
0

I spent 8 hours trying 1000 ways to delete the cache. But after login I still got the blank screen with the message. Finaly I removed everything on the server and installed all new again.

  • did this give solution? – Amit Bera Apr 1 '16 at 10:21
  • Yes, but not very good for people with productive shops. – Oliver Schmid Apr 1 '16 at 10:47
0

I could solve the problem. It was a wrong location time in configuration. Changing from to attributes was also not possible.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.