Forum Replies Created

Viewing 15 replies - 46 through 60 (of 967 total)
  • Hi there @habibjh,

    Thanks for reaching out! When you can, check your XML file in a text editor. Look for any encoding issues in the text that appears in the XML file. This way, we can see if the problem happens before or after it gets imported.

    Also, check the encoding type listed in your XML file. If it’s incorrect, it may cause encoding issues.

    I hope that helps! Have a great day!

    Hi there @guido07111975,

    Thanks for reaching out. When the Force From Email option is enabled, WP Mail SMTP will force the From Email address to be the one configured in WP Mail SMTP. However, if that option is disabled, we’ll use whichever one is added when the email is created. For instance, if you have WPForms installed and have two forms set up, each with a different From address, those emails from Form 1 will use it’s From address, and emails from Form 2 will use that one’s From address.

    However, your mailer service may not like this so much and are very particular about which From address they accept. For instance, when using Zoho, you can only send with the address you are connected to.

    SMTP services like you would use with the Other SMTP mailer often operate the same way. So, if you are connected with info@example.com and you try to send an email From sales@example.com, the mailer service will reject it.

    Are these From email addresses using the same domain? Such as in the example above, info@example.com and sales@example.com both use example.com as their domain. If so, check out SendLayer, SMTP.com, Brevo, and Mailgun. They’ll allow you to send emails From any address on the domain you’ve connected to.

    Also, you can check out this guide in our documentation. It walks through each mailer we support and includes the benefits of each: https://wpmailsmtp.com/docs/a-complete-guide-to-wp-mail-smtp-mailers/

    I hope that helps! Have a great day!

    Hi there @ablamohamedamine,

    Thanks for the responses and feedback. Our development team took a look and tried to replicate the issue. They were able to run the import without any issues. They suggested that your need to run the import twice might have something to do with the hosting environment, such as a caching mechanism that’s interfering. Try using the import again, and then wait for a few minutes or try editing a post. That may flush any caching that’s in place.

    Regarding the My Account page, that also worked for us. We looked at the xml file and it’s importing well when we test. Try re-exporting your file and then double check the xml file that is being shipped. Something may be off.

    Regarding the language issue, we’re checking into that on our side. If you can let us know which other languages you’re trying, we can check to see if it may be specific to the language being used.

    I hope that helps! Have a great day!

    Hi @dav74,

    It’s best to use an email address that matches the domain registered to Mailgun. You created the connection with a subdomain of your domain (mail.mysite.com), so emails from your domain (@mysite.com) will work. Also, it doesn’t have to be a real email address, but it’s generally a good idea to use one with an inbox just in case someone replies.

    I hope that helps! Have a great day!

    Hi there @ablamohamedamine,

    Can you share the import files with us? This way we can take a look at them to help get this sorted out. You can reach out to us using the WP Mail SMTP contact form here to send them over: https://wpmailsmtp.com/contact/

    Regarding the issue where the My Account page is getting the wrong idea, you may need to try switching out the method of detection from post_title to post_name. Here is an example of what I mean:

    // .... 
    $pages = get_pages();

    foreach ( $pages as $page ) {
    switch( $page->post_name ) {
    // ....
    case 'my-account': update_option('woocommerce_myaccount_page_id', $page->ID);
    break;
    // ....
    }
    }

    I hope that helps! Have a great day!

    Hi there @dav74,

    Thanks for reaching out! In WP Mail SMTP, did you set the Mail Domain option with the subdomain you created?

    https://wpmailsmtp.com/docs/how-to-set-up-the-mailgun-mailer-in-wp-mail-smtp/#domain-name

    Since emails are working, the problem seems to just be that WP Mail SMTP is looking in the wrong place for the DKIM. It’s a check we run to see if it’s been added, and our warning doesn’t break anything if it can’t find it. As you’ve seen, it can fail to detect the record, but as long as things are still configured correctly in the DNS, your emails will still work.

    I hope that helps! If you have any questions, just let us know! Have a great weekend!

    Hi there @mstissa,

    Thanks for the response. Just to be clear, when you say you changed it in the settings, you mean you set the From address in WP Mail SMTP to the old domain, correct?

    You’ll also want to check your SMTP host and username to make sure they are correct. If they were updated to the new domain, you’ll need to switch them back to the old domain.

    If that’s all set and it’s still trying to connect to the new domain, likely one of these has happened:

    • There is a custom setting somewhere (custom code or another plugin) overriding our connection details setting
    • The host is overwriting the username or From address to match the new domain

    I hope that helps! Have a great day!

    Hi there @ablamohamedamine,

    Thanks for reaching out. I wonder if your server may be terminating the process early. When you get a moment, try running an import while the WordPress debug feature is turned on. That way we can find out if you might be running into any errors when the plugin runs.

    Check out this guide on our site. It goes over some of the issues you might encounter. It also provides some recommended settings for things like max_input_time and max_execution_time.

    As for the WooCommerce issue, the pages are imported but we don’t automatically assign them in your WooCommerce settings. To do that, you would need to write a custom function to update the settings after the import runs.

    Check out our advanced integration guide here. It provides information on the after_import function and how you can use it to run custom PHP after the importer runs. You could use it to to find your WooCommerce pages and then update the options with the correction IDs.

    Check out this snippet for a better idea of what I mean. We haven’t tested it, but it should help get you pointed in the right direction:

    function my_custom_ocdi_after_import_setup() {
    $pages = get_pages();
    foreach ($pages as $page) {
    switch ($page->post_title) {
    case 'Cart':
    update_option('woocommerce_cart_page_id', $page->ID);
    break;
    case 'Checkout':
    update_option('woocommerce_checkout_page_id', $page->ID);
    break;
    case 'My Account':
    update_option('woocommerce_myaccount_page_id', $page->ID);
    break;
    case 'Terms and Conditions':
    update_option('woocommerce_terms_page_id', $page->ID);
    break;
    }
    }
    }
    add_action( 'ocdi/after_import', 'my_custom_ocdi_after_import_setup' );

    I hope that helps! Have a great day!

    Hi there @sayeedku,

    It looks like you might have a permissions issue on your server. To test, I downloaded the XML file you linked to and imported it into a test site. It took a few minutes but eventually completed.

    You may need to reach out to your host about this so they can check your file permissions.

    I hope that helps! Have a great day!

    Hi there @nickandyhead,

    Thanks for the response. Since you’re connecting WP Mail SMTP directly to your Google account, Google is referring to the app you create in the Google console. So, in this case, you would be considered the app developer (the one in Google, not WP Mail SMTP itself).

    I hope that helps! Have a great day!

    Hey @redanser,

    Just to follow up, we were able to reproduce the error and we’ll be fixing it in our next release. Thanks for bringing that to our attention!

    Have a great day!

    Hi there @redanser,

    Thanks for reaching out. We’ll review this and get back to you. In the meantime, if you have any questions, just let us know!

    Thanks!

    Hi there @maurasa and @rsgoin,

    Thanks for reaching out! When you get a moment, check your Transactional page in your Brevo account to see if the emails have appeared there, or if they are showing any type of notice. Sometimes Brevo will display a notice on the bottom of the Transactional page that relates to an account issue.

    Troubleshooting Plugin Conflicts

    If you don’t see anything like that, there may be a plugin conflict causing an issue.

    Deactivate Other Plugins:

    If the issue is a plugin conflict, you’ll need to follow these steps to find out which one is causing the problem.

    • Methodical Approach: Deactivate all plugins except WP Mail SMTP.
    • Testing: Retry the Email Test after each deactivation. If it works, you’ve found the conflicting plugin!
    • Reactivation: Reactivate plugins one by one, testing the Email Test each time. This pinpoints the troublemaker.

    Check for Theme Conflicts (Less Common):

    While less frequent, themes can sometimes cause issues.

    • Switch to Default: Temporarily activate a default WordPress theme (like Twenty Twenty-Three).
    • Test Again: If the Email Test works, your theme might be the culprit.

    I hope that helps! Have a great day!

    Hi there @suonoweb,

    Thanks for reaching out. That error message is coming from the mail server you’re sending the email to. So in the example, yyy.it is reporting back that there is no such user there. If the account does exist, there is likely a configuration issue on that mail server. Whoever manages that server would need to look into the issue to find out why it’s rejecting emails that are being sent to a valid email address. If I had to guess, it may be a firewall or some other type of security software that’s blocking emails and reporting back that the address doesn’t exist.

    I hope that helps! Have a great day!

    Hi there @nickandyhead,

    Thanks for reaching out! We’ll be happy to help you get this sorted out.

    Usually, when we see the Gmail mailer repeatedly disconnecting from WP Mail SMTP, it means that your Google API app (OAuth screen section: https://a.supportally.com/HMVXQm) is in the “Test mode” and needs to be changed to “Production” to resolve this issue.

    Can you please look into adjusting this setting in Google’s API & Services > OAuth consent screen Publishing status area and see if it resolves this issue for you?

    Other Causes for Gmail Disconnections

    The OAuth token in Gmail will reset for any event breaking the connection, including but not limited to:

    1. Changing Google password
    2. Enabling or disabling 2FA
    3. Google account access reset
    4. Activation of Google advanced protection program
    5. Revocation of the app to profile
    6. App OAuth permission revoked by Google
    7. App moved from public mode to private/internal mode by Google (or by a user whose user domain is not in the allowed org domain zone)
    8. App verification failure on reaudit
    9. Suspension of Google account
    10. User requested linked account unlinking
    11. The user does not use the app for 6 months (automatically expires refresh token)
    12. The user adds/removes sensitive or needs review scopes to the app but does not complete the app review process
    13. If the user is at the maximum limit for OAuth tokens to a Google profile (50) or for the service (25 for example in analytics), activation of a new refresh key will also automatically revoke the earliest key

    To resolve the issue, please head over to the WP Mail SMTP > Settings page, and click on the “Remove Connection” button. Then click on the “Allow plugin to send emails using your Google account” button to re-enable access.

    Verified App

    You also mentioned seeing a warning that said “This app is not trusted, Proceed? (Unsafe.)” The wording is a little different from what we’ve seen, but it sounds like the verification screen. This notice that you see is due to Google’s strict security settings. In this case, you can go ahead to click on Advanced Options > Go to [your site name] to proceed with the configuration (please see the screenshot here: https://a.supportally.com/8yXSUv).

    In case it helps, you can check more information about this error in our guide here: https://wpmailsmtp.com/docs/how-to-set-up-the-gmail-mailer-in-wp-mail-smtp/#verified.

    I hope that helps! Have a great day!

Viewing 15 replies - 46 through 60 (of 967 total)