Debugger

When trying to validate the Facebook settings I get:
“Error: cURL error 28: Connection timed out after 10000 milliseconds”

I was going to ask the same thing.

Screenshot of the notification:
https://s7.postimg.cc/e6j4xtofv/review.png

I had this option set.
The problem is that the import of the emails in Mailpoet is through the web browser, so this does not solve the problem.
Any other ideas?

Yes, I tried to make a call to the graph API, but I noticed that link field is not working (404).

Anyway, thank you for the reply and have a great day!

Thanks!

Thanks!

@till Krüss
I will pay for this.

How can I reach You?

Anyone?

Sure, but this should be patched immediately as it breaks the plugin functionality.
We should not wait 7 days until next scheduled update…

OK, I found the problem by myself. It’s because of this plugin:
https://www.ads-software.com/plugins/block-temporary-email/
it was passing each and every single email address through his API and that’s why the procedure of importing new users was failing.

Case closed.

PS. I am really disappointed with the premium support.
For nearly 48 hours I received a single reply from Mailpoet team, suggesting to enable WP_DEBUG…
Even that the problem was not caused by Mailpoet plugin, the support should be more responsive and quick…

I am a paying customer with 3 active licenses and more than 24 hours I cant use your plugin properly. Terrible support!

Still waiting for a reply to at least one of my tickets.

PS. I Just checked the code located in \includes\providers.php

        $username = strtolower($first_name . $last_name);
        if (empty($username)) {
            $username = strtolower($name);
        }
        if (empty($username)) {
            $username = str_replace(array(
                '@',
                '.'
            ), '', strtolower($email));
        }

The part where you parse the username from the email is not a good idea. The email is something private and using it to build a login name will make it publicly available to all others, that can see your username.

Hello,
thanks for the quick reply!

On your first question, yes that’s what I propose. The possibility of setting custom default username in the admin area. And also, always to include the prefix. In my case, I depend on that prefix to execute some custom actions for these users. But anyway, it will be much more consistent if all users have it, right?

The problem really occurs when there are too many users with the default name in the DB. $username . $index in this case $index can always be replaced with the provider ID or simply with build in rand(). It will do the trick in both cases.

If a feature is introduced, in my opinion, it should prepend the prefix before inserting the username to the db.

Thanks for the suggestion about the Cyrillic usernames, but I prefer to keep all usernames in Latin. It simplifies searching and adding custom scripts that manage these users.

dupe
problem already solved

• This reply was modified 6 years, 9 months ago by Debugger.

Hello,
thanks for the quick reply.
Actually, the SMTP plugin was the one to blame. It was previously overwriting the sender name but after the last update, it suddenly stopped.
Anyway, a simple function solves the problem.
Have a great day!

PS:

function change_mail_sender( $original_email_from ) {
    return get_bloginfo( 'name' );
}
 
add_filter( 'wp_mail_from_name', 'change_mail_sender' );