Some settings not saved

Thanks for your message

I can’t recreate this. If there is a petition and I enable (2) don’t collect email addresses, as it says, this is not reversible. https://speakout.123host.net.au/faqconc/why-cant-no-email-address-be-reversed/ It will also affect (1) do not send email, since addresses aren’t being collected. When I enable (2) it works as expected for me. Or am I misunderstanding you?

Thanks for (3) about custom 5 required. Yes there is a bug, I will fix that and release an upgrade.

Update on this. Checking Custom Field 5 Required was actually working, it just wasn’t checking the box on the page due to a typo.

If the box was checked when you saved, the field was required. If you hadn’t noticed that the box wasn’t checked (due to this bug) and you saved again, then the field was no longer required (as the box wasn’t checked).

I have releases a fix for this in 2.14.10

Thanks for your reply.
There seemed to be a connection between the problems.

When I check 1) √ and 2) √ and then go to 3) and save that, the 1) and 2) are back to unchecked. Looks like as soon as you save something on tab 3, both these 1) and 2) are reset to standard. Or something …
So that should not be a huge problem, as long as I end with 1 and 2.

I will now try the new version for 3).
Thank you.

Ok, so I updated the plugin.
The box checking was now working in admin.

But … it does not work on the front side, because when we fill in the form, without selecting that dropdown, the form goes through indeed. While it should block and throw an error for that dropdown not chosen. ??
(cache emptied)

Hope you can recreate that.
Thanks in advance.

Ahhh…you are right.

It took ages to track this down, but what was happening was that because the fields were disabled, it wasn’t passing their values – which is expected behaviour, but I hadn’t allowed for it. So whenever any save was done, those fields were seen as unchecked.

Fixed in 2.14.11

Thanks for working with me on this.

Hi, Thanks also for working on this, but sorry to say, I still got the same “Required”-dropdown-problem not working in the form.

To be sure, I created a new petition with a required dropdown.
When we do not choose that dropdown item on front, the form still gets passed, without that data input. It should throw an error.
What we see then as the result on display is: >nameofthedropdown
So the Required option is not doing its job.

(Also afterwards when going back into Edit Email Petition, one is forced to fill in Target Email and Email Subject, although this is useless, since we “√ Do not send email”. But that is not a real problem and might be kept for later. ??

Thanks again Pieter, that > was the problem passing what should have been no value. I have also improved how the fields handle being required.

Look out for a new version maybe today or tomorrow when I have time.

Any progress on this?
We’ve put a project on hold because of this bug.
Thanks.

Pieter, which version do you have installed? Is the bug still present?

I thought I had fixed it but have been distracted with another project

Hi, we’re on 4.14.11 which is the latest version, right?

So you did not fix that latest > problem yet in that version. Or at least not uploaded a new version as far as I can see.
And indeed the bug is still there.
Required dropdown just goes through anyway, without selecting any dropdown item.

Thanks for following up.

Oops…I fixed in on my test site and it worked…but then I left some code out of the new version.

It was working if custom field 5 was at the top, but not if in middle or bottom.

Look out for 2.14.12

Thanks again

Now, with 2.14.12 I get this:

The required dropdown has a red border, which is good and means it is required.
But … when I fill in the form and do NOT choose an item from the dropdown, the form still goes through. The difference is that now in the result there is no >nameofthedropdown so that part is ok, but still, ‘required’ does not work. It should throw an error and not send the form in the first place.

Stubborn bug it seems. :-/

Thanks Pieter,

I can’t recreate this – try not choosing anything in custom field 5 at https://speakout.123host.net.au/speakout-demo/ and it won’t submit

If it still isn’t working for you, please contact me via the contact form at that site so I can have a look at yours without you having to post the URL here.

Hi,

Thanks for checking.

That is strange indeed. Works very well now on your site and not on mine.
First I will do some more testing here then.
I’ll come back later to report and consider further steps.
??