Difference between revisions of "SBN - Blog Server Notes"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
*[[BlogServer - WordPress Installation|WordPress Installation]] | *[[BlogServer - WordPress Installation|WordPress Installation]] | ||
| − | == Potentially Useful Links == | + | ==Potentially Useful Links== |
| − | * [https://wordpress.org/support/article/editing-wp-config-php/ Editing wp-config.php] | + | *[https://wordpress.org/support/article/editing-wp-config-php/ Editing wp-config.php] |
| − | == Problems Solved == | + | ==Problems Solved== |
| + | |||
| + | ===WP_Filesystem is not available=== | ||
When WP shows you this very helpful screen: | When WP shows you this very helpful screen: | ||
[[File:WP Bullshit-1.png|none|thumb|600x600px]] | [[File:WP Bullshit-1.png|none|thumb|600x600px]] | ||
| Line 16: | Line 18: | ||
([https://chap.website/wp-filesystem-api-help/ Reference]) | ([https://chap.website/wp-filesystem-api-help/ Reference]) | ||
| − | <br /> | + | ===Error establishing a database connection=== |
| + | Check your credentials. Simple as that. | ||
| + | |||
| + | Most common reasons for this error are either that the database server isn't running (possible, but not #1) or that you've messed up the user name or password for accessing the database.<br />(It IS also possible that you've told WP to access the database by the wrong name or on the wrong server... Check those items too.) | ||
Latest revision as of 02:01, 18 July 2020
Contents
Potentially Useful Links
Problems Solved
WP_Filesystem is not available
When WP shows you this very helpful screen:
Open up wp-config.php and add:
define('FS_METHOD', 'direct');
at the bottom.
Error establishing a database connection
Check your credentials. Simple as that.
Most common reasons for this error are either that the database server isn't running (possible, but not #1) or that you've messed up the user name or password for accessing the database.
(It IS also possible that you've told WP to access the database by the wrong name or on the wrong server... Check those items too.)
