Trouble restoring SQL backup

Hi wslade,

Thank you for this information! I deleted all the WP files and made a fresh install to the same directory and edited the wp-config.php file per your instructions. Weirdly, however, this does not seem to change anything. Both the blog page and the admin console look the same. I am wondering if I need to make some other changes to the file, as it differs from the earlier one in couple of other ways.

This if from the current wp-config.php:

[ Moderator note: code fixed. Please wrap code in the backtick character or use the code button. ]

/**
 * WordPress Database Table prefix.
 *
 * You can have multiple installations in one database if you give each a unique
 * prefix. Only numbers, letters, and underscores please!
 */
$table_prefix = 'wp_zpfi_';

/**
 * For developers: WordPress debugging mode.
 *
 * Change this to true to enable the display of notices during development.
 * It is strongly recommended that plugin and theme developers use WP_DEBUG
 * in their development environments.
 */
define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

/**
 * Include tweaks requested by hosting providers.  You can safely
 * remove either the file or comment out the lines below to get
 * to a vanilla state.
 */
if (file_exists(ABSPATH . 'hosting_provider_filters.php')) {
include('hosting_provider_filters.php');
}

This is from the old one:

/**
 * WordPress Database Table prefix.
 *
 * You can have multiple installations in one database if you give each a unique
 * prefix. Only numbers, letters, and underscores please!
 */
$table_prefix  = 'wp_';

/**
 * WordPress Localized Language, defaults to English.
 *
 * Change this to localize WordPress. A corresponding MO file for the chosen
 * language must be installed to wp-content/languages. For example, install
 * de_DE.mo to wp-content/languages and set WPLANG to 'de_DE' to enable German
 * language support.
 */
define('WPLANG', '');

/**
 * For developers: WordPress debugging mode.
 *
 * Change this to true to enable the display of notices during development.
 * It is strongly recommended that plugin and theme developers use WP_DEBUG
 * in their development environments.
 */
define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php’);

Do you have any ideas? Or is there any other information I can provide that would be of help debugging?

Many thanks,
Patrick

Thanks for the quick response! The URL is http://www.ijfab.org/blog/.

It now functions as a fresh install. (I just put up our banner and tweaked the color scheme a little.)

The weird thing is that I did change the info in wp-config.php so that it points to the old database with the appropriate pw, but, as far as I can tell, nothing changed. Nothing. I was expecting to get either a really messy version of my old page (missing graphics and visually distorted in who knows what other ways) or else an error saying that the whole thing was inaccessible, contact system admin, etc.

Oh, and I did just check phpMyAdmin, and the old database, to which my current wp-config.php points, does indeed look to still contain all my old content. The only other SQL database is the new one that was installed with the clean install this morning.

The blog/wp-config.php is pointing to the SQL database with years worth of content stored in it. I changed all of these fields to match those from the wp-config.php of an old version of the file from when the site was still working (even if, for several months, we were infected and being used as some kind of a mirror server for an pharma site based in Russia).

[ Moderator note: code fixed. Please wrap code in the backtick character or use the code button. ]

define('DB_NAME', ------------');

/** MySQL database username */
define('DB_USER', '------------');

/** MySQL database password */
define('DB_PASSWORD', '------------');

/** MySQL hostname */
define('DB_HOST', '------------');

I notice, as you will see above, that these value was also changed for “$table_prefix =” and also that this:

is appended to the end of my current file, but is not in the original.

I figured out part of the problem. The database contains a bunch of different table prefixes, which seem to correspond to at least some of the multiple installs I’ve done trying to correct this. When I changed the $table_prefix value from ‘wp_zpfi_’ to ‘wp_’, the site went blank–but I can see all my content when I log in as admin!

If you or anyone else knows how what I need to do to make it appear properly, please do share; otherwise I will tinker around a bit and see if I can figure it out myself before posting further inquires.

Once again, thank you so much for all of your help! We had come to believe that all of this was lost!

Best regards,
Patrick

I mean that the content is all there when I log in as through /wp-login.php. In fact, I updated my theme, and now the site looks great–expect that you cannot click through to view full posts. Something amiss with the permalinks? Or else…?

Also, Jetpack goes haywire every time I try to connect to WP.com, plug-ins are gone, etc. But still, this is progress. I’m feeling increasingly optimistic.

Thanks, I will definitely install those programs/add-ons/whatever. You don’t have any idea about why you “read more” takes you to a dead page do you?

I exported the data from that version of the blog and made another one here: http://www.ijfab.org/testblog/. Here, you can click through to view the full posts (even if they are all attributed to me–I think I can fix that if I decided to do yet another clean install on the /blog directory), but the permalink URLs have all changed and other widget preferences, etc. are gone.

My preference would be to do a little more work to fix the first one that has all the user info, etc. saved, but access to the full content is much more important–even if this means that I need to manually redo the other stuff.

It found no malicious files, just the “potentially” malicious files listed below, which they would like me to pay them to analyze. I really did delete all of the files and start from scratch, uploading only images from the original site (and the html and css files that comprise the website, http://www.ijfab.org). Unless the trojan made its way into the SQL database, I’m inclined to think the site is infection-free. The more likely problem, I suspect, is that the database is trying to refer to files that do not exist on my clean install…

Total Scanned Files: 1790
Total Unsafe Files: 5

File with malicious codes
/wp-content/plugins/w3-total-cache/pub/files.php
/wp-content/plugins/mojo-marketplace-wp-plugin/inc/spam-prevention.php
/wp-content/plugins/w3-total-cache/lib/CSSTidy/data.inc.php
* * * * * FREE REPORT LIMITS * * * * */data-wp.inc.php
* * * * * FREE REPORT LIMITS * * * * */data.inc.php