Data collection
According to the troubleshooting process that we have been following, the next step is to gather as much data as possible around the issue. One of the best sources of information is the person reporting the issue; for this situation, we will ask two basic questions:
How can I duplicate the issue and see the error?
Has anything changed recently with the WordPress application?
When asked, the developer states that we can see the error simply by going to the blog in the web browser. On the second question, the developer informs us that the database service was recently moved from the webserver to a new dedicated database server. He also mentions that the move happened several days ago and that the application was working until today.
Since the database service was moved several days ago and the application was working up until this morning, it is not likely that this change caused the issue. However, we should not discount this as a possibility.
Duplicating the issue
As discussed...
