500 Error After Moving WordPress
-
I’m working with a WordPress site that exists on both a staging and a development server. On the dev server, I updated WordPress and multiple plugins, confirmed everything was working smoothly, and then committed the changes to dedicated git branch. I then merged the branches in git. On the staging server, I duplicated all database-related work (creating pages, menus, etc.), and moved the file structure over via git. So, nothing in the database moved. .htaccess was in the .gitignore file, and so it did not move with the rest (the staging server had it’s own), as was the wp-conifg file. Upon loading the page after the git pull, I received a 500 error. This remained for approximately five minutes, and then the site seemingly recovered itself and began working. No cache plugins are currently running, and no caches are on the server installations.
I can confirm that the site was running without issue on both staging and dev servers prior to the git pull (and after db-related changes).
Anyone else ever experience this?
- The topic ‘500 Error After Moving WordPress’ is closed to new replies.