nztim

Yes it works fine, had to do it again after a recent update though.

As per the other topic, this appears to produce a validated required select box:

[select* fieldname "" "option1" "option2" "option3" "option4"]

Note there is no ‘include_blank’ and the first option is blank.

Yes I have the same problem too, and I’m pretty confident that it was working correctly until recently.

It appears that the demo on https://contactform7.com/checkboxes-radio-buttons-and-menus/ demonstrates the issue – you can submit the form without selecting anything from the required select box.

For anyone reading this, my immediate solution is to add hidden fields for the post name and title, and automatically fill these with Javascript on page load. This means the post slug and title will always be passed through.

I think I’ve figured this out:

The website pages containing this form are updated by an automated process that deletes and re-adds them.

If a page is loaded and left open in the browser while an update occurs, and the form submitted after the originating page has been deleted and re-created, the [_post_name] and [_post_title] tags will fail.

Presumably this is because even though the post appears the same, the original post ID will no longer be valid. It also explains why the URL parameter works when the post variables do not.

So thank you for your suggestions, they were very helpful ??

Thanks again for responding. This form is only used on one specific page template. The shortcode is embedded in the page template file, and it’s inside the Loop. So there are no variations in the placement of this form.

As mentioned above, in most cases it works but occasionally it fails. So far today there are 23 submissions and two have exhibited this problem. When I try the form on the pages concerned it works OK for me.

Do you think it has to do with the user environment? Any further suggestions for troubleshooting would be appreciated.

Thanks for your reply. I put the [_url] tag in and found that in fact it does function on the occasions when the [_post_name] and [_post_title] tags fail.

Of course I tried the form on that page and the tags worked normally in my test.

Nevertheless this is potentially a solution, as the URL can identify the post instead of the [_post_name], but the slug is the information required by the receiving system and the post title is also very useful, so it would be much better to continue to use [_post_name] and [_post_title] if they worked consistently.

Do you think there any way to figure out the reason or circumstances causing these two tags to fail?

I just had a look at the latest HTML5 spec for this and it looks different than the older version:

https://www.w3.org/html/wg/drafts/html/master/forms.html#radio-button-state-(type=radio)

Constraint validation: If an element in the radio button group is required, and all of the input elements in the radio button group have a checkedness that is false, then the element is suffering from being missing.

With respect Takayuki, checkboxes don’t look exclusive, so making them exclusive for some questions is confusing and unnecessary – that’s what radio buttons are for.

Take the example of a gender question – radio buttons are the obvious choice, having checkboxes would be downright weird because of their non-exclusive appearance. If it’s an important and required question, making one radio button option pre-selected is a recipe for unreliable results.

Thanks for an awesome plugin!

Thanks eliteclientele, I’ll keep that in mind.