![]() When visitors try to access your site while this error is happening, it will generate a 500 HTTP status code in your logs. ![]() And in cases like the above, the frontend of the site in most cases (unless you have a script or part of your site breaking the cache) would stay up a lot longer. ![]() If you have a site that doesn’t change very often, this can increase your site’s performance as it does not have to grab new files as often after the cache expires. Therefore, if a site is still serving from the cache, it might appear acceptable to a visitor.Īt Kinsta, our support team can increase the duration of your cache to, say, an hour or even a week if you want. For example, at Kinsta, all WordPress sites are cached for one hour by default. That is because your site is most likely still serving from cache until it expires. However, visitors might not see this error on the frontend right away. “Error establishing a database connection” message in Chrome. Not only does this break the frontend of your site, but it will also prevent you from accessing your WordPress dashboard. The entire page is blank because no data can be retrieved to render the page, as the connection is not working properly. If this isn’t working correctly, you are left with the “error establishing a database connection” message, as seen below. When someone visits your website, PHP executes the code on the page, queries the information from the database, and then displays it to the visitor in their browser. The only data not stored there is media content such as images and your theme/plugin/core files such as index.php, wp-login.php, etc. This is how it works: all the information on your WordPress site, such as post data, page data, meta information, plugin settings, login information, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |