That is what I did. I’ll check back with Elements eventually.
Did you verify everything at brevo.com and put in the right smtp and details? Mine worked at the first try.
I can find my settings and share, if it can help.
But your e-mails will be to and from the to-address, so the to-address must be the sending address verified in brevo.com. Just to be clear on that.
This is the same for many SMTPs, and the reason we just need to be able to set the sender address (from email).
I would love for you to share your settings but I am pretty sure I had it all set right. I am extremely frustrated at this point and trying to just solve this issue.
Of course - just wanted to try to help.
I’m going to find them and post back very soon - 10-20 min, and I’m back at the computer.
Here’s how it looks in my panel - I’ve only red’ed out username and password to the service (and the to-email), of course, but these are the settings. The e-mail in “To Address” is validated for sending in Brevo.com. First time I tried, I found the e-mail there, but it hadn’t gone all the way through, so I had to validate my sender address. After that, it works very well.
Thomas I appreciate that and my settings are correct but the form will not even submit because I get no error or success when hittin the submit button. This FORM in Elements is really jacked up still. I have no doubt they will get it worked out but right now it is unusable the way it is. I can’t even check to see where the data is getting POST and what PHP is handling the sending. Frustration is too the maximum, especially since in Rapidweaver never had these kind of problems with forms.
I tried some changes to my own setup, and I notice that for Microsoft Exchange e-mail (when domain is pointing to them), Brevo give a warning about possible situations where recipients may not receive e-mails before domain is validated also.
It’s not hard to do, basically setting up records at the domain.
At Brevo-site, you go to your user symbol, and choose Senders, Domains etc.:
This was showing for one of my new e-mail addresses to send to:
This warning was under “Domain” tab:
Okey.
I’m very sure they’ll of course nail this for us, so no worries for that. 
But, in the meantime, I think of a few solutions - or let’s be honest - workarounds:
- Make the form in RapidWeaver
- Publish it to a special location on a web server (maybe best outside the main website)
- Put it in an iFrame via the HTTP component (described in my next post) on the Elements version
- Publish Elements version
OR - but I’m so new to Elements and don’t have RWC, so don’t know:
- Make the form in RapidWeaver
- Export it to local drive
- Import the HTML (and required files, may be the problem of this method) into the Pages in Elements
- Publish it all from Elements
So Thomas,
Going through Brevo is not working at all. I can not get the post to even leave the website to go to brevo so much for using them. Yes I will figure out how to integrate my rapidweaver page into elements or at least how to link my RW contact page to the Elements site. It will take some sitting down in a quite space and just work through it but I know I can figure that out. I do not know HTML code well so it will take a little manipulation but I can get it. Worse case I will recreate the whole site in Rapidweaver for now until Elements comes of age Thank you for trying to help me though.
The iFrame is done by pasting this code to the HTML-component (under custom components):
I try to show it quick in a screenshot - explains below
I just put the HTML component inside a container (to be able to place and adjust it, your form may not cover the entire view like I do here). This is circled in red.
Then, when HTML component is chosen in the node list (the one below the container circled in red in my screenshot), hit the button up to the right to show the inspector/code part below, then paste the code and replace my URL with yours to the form (easiest when it’s a full https://www… one), and change the width and height to your liking.
When previewing in browser, it will show.
Oh, and feel free to ask if HTML code help should be needed.
Just wanted to add for anyone having issues — please ensure you are running at least PHP 8.1 on your server. Ideally you should be running PHP 8.4, but as a minimum you need 8.1.
You can easily check this by appending ?apicheck to any page with a Form, for example:
my-website.com/contact/?apicheck
1 Like
Just to follow on from @ben’s post, I’ve updated the Form page in the manual to include this information along with a compatibility checklist.
We’ll add to this document over time to ensure it covers any other common gotchas when trying to publish a form.
1 Like