Skip Navigation

[Resolved] Improve required field warning in backend

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.

This topic contains 2 replies, has 2 voices.

Last updated by ScottM9386 5 years, 9 months ago.

Author
Posts
#952386
Capture.JPG

Hi,

I have required fields. The problem is, in the backend, it's easy to navigate away from the page with out filling them in.
The warning is not a browser pop-up box like it is in, say, "views" if you try to navigate away before saving.
See image.
Any way of fixing this?

Thanks.

#952778

No, because those are different things.

1. The navigate away warning is only happening when you made edits somewhere in an editor and did not save
2. The warning about putting something in the required area is happening only when you want to save that what you work on, but did not complete it.

So, the one excludes the other.

1. If its' possible to navigate away without a warning it means, no one edited something and hence, nothing needs to be checked (nothing is published.)
2. If it's not possible to navigate away it's because of an edit
3. As soon you save we check the requirements and block where needed.

That is how it's expected to work, the goal you try to achieve would require customization that we cannot provide.
Maybe, contractors can help:
https://toolset.com/contractors/

#952861

Thank you Beda.

Regards.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.