Brandon Olivares

Hi,

As far as I know, BackWPup does not support SFTP. It supports FTPS (FTP over SSL), but not SFTP over SSH. You’re trying to connect on port 22, which is an SSH port.

I have taken the data you gave above from HeidiSQL’s backup, and inserted it into my database. I then backed up that table using BackWPup, and imported it back into my database. The data is precisely the same both times, which I’ll demonstrate below.

The only difference is that HeidiSQL is casting the data to binary using _binary, and converting it to a hex string, whereas BackWPup escapes the data and inserts it as a string. Both seem to work equally from my testing.

mysql> CREATE TABLE IF NOT EXISTS wp_wffilemods (
    -> filenameMD5 binary(16) NOT NULL,
    -> filename varchar(1000) NOT NULL,
    -> knownFile tinyint(3) unsigned NOT NULL,
    -> oldMD5 binary(16) NOT NULL,
    -> newMD5 binary(16) NOT NULL,
    -> stoppedOnSignature varchar(255) NOT NULL DEFAULT '',
    -> stoppedOnPosition int(10) unsigned NOT NULL DEFAULT 0,
    -> PRIMARY KEY (filenameMD5)
    -> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.00 sec)

mysql> INSERT INTO wp_wffilemods (filenameMD5, filename, knownFile, oldMD5, newMD5, stoppedOnSignature, stoppedOnPosition) VALUES
    -> (_binary 0x00052637AA911325611628FE89731222, 'wp-content/plugins/ultimate-faqs/Functions/Register_EWD_UFAQ_Posts_Taxonomies.php', 0, _binary 0x1ABD78AC67ECAA54229E30472935D245, _binary 0x1ABD78AC67ECAA54229E30472935D245, '', 0),
    -> (_binary 0x0013DF4075189CA59C3205B6EE58E7B6, 'wp-content/plugins/contact-form-7/modules/date.php', 1, _binary 0x00000000000000000000000000000000, _binary 0x5684AD43D143309760C0EE321B08671F, '', 0);
Query OK, 2 rows affected (0.01 sec)
Records: 2  Duplicates: 0  Warnings: 0

mysql> 

Then if I select this data it looks like this (only selecting the filenameMD5 column for simplicity’s sake):

mysql> select hex(filenameMD5) as filenameMD5 from wp_wffilemods;
+----------------------------------+
| filenameMD5                      |
+----------------------------------+
| 00052637AA911325611628FE89731222 |
| 0013DF4075189CA59C3205B6EE58E7B6 |
+----------------------------------+
2 rows in set (0.00 sec)

mysql> 

This is exactly what your above data looked like, so this is good.

After running a job on this table only, here is the file output (relevant lines only):

--
-- Table structure for wp_wffilemods
--

DROP TABLE IF EXISTS wp_wffilemods;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = 'utf8' */;
CREATE TABLE wp_wffilemods (
  filenameMD5 binary(16) NOT NULL,
  filename varchar(1000) NOT NULL,
  knownFile tinyint(3) unsigned NOT NULL,
  oldMD5 binary(16) NOT NULL,
  newMD5 binary(16) NOT NULL,
  stoppedOnSignature varchar(255) NOT NULL DEFAULT '',
  stoppedOnPosition int(10) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (filenameMD5)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Backup data for table wp_wffilemods
--

LOCK TABLES wp_wffilemods WRITE;
/*!40000 ALTER TABLE wp_wffilemods DISABLE KEYS */;
INSERT INTO wp_wffilemods (filenameMD5, filename, knownFile, oldMD5, newMD5, stoppedOnSignature, stoppedOnPosition) VALUES 
('\0&7a‘%a(t‰s\"', 'wp-content/plugins/ultimate-faqs/Functions/Register_EWD_UFAQ_Posts_Taxonomies.php', 0, '\Z?x?gìaT\"?0G)5òE', '\Z?x?gìaT\"?0G)5òE', '', 0),
('\0?@u?￥?2??X??', 'wp-content/plugins/contact-form-7/modules/date.php', 1, '\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0', 'V?-C?C0—à?2g', '', 0);
/*!40000 ALTER TABLE wp_wffilemods ENABLE KEYS */;
UNLOCK TABLES;

Now if I import this file:

$ mysql -h dbhost -u dbuseruser -p dbname < backup.sql 
Enter password: 
$

No errors. Now I’m running the same query as above:

mysql> select hex(filenameMD5) as filenameMD5 from wp_wffilemods;
+----------------------------------+
| filenameMD5                      |
+----------------------------------+
| 00052637AA911325611628FE89731222 |
| 0013DF4075189CA59C3205B6EE58E7B6 |
+----------------------------------+
2 rows in set (0.00 sec)

mysql> 

What are you using to import your data? Is it possible that that could be messing with the encoding of that data? From the above I’m not seeing any issues on BackWPup’s end. Backing up of the data as well as importing seemed to work perfectly fine on my end.

All pointers indicate that it is being saved as UTF8. It’s possible that whatever you’re using to view it is just garbling the characters. Have you tried importing it to a test database and seeing if it imports properly?

You’ll need to look at your log files to see what the exact issue is. If you can’t figure it out, then you might want to generate a debug log file and send it to BackWPup. This document will tell you how to do that.

Okay, in your sql file, what is listed as the charset? For instance, in the header I have this:

/*!40101 SET NAMES utf8 */;

And before each table I have this:

/*!40101 SET character_set_client = 'utf8' */;

Do you have the constant DB_CHARSET set in your wp-config.php? Setting this to utf8 may help. The plugin uses the default charset if none is defined.

You can select the type of compression, but all jobs use some sort of compression, as it saves a lot of disk space.

You say you only have 45 blog posts, but what about media? Are you uploading your wp-content/uploads folder? Sometimes if there’s a lot of large media files, that could increase the time to compress.

What exactly is the error you’re experiencing?

Just looking at your info, it looks like curl is disabled, which might be needed depending on the backup destination.

No, I’m actually on DreamPress. So what can I do to get it to work?

Just did, and you can see the results here.

It still double links it.

Thanks so much.

Something else I noticed, not sure if you already fixed this or not, but if I have a link like:

<a href="https://example.com/"><em>Book Title</em> by [author]</a>

If the Book Title is one of my auto-links, then it’ll double link it as well. Hope that makes sense.

Thanks. I’ll try that out. ??

Okay, so enabling the setting to purge comments did not help.

I notice that when someone comments, and it caches their name/email, if I then comment from the admin dashboard on the comments page, it clears the cache and the form is clear.

But still can’t track this down. Any other suggestions?

Thanks, already done. I’ll see what the new settings do with the comment issue and report back if necessary. ??

Yes I’m on a Genesis theme, which uses fragment cache.