charle97

that’s trackback spam. you only switched the usual settings for new posts. trackbacks for posts prior to switch remain open.

what do you think awstats is?

did the traffic triple?

use a test wordpress install to do the upgrade prior to upgrading your production blog to see what breaks. after finding solutions to the breakage, upgrade the production blog or switch the test blog to your production blog if you used your production blog db as the db for your test blog.

prior to upgrading your production blog, test the upgrade using a separate wordpress installation.

did you change your nameservers to point to bluehost?

how to change your password using phpmyadmin

edit the permissions of the file to allow writing.

https://codex.www.ads-software.com/Changing_File_Permissions

use a php include

i know what you’re asking. i was trying to show you that you don’t need to worry about it, since it’s not a security risk.

if you insist on having wp-config.php file somewhere else then you’ll probably need to hack the core.

browse to wp-config.php. you should see a blank page.

make sure the index file appearing at https://msj2010.com has a .php extension (index.php)

open the index.php file in the root of your wordpress install

copy the require(‘./wp-blog-header.php’); line and paste to the top of the index.php file at https://msj2010.com

edit the path of the wp-blog-header.php file, most likely it would appear like require(‘./wordpress/wp-blog-header.php’);

edit the main index template of the classic theme and copy the code of the loop

paste the loop code where you want it to appear in the index.php file at https://msj2010.com

you have a forced redirect to your index.php file. look into your server setup or .htaccess file.

not a bug in wordpress. maybe a bug in feedwordpress. more likely your new host is using a mysql version that is not feedwordpress friendly.

you can convert the wp_blacklist_check function into your own plugin. use wp_die to output your desired error.