I have been using WFB 2.5 for many years.
I have updated to WFB 2.20 and the server is now running PHP 8.2

The problem is that the notification email isn't being received. I've tried changing some things but I can't resolve. Tech support at my hosting can't find the problem either. Could I get some suggestions please on what to check / change?

There is no error message produced on screen when the form is submitted with the current settings.

The confirmation email to the customer (currently testing using a yahoo account) is working fine.

The confirmation message to load on the form to show on the web page after submission is working fine.

But the notification email which goes to the site owner e.g. me@mydomaim.com isn't coming through. The form is located on the landing page of mydomain.com so the email address is at the same domain. It has an SSL at the site.

Tech support have updated my SPF settings and DMARC. I have edited the user.cfg file on the server to reflect the host as localhost and the port number 25.

Tech support feel it is something wrong with the form rather than server or email settings at their side.

Can someone please advise thank you

It's a bit difficult without seeing the form and the page it is on,
When you exported the form what sort of container on the page the form is displayed in did you place the code it asked you to place.

https://www.coffeecup.com/help/articles … he-scenes/ under the heading 'Notifications tab' says "As with the Confirm Email settings, you also have two different options when editing your notification email. You may, edit the code in Web Form Builder itself or you can edit it in Responsive Email Designer!".

I understand that both editors modify the same underlying template, but that they do not synchronise or merge changes. That can mean that editing and saving in RED will overwrite previous WFB edits. If both programs are used, it may be worth checking that the notification email set in one program hasn't been deleted when editing in the other program.

Frank

Hi MG,

I understand that you are testing your form as a customer using a Yahoo Mail account. How about the email account you are using for yourself to receive notifications?
I have seen problems with receiving notifications when using email addresses from Yahoo, Gmail, Outlook and others, but it usually works ok if the email to oneself is an address pertaining to the domain where the form is sitting.

It's the address pertaining to the email at the domain where the form is hosted which isn't working - the emails to Yahoo are sending

The email notification content was created in free html editor and pasted in.

If it was some issue with that, then would it stop the notification email from sending? Or would it still send but send something like a black page?

Because there's nothing at all being received

Yep that would be the culprit

Ok What would be the solution for this please?
Apart from pasting code in which is created in another program, I've done it this way for 10 years but not encountered this I don't think. But I've switched to this btw version.Both the files have different names already for notification and confirmation is there a better way to insert the code?
Thank you

The latest post seems to clarify the intended meaning of the sentence quoted above.

I'm sure Wayan's post was not suggesting that the problem was with the free HTML Editor, but rather perhaps with what was created using it, or perhaps with something of what was created having failed to upload properly.

It may be that a link to the page containing the form would help someone to identify the problem.

Frank

I agree that discussing a form that fails without having the chance to examine it, or at least see it on a page, is prone to just guessing or talking at cross purposes. You could, for example, make a copy of the form, strip all your personal information (user name, server name, any passwords or geographical identification), and then post the form itself as a project file (.fb file), zipped up for us to test on our own servers. That way we would have a fair chance of producing some solution that would actually help.
If your form is so secret that you can't even trust us with that, and only if the form is a simple one, then take a look at my component collection. See URL in my signature, then select the framework you're using and take a look at the 'Basic Form'. On my server, it works well if you use email addresses from the domain where the form is hosted. The end-users can use whichever email address they have. There is another form too, a bit more complex, but I think I'll have to update it a bit before I can recommend it to anyone.