Skip Navigation

[Resolved] Trouble with email notification

This support ticket is created 5 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 8 replies, has 2 voices.

Last updated by Shane 5 years, 7 months ago.

Assisted by: Shane.

Author
Posts
#1207101
ussrefields2.jpg
ussrefields1.jpg

Hi
We have an user front end cred form.
When the new user is created we set up an email alert to email that person their log in details

This was working

We have had some emails to say that they have nit received their welcome email

When I loom at the alert and email settings everything is as it was - except there is an error on the 'select' email field dropdown and I cant select an email field from here

Nothing has changed plugin wise wbut this seems to have happend over agi.

Any ideas as to the cause or a fix?

Please see screen shots

#1207143

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Caspar,

Thank you for contacting our support forum.

This issue should've been fixed in the latest release of toolset forms 2.3.1

Could you ensure that you are currently using this version. If so could you then provide me with the credentials of the site so that I can check on the issue ?

The private fields have been enabled for your next response.

Thanks,
Shane

#1207245

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Caspar,

I've made a report to our 2nd tier supporters about this issue and they should be investigating it soon.

Thanks,
Shane

#1207248

Thanks Shane
I appreciate it

#1207252

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Casper,

I'll update you with any further info on this.

#1207254

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Casper,

Our team did an investigation on this.

What I advise that you do is to recreate the form. If you take a look at the form here you will see that i'm able to add the email field to the notifications.
hidden link
Please let me know if this helps.
Thanks,
Shane

#1207260

Hi Shane
Sorry I think we were working on it at the same time.
on hidden link
I reverted back to Forms 2.1.2 because this definitely worked and it does - I did this about 30 min ago - 19.00 gmt

So I think you new test form was with this - which is fine as we know that works

We development clone of the site the access details are exactly the same but used dev. instead of www.

On this site Forms 2.3.1 is installed and the same form is having the same issue- you cant select an email field on notifications.

I just created a fresh form out of the box and the problem is still there - so i think there must be something with this version.

I will leave this with you if it helps as clearly other people maybe having issues so the team may want to see this 'bug' in action

But obviously for ,my live site ill stick to the old version until resolved

Thanks for everything

#1207711

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Casper,

Our 2nd tier team has opened a ticket with the development team for them to check on this further.

I will update you as soon as any information is posted on this.

Thanks,
Shane

#1224749

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Caspar,

This issue should be fixed in the current version that we have on our site.

Thanks,
Shane