John Sundberg

Try this; it should be fully responsive too.

.home-widgets .home-widgets-5 .widget {
text-align: left;
}

.home-widgets-5 .enews .widget-title {
margin-bottom: 0;
}

.home-widgets-5 .enews {
margin: 0 auto;
max-width: 90%;
width: 400px;
}

.home-widgets-5 .enews input {
width: 100%;
}

.home-widgets-5 .enews input[type="submit"] {
width: 200px;
}

I’m running into a similar issue, though the confirmation emails are being sent.

The widget is in the footer, and when a user submits the sign-up form the page reloads and stays at the top. If the user were to scroll down they would see the MailPoet confirmation notice, but that’s asking a lot for most users, probably.

MailPoet’s built-in widget handles the confirmation notice nicely with some AJAX, I believe, leaving the page in the same position and displaying the confirmation notice where the user would expect to see it, though eNews is the better widget overall.

Any chance we can see this same behavior with eNews Extended and MailPoet?

Forgot about that default form!

No, this site is a unique set-up where the client wanted to allow users to register who (supposedly) don’t have email addresses, so I did some custom coding that assigns a default email address to anyone who checks that option on the registration form. So there’s only one email address that’s allowed to be used for multiple users. And it’s an email address that doesn’t actually exist.

But your questions reminded me that I’m also running Theme My Login, and there’s a setting in that plugin to disable the admin notification email for new users. I selected that option, thinking that TML and GF User Registration were BOTH sending the email, and that solved the problem.

Thanks for the nudge in the right direction!

v3.0.1 fixed the warning for me. Still getting two New User Registration emails but I can live with that.

Thanks for the update!

If I may add my voice to this thread, I’m getting the same first warning, but not the second.

Warning: mysql_real_escape_string() expects parameter 1
to be string, object given in /wp-includes/wp-db.php on
line 1036

However, I’m seeing this on the front end and not in the admin. I’m using Gravity Forms and their User Registration Add-on. When the registration form is submitted, the warning is displayed but the user is still registered.

Something to note though, I think AMA’s count_multiple_accounts function is being called twice during this process, once without the user ID, and the second time with the new user ID.

I came to that conclusion two ways:

1. I’m receiving two New User Registration emails from WordPress with the same info in each email, for each registration.

2. I modified the code in that function to echo the $sql variable, and it prints out the SQL string without the ” AND ID != %d”, and then with it, all in one line.

When I comment out the line in that function that includes $wpdb->prepare, the warning doesn’t appear.

Don’t know if that will help. I worked on the AMA code for a while last night trying to solve this, but I need to move ahead with some other aspects of this project now.

And Scott, thanks for the helpful plugin!