mikeschumann

I just tried another test. It appears that if I try to login using a non-existent username but a blank password, I get the Yellow Live Traffic Icon and my IP address is not blocked. If I do the same thing with a non-blank password, then the Live Traffic log shows a Red X and the IP address is blocked.

Personally, I think that all login attempts to a non-existent username should be blocked, regardless of whether or not a password is present.

I am having the exact same problem. I have configured the free version of Wordfence to immediately block all login attempts to non-existant user names for two months. When I test this myself, it seems to work fine.

However, today I looked at the Live Traffic log and see a LOT of failed login attempts to non-existant user names. Most of these entries have a yellow warning, not a red X. The IP addresses for the Live Traffic entries with the Yellow Warning icon are not blocked. The entries with the Red X icon are.

What is the difference in the Live Traffic log between the Yellow Warning and Red X log entries? Why are the Yellow Warning failed logins not resulting in the IP addresses being blocked?

I checked with the administrator panel. I’ll double check the database. Username was not in the database either.

• This reply was modified 4 years, 4 months ago by mikeschumann.

I ran another test. I converted my website’s WordPress MySQL 5.5 database to 5.7 using the process outlined in the IONOS help files (Exporting the database using phpMyAdmin, and the Importing the file into a new MySQL 5.7 database). I then updated the WordPress wp-config.php file with the new database info. Once I did this, I tested the website. I then ran duplicator on this website and created a new package for this MySQL 5.7 based website. I then tried to install this package on an IONOS website using a MySQL 5.7 database. I ended up getting the exact same errors as before.

Bottom line, the problem is not related to a mismatch of MySQL database versions, but rather a result of trying to install a Duplicator package using a MySQL 5.7 database. I’m not sure if this is an IONOS only problem, or if this is more widespread than that.

I ran a test with an old MySQL 5.5 database that I no longer needed in my hosting account. The website installed correctly. My problem is definitely the result of trying to install a Duplicator package that was created with a MySQL 5.5 database to a new site using MySQL 5.7. Any suggestions on how I can solve this problem?

One additional note: The WordPress site that created the duplicator package uses MySQL 5.5. The database for the new site is MySQL 5.7. Not sure if this has anything to do with my problem.

PHP Mode was selected when I created the package.

I’m having exactly the same problem duplicating a 1and1.com site. This used to work just fine a couple of months ago. Is there any more info on how to fix this?

That’s not my experience.

I got a clarification from Mailchimp on why I am not receiving e-mail notifications when someone subscribes using this plugin.

According to Mailchimp, the e-mail notifications are only sent to the list owner if a person signs up using the double opt-in process. If the person subscribed using an application or plugin that uses the Mailchimp API, without going thru the double opt=in process, they consider this identical to importing a name into the list, which would not trigger a subscription e-mail to the list owner.

Other than that, the plugin seems to be working fine. It does typically take a couple of minutes however, for subscribers to become visible in the Mailchimp mailing list after the subscription has been completed.

Good news. It appears that the plug DOES work. It just takes a couple of minutes for new subscribers to show up in the Mail Chimp list after you have subscribed using the plugin.

However, e-mail notifications aren’t happening for each new subscriber. It’s not clear if this list setting applies to subscriptions that occur thru the Mailchimp API.

Yikes! I just did another couple of tests, and the names don’t get added, even though the widget says that the signup was successful. I initially thought the problem was that I just wasn’t getting the notifications, but now it looks like the signup doesn’t work at all!

I have tested this with the latest WordPress Release (3.5.2) and the Twenty Twelve theme.

When you restore an older version of a post, the custom fields are not restored. The Custom fields for the post remain unchanged from the newest version of the post.

This is obviously a bug in WordPress that should get fixed.

That needs to be addressed in a future release!!!!