Common Issues
Last updated
Last updated
The issue appears when you have an incorrect theme path in the theme configuration in the database.
To fix the issue follow the steps below:
Open core_config_data table and find a row with design/theme/theme_id path value.
Open theme table and find a row with theme_id value corresponding to value from the previous step.
Make sure that theme_path value is the same as the one declared in your theme's registration.php file. (for ScandiPWA it will be likely scandipwa/scandipwa)
An error message should look like this:
This issue happens when env.php file is missing.
This issue might appear at the first start of the project.
This issue might appear if you, for some reason, have no Magento database installed in MySQL.
This issue might appear if your port configuration has changed but Magento still uses old configuration.
There are 2 options on how to solve such a problem:
Recommended, as it is the safest option.
Not recommended, because you will lose all the configuration from that file.
This issue might appear if you have a theme installed but persisted queries are not set up for some reason.
This issue might appear if you have previously installed Magento with CMA but now lost all the data in MySQL for some reason.
Connect to your database using the database client. (like )
You can get host, port and credentials after running the command.
Run command the second time.
Run command the second time.
Delete app/etc/env.php file, after that run command.
This will force CMA to reinstall Magento but you will lose some configuration, for example, a persisted query that is required for the ScandiPWA theme.
Get current port configuration from docker ps or command and edit app/etc/env.php file and run the command.
Delete app/etc/env.php file and run the command.
Run command to re-link the theme and setup persisted queries.
Delete app/etc/env.php and run the command again.
