dschmidtke

Yes, problem solved!

For a later update, not for now: please have a look at the UX of the mail action form. When I add a CC address, save the form and open it again, the CC/BCC toggle is set to “off”, the CC address is not visible, and it appears like CC mailing is deactivated. When I switch the toggle to “on”, the CC address is visible again.

Merry Christmas!

Hi Darian, thanks for the suggestion to use this filter (I will try that), but I would rather consider this a hack. So – I don’t want to bug you, but I would like to emphasize again that full page editor is the future of WordPress and I hope for updates in this respect.

My bad, you are absolutely right. I used the default contact form template in all Formello versions for testing purposes and for some reason submissions were activated in 2.2.2 but not in 2.3.x.

So – I can confirm that submissions work. I was also able to create an email alert and it worked partially. The mail is sent to the address in the “TO”-field, but an entry in the “CC” field is ignored (I did not test BCC), so only the “TO” recipient gets the mail (and this mail does not show a CC recipient).

I remember that this never worked for me – even in old Formello versions – and that I therefore hat to create a second email action to inform the CC recipient in a separate email.

Made some tests by clean-installing older Formello versions and adding a contact form from default template. The result is: The latest Formello version to store submissions is 2.2.2, starting with Formello 2.3.0 nothing is stored anymore.

Yes, I updated. Its possible now to enter a message, but the email action form is still buggy. I could reproduce it like that: If you start fill in the form with FROM, TO, REPLY, SUBJECT and message and click again on FROM, field inputs are erased (except for the message textarea).

But it gets even worse: Submissions are no longer stored. I reproduced it this way: Created an new form in my test server, chose the pre-made contact form, did not change anything but publish it immediately, opened the form page in the frontend, filled it in, submitted it (“Thanks for submitting this form.”) – but there is no submission in the backend.

Thanks. I’ll stay with TEC 6.2.6, until I hear for you.

Hi Frank, I unregistered my custom single event template (in fact I deleted it) as you suggested. But that does not help. As I wrote before, since TEC 6.2.7, my custom template is no longer used – so even if it is registered, each event is displayed in a default way that does not fit the design of the website.

Since the site editor is the future of WordPress – like it or not -, I urge you to bring back the possibility for TEC to recognize a custom template, following the template hierarchy and naming scheme of WordPress.

Or you should at least provide a mechanism to overwrite the default template like it was always possible with TEC in classic themes to customize every template and store the customized version in a distinct folder of the theme.

Sorry for the late reply. I thought about setting a default value or not, and came to the conclusion, that it might be the safest not to set any default – neither “yes” nor “on” – but perform the JS validation in a way where a checkbox, that is checked but has no value, is validating – like it does with HTML5 validation. That way, you are following the standard, and at the same time, your don’t have to make up a value or ask the Formello user to set one, because a value is not necessary.

For reference:

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/checkbox#value

https://www.w3.org/TR/2011/WD-html5-20110405/common-input-element-attributes.html#dom-input-value-default-on

Thanks for your explanation!

The big question now is: How can we overwrite this new single Site Editor template?

As I wrote in my first post, until TEC 6.2.6 a template named single-tribe_events.html did the job. What should I name the template in TEC 6.2.7 and later? Or is there another way to add a custom single event template?

Yes, that’s it – the missing value. With JavaScript validation enabled, the form does not validate without a value for the checkbox. As soon as I set “on” as a value it worked.

However, with JavaScipt validation disabled and HTML5 validation only, the form validates even without a value. And that’s how it’s supposed to work since the HTML spec says that if a checkbox name is submitted with empty value the default value should be “on”.

So I suggest that you rework the JS validation in Formello and make empty checkboxes validate with “on” as default value.

Thanks for your support!

No, I cannot share a link, since the website is in production and I have to roll back immediately.

However, I noticed that you provided another update (2.3.2). I performed the update again, had the same problem with a checked checkbox not validating, but the json error after removing the checkbox block is gone.

So I am on 2.3.2 now without a checkbox.

Moreover after removing the checkbox block, the form does not submit anymore in Formello 2.3.1, outputting

SyntaxError: Unexpected token '<', "
Es gab "... is not valid JSON

No, it didn’t solve the problem. Here is the markup of the gdpr block used:

<!-- wp:formello/input {"advanced":false} -->
<div class="formello formello-checkbox"><label class="" for="field_99ef3d"><span>Ich stimme zu</span><span class="required">*</span></label><input name="checkbox" id="field_99ef3d" type="checkbox" required class=""/></div>
<!-- /wp:formello/input -->

And here ist the markup for the enclosing form block:

<!-- wp:formello/form {"successMessage":"Vielen Dank! Ihre Bestellung wurde gesendet.","errorMessage":"Entschuldigung. Ihre Eingaben sind noch nicht komplett.","lock":{"move":false,"remove":false},"className":"as-row","style":{"spacing":{"padding":{"top":"0","right":"0","bottom":"0","left":"0"}}}} -->
<form class="wp-block-formello-form as-row" style="padding-top:0;padding-right:0;padding-bottom:0;padding-left:0" method="post" data-id="151" data-hide="true" data-validate="true" novalidate>

Well, the site is in production now and I won’t rename my form fields again after removing all hyphens, so I don’t test it, but I trust you fixed it.

In this context, I noticed that in the action email a field value of “0” is evaluated as empty (typical PHP pitfall) and therefore not printed, while in the form entries table it is correctly listed as “0”.

Yes. Bulk delete works with latest version.