[Resolved] Unsaved changes are being lost without a prompt

[Author]

Posts

[dashD]

Tell us what you are trying to do?
I have created a custom post type. If I edit the content within the custom fields and then accidentally move away to a different page then there is no prompt to say that I have unsaved changes and my changes are lost. Unsaved changes in the default WordPress post body filed however result in the "unsaved changes" prompt. I was hoping that similar behaviour will exist for custom fields. Is there a way to get the browser to provide the "unsaved changes" prompt when a user moves away from the page with unsaved changes?

Is there any documentation that you are following?
No

Is there a similar example that we can see?
The issue appears to be similar to the one discussed at https://toolset.com/forums/topic/prompt-before-losing-unsaved-settings-by-navigating-away-from-page/. If this is the case then it will be good to know when the feature will be ready.

What is the link to your site?
Local development machine

[Beda]

The feature can be upvoted here:
https://toolset.com/feature-request/confirm-to-navigate-away-from-page-if-fields-are-populated-but-not-saved/
https://toolset.com/feature-request/?wpv_post_search=Confirm+to+navigate+away+from+page%2C+if+Fields+are+populated+but+not+saved&wpv_sort_orderby=post_date&wpv_sort_orderby_as=string&wpv_view_count=686737&wpv_sort_order=asc

There are no plans on this yet.

[dashD]

Thanks Beda. I have upvoted. However given the low number of votes, I can't see the Toolset team getting to this anytime soon. Is there anything I can do now, even if it means adding some code manually, to overcome this issue?

[Beda]

As stated on that list, that is not the only parameter measured, even denied features can be done depending on our Developers decisions, finally.

The developers are the only along with management that can accept or finally deny a request.

To do this now, you would need custom code that we cannot provide here in the forum.
You could consult with the contractors if someone is available to do this:
https://toolset.com/contractors/

[Beda]

Changing the state of ticket

[dashD]

Issue is not truly resolved but good to know it is on the radar of the Toolset team to fix. Thank you!