New answers tagged

0

If you have no database backups then you're going to have to start from scratch. The database cannot be recreated from the uploads folder and plugin/theme files.


1

As in this question and answer, and because of your huge .htaccess file it's like you have a .htaccess directive that's causing your apache to not process that file or understand its type. As mentioned by @Rup, using the default Wordpress .htaccess, and checking other directories for rogue .htaccess files will likely resolve this issue. If it doesn't, you ...


2

Yes, you can safely delete that file. It's a template of what a minimal wp-config.php looks like, so as soon as you have a working wp-config, you don't need it. It will never be restored unless you reinstall Wordpress from scratch, e.g. by downloading and unpacking a clean Wordpress installation. If for some reason you need to refer to it in the future, then ...


0

Sorry to bump an old post but is there not just an obvious solution to all this. We know there is some security benefits from moving the wp-config.php file out of the wordpress route directory. Some would argue that the benefits are minimal others would not. On the flip side there can be some drawbacks to moving the file out of it's default location such as ...


1

These fields have the keys 'blogname' and 'blogdescription' respectively in the options table. I'm not sure exactly why you need to do this as it seems like a priority to secure your site and be able to update it through the dashboard yourself, but you can update them easily from functions.php with update_option, e.g.: update_option( 'blogname', "site ...


0

In my case, there were a plugin that force redirect to https. So, also check if any plugin is active and redirect requests to https.


Top 50 recent answers are included