This can be done by entering the htdocs directory and click the WordPress installation folder, open the wp-config.php file and check to see that the $table_prefix variable for both sites are different. You can see if this is the case by checking each site’s wp-config file. Normally, WordPress will pick up on a table prefix being used twice but it doesn’t hurt to check. If both of the WordPress sites are using the same database, then I’d also make sure that the table prefixes for the sites are different.
#Mamp wordpress files could not be moved update
Then, run wp core update-db to update the database. Assuming you don’t have a root user using the database, then you may try checking the permissions for the database user just to make sure it has the appropriate permissions for using the database. To be able to update an older website to latest WordPress, you could try one of the following alternatives: Fully-automated: Run wp core download -force to download latest WordPress and replace it with your files (don’t worry, wp-config.php will remain intact). You may try checking if the server did in fact start, as the Apache server alone may have loaded.Īnother reason why this could be happening is your database user doesn’t have correct permissions for the database defined in the wp-config.php file.
![mamp wordpress files could not be moved mamp wordpress files could not be moved](http://support.typora.io/media/files/Screen%20Shot%202019-01-24%20at%2023.39.15.png)
![mamp wordpress files could not be moved mamp wordpress files could not be moved](https://mythemeshop.com/wp-content/uploads/2020/05/best-wordpress-migration-plugin.png)
The first reason is that the MySQL server was not able to start whenever you first started up MAMP (it will load up the Apache web server and MySQL server). This error regarding WordPress not being able to connect to the database could happen for multiple reasons.