hallo u. guten Abend,
ein oben beschriebener Fehler: . er kann auch in Abhängigkeit von speziellen Themes ( oder Plugins ) auftreten.
gemäß dieser Anleitung .... kommen einige Dinge in Betracht.
Und - die Geschichte mit den Plugins (Themes) - die hatte ich früher auch schon einmal....
https://websitesetup.org/error-establis…ase-connection/
If the error message is the same on both pages “Error establishing a database connection”, then proceed onto the next step. ... The database may need to be repaired”, then you need to repair your database. You can do this by adding the following line in your wp-config.php file. Add it just before 'That's all, stop editing!01.03.2019
https://websitesetup.org/error-establis…ase-connection/
Step 2: Check If Your Plugin or Theme Files Haven’t Been Corrupted
Your WordPress files might get corrupted as a result of a couple of misfortunate events.For instance, maybe you’ve updated a plugin or a theme, and the whole thing collapsed? Maybe you hooked the site up to an external service? Maybe you hand-edited some of the files?
If any of the above ring a bell, you probably have your culprit. If you haven’t done any of that, skip this step.Here’s what you can do:
1. First, connect to your host via FTP. You can do this with a free tool called FileZilla.
In order to connect, you need a login and a password to your FTP account. If you don’t know what/where those are, the easiest way to get them is to search through the initial emails that you got from your web host when you first signed up. Alternatively, you can ask the live chat support representative to give you those details.Having them, connect to the server and navigate to the WordPress root folder. It’s usually called “public_html” or “www” or you might be in it already once you establish the FTP connection.
The rule of thumb is that if you can see sub-folders like “wp-content” and “wp-admin” then you’re in the WordPress root. Example:
WordPress root
2. Go into “wp-content” and rename the “plugins” folder to something else (whichever other names, as long as it’s not “plugins”):
rename plugins3. Go back to your site and see if the error is still there.
If not, you now know that it’s been caused by some plugin. Go back to FTP, rename the folder back to “plugins”. Go in it, and change the folder names of the individual plugins, one by one. The easiest way to do this is to add an underscore at the end: “_”name changed
Keep coming back to your site to see when the error gets triggered or vanishes. Once you’ve narrowed it down to one specific plugin, you have found the troublemaker. Either delete it or go online to see if the solution has been documented.
If the error is still there even after renaming the “plugins” folder, go through the exact same process with the “themes” folder.If that doesn’t help, rename both folders back to “plugins” and “themes”. The error is caused by something else.
Step 3: Check If---.....
Ich bin derzeit diesem Fehler auf der Spur - und stelle fest dass auf dem Server mehrere Seiten laufen - andere aber nicht.
- Könnte Theme bzw. plugin-Abhängig sein.
Ich werde das jetzt weiter überprüfen.
VG