1. it’s been a month and user (me) still have to guess why plugin doesn’t work. If it’s just a matter of notice, could you please release a patch?
2. importing your sql doesn’t work for me. Error: ERROR 1067 (42000) at line 4: Invalid default value for 'comment_date'
SQL code is this:
DROP TABLE IF EXISTS
wp_comments`;
#
# Table structure of table wp_comments
#
CREATE TABLE wp_comments
(
comment_ID
bigint(20) unsigned NOT NULL AUTO_INCREMENT,
comment_post_ID
bigint(20) unsigned NOT NULL DEFAULT ‘0’,
comment_author
tinytext COLLATE utf8mb4_unicode_ci NOT NULL,
comment_author_email
varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
comment_author_url
varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
comment_author_IP
varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
comment_date
datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
comment_date_gmt
datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
comment_content
text COLLATE utf8mb4_unicode_ci NOT NULL,
comment_karma
int(11) NOT NULL DEFAULT ‘0’,
comment_approved
varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ‘1’,
comment_agent
varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
comment_type
varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
comment_parent
bigint(20) unsigned NOT NULL DEFAULT ‘0’,
user_id
bigint(20) unsigned NOT NULL DEFAULT ‘0’,
PRIMARY KEY (comment_ID
),
KEY comment_post_ID
(comment_post_ID
),
KEY comment_approved_date_gmt
(comment_approved
,comment_date_gmt
),
KEY comment_date_gmt
(comment_date_gmt
),
KEY comment_parent
(comment_parent
),
KEY comment_author_email
(comment_author_email
(10))
) ENGINE=InnoDB AUTO_INCREMENT=41 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci ;`
I have compared it with default mysqldumps that works fine, and found that for it to work, there should be
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
before, and
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
after whole sql dump.
There are other presets changed in mysqldump that you do not change, they also seem to have a safer way of importing, using some locks when inserting.
I have no idea what’s going on, I’m no SQL expert, but this totally feels like using search&replace is not safe, functionality of “Search & Replace” (2nd tab) just dies silently, and functionality of “Replace Domain URL” (3rd tab) produces dead dump that can’t be imported…
Can you do something about it?
Why do you “protect” me in the first place? I have already changed my site scheme from http to https, now only thing I want is fix all the images and links (and maybe something occasional else). If your plugin does it’s job right, why would I need “protection”? Are you totally sure that’s a feature, not a bug? I’m not.