Skip Navigation

[Resolved] Field required even when working on a template where it is set not to display

This support ticket is created 5 years, 9 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
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 6 replies, has 2 voices.

Last updated by kasiaG 5 years, 9 months ago.

Assisted by: Beda.

Author
Posts
#1201167

I have a custom field group set to display only when a specific template is selected for the page. One of the fields in this group is a required field. I was expecting that when working on a page where the specific template where this field group applies is NOT selected, the user will be able to save the page even if the required field is not filled out (given that the field group does not display). However, pages where the template using the field group is not selected will not save under these circumstances. It just hangs and hangs, expecting that the required field be filled, but since the field groups aren't displayed, it isn't apparently obvious why it's not working. While I can get around this by making the field not required, this isn't ideal, as pages where the template for the field group IS selected needs that field to be filled in. Please advise.

#1201244

This is not happening on my local test.

Whenever I create a post and have no such template chosen, the field is not displayed and I can save the post.
Only when I change, from using the template, to not using, then, of course, the field stays there and asks to be filled out, because it does not listen to the template on the fly but only when the page loads.

I agree that this is not nice, it makes it impossible to remove the Template without actually saving the field. It is however not what you describe, and to be sure I do not miss anything I suggest I have a look at the site - can you provide me access, and allow me to create a dummy post to test?

#1201297

I have confirmed that I am only experiencing issues since version 3.2.5. Rolling back to version 3.2.4 resolves all of my problems. I am not able to give you access right now as this website is in a staging environment but will be going live any day. Once I have transferred this site to the live server using Types version 3.2.4, I will do a screen record demonstrating my issues and then provide you with access to the backend of the staging site with version 3.2.5 installed. Just a side note, I do have the Classic Editor plugin installed. I am wondering if this might be contributing to the issue.

#1202942

This does not happen even if I disable the Gutenberg.
I suspect it requires more steps, or other plugins, to make this happen.

It is important to fix this if replicable.
Can you send me a duplicate? This is the only step that can help us get closer to the issue, and fix it.

Online we cannot debug issues, usually, if it requires to see what happens with the code while performing the actions because that requires debugging processes and tools, which work only locally and mostly are dangerous to apply online (may result in broken sites)

Note that we released an update of Types meanwhile fixing other release-related bugs, I suggest updating (Views will follow with some updates later this week or the coming Monday)
However, the issue you mention was not yet reported by other users.

#1203428

Thanks for the update. I can confirm that the issue is still present in version 3.2.6, so I have once again rolled back to 3.2.4. I am transferring this site to its live server today on version 3.2.4, once I've done that, I can give you access to the staging environment I have set up to troubleshoot the issue. From there, you can feel free to take a duplicate.

#1203655

OK.

#1206620

Just wanted to let you know that updating to version 3.2.7 has resolved this for me. Thank you guys for fixing this!