In this tutorial i will show you how the Magento 2.3 admin blank page issue get solved.

Let’s do this practice step by step.

This issue mainly occurred during up-gradation, migration or perform a fresh Magento 2 installation whether it is Community Edition or it can be Enterprise Edition, you have seen that well known blank page issue that displays nothing on the front end and also occur some time in back end

And also this issue occur after installation of Magento 2.3 .Best way to install the Magento 2.3 is can be done via composer.

Command which is executed in cmd or git bash to install Magento 2.3 are as follow as:

$ composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition install-directory-name

example :

$ composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition magento235/

Second to install Magento 2.3 execute below command:

$ bin/magento setup:install \--base-url=http://localhost/magento235\--db-host=localhost \--db-name=magento \--db-user=magento \--db-password=magento \--admin-firstname=admin \--admin-lastname=admin \[email protected] \--admin-user=admin \--admin-password=admin123 \--language=en_US \--currency=USD \--timezone=America/Chicago \--use-rewrites=1

After which installation blank page issue (magento 2.3.5 admin blank page) occur. This is Magento bug. Wrong paths to Windows are generated. The fixed fix is

Solution to Magento 2.2.7 and 2.3 – 2.3.5 Admin Page Blank Issue:

How to solve the issue:

Navigate to: /vendor/magento/framework/View/Element/Template/File/Validator.php:113

the string

$realPath = $this->fileDriver->getRealPath($path);

to replace

$realPath = str_replace('\\', '/', $this->fileDriver->getRealPath($path));

Then go to var/cache , delete all folder / file

Run following command

bin/magento indexer:reindexbin/magento setup:upgradebin/magento setup:static-content:deploy -f

refresh the page, done.

From below video tutorial you can check how issue is fixed practically.

Solution is currently (Fast solution) the way to hack core code to get 2.3 working in a windows environment BUT it will be reverted when you get a Magento update to whatever they have changed it to or back to the original. This is currently best practice is to use a form of virtual machine and vagrant like service with a linux operating system. This is not the immediate and quickest way but it is the best way to keep working without putting your workflow as risk in the future by hacking a fix into core code

Magento Blank page issue some time occur in both front and back end.