David Vongries

In Swift SMTP, do you have the content type set to Plain Text or HTML?

Both, the Header & Footer are not coming from Swift SMTP, so I’m guessing there’s another plugin at play here.

By default, Swift SMTP has the email type set to plain text, to match WordPress’ default emails. If switching to HTML, all the emails will have to be formatted properly under the “Welcome Email Editor” tab to use HTML.

Just to double-check. You are in the Swift SMTP tab when trying to send the test email, not the Welcome Email Editor tab, is that correct?

Can you elaborate on where the error message appears? Does your email sending service actually allow sending without authentification?

The error message here points to a line where we simply load a file from the plugin. That doesn’t make much sense at first glance. Still trying to figure out what the issue is here. What version of GF do you have installed? Does reinstalling Swift SMTP and Gravity Forms make any difference?

We have just pushed an update to the plugin, adding 2 settings to force the “From Name” and “From Email” set by Swift SMTP. These settings are unchecked by default, meaning updating to version 6.1.1 should automagically fix the issue for you guys ??

We have just pushed an update to the plugin that should address & fix the issue. Please try sending another test email running version 6.1.1 of the plugin.

We are going to look into this and provide a solution asap. Thank you for bringing this to our attention!

Fixed.

Hey Kaleb,

to enable Elementor for Admin Pages, please have a look at this article from our docs. At the very bottom we describe how to enable Elementor for our Admin Pages post type – https://ultimatedashboard.io/docs/admin-pages/

Regarding the other issue, I’d like to ask you to create a support ticket with us as this is a pro feature – https://ultimatedashboard.io/support/

Thank you!

Best,
David

We’re going to look into this ??

@psypat, the server went down around an hour ago. everything should now be back to normal ??

Are there any other details you can share? Based off of the information given, we cannot locate the issue.

We’ve fixed the vulnerability yesterday and are going to push the update later today ??

This is now fixed with version 3.7.11 ??

Hey guys! We are looking into this and are going to push an update asap. Thank you for bringing this to our attention. I’ll keep you posted.