Saving empty values with hide_from_front
Support › MB Frontend Submission › Saving empty values with hide_from_frontResolved
- This topic has 7 replies, 2 voices, and was last updated 2 months ago by
Yumikom.
-
AuthorPosts
-
September 30, 2025 at 12:17 PM #49067
Yumikom
ParticipantHi,
The form is displayed using a shortcode with hide_from_front specified.
When saved, the readonly field with hide_from_front specified is saved as an empty value, causing the data to disappear.Can I prevent values I don't want displayed on the front end from changing during saving?
Thanks and regards,
YumikoSeptember 30, 2025 at 10:56 PM #49068Peter
ModeratorHello Yumiko,
I'm not able to reproduce the issue on my demo site. If a field has the setting
hide_from_front, it will be excluded from the frontend form. That means the input field is not available in the HTML structure so it isn't possible to save an empty value for that field.October 3, 2025 at 4:08 PM #49078Yumikom
ParticipantHi Peter,
Thanks for your constant support!
Since the values keep disappearing in my environment, please allow me to review the code on your demo site.October 3, 2025 at 9:00 PM #49081Peter
ModeratorHello,
I don't use any custom code on the test site, just the basic setup. You can access the test site with the credentials below. Note: it will expire in 2 days.
https://vengefulstem.s6-tastewp.com/wp-admin
Username: admin
Password: 1a3pwf0KuP0October 6, 2025 at 10:09 AM #49087Yumikom
ParticipantHi Peter,
I didn't receive any notification, so I missed the weekend and the validity period expired. A slightly longer validity period would be helpful.
Currently, in another case, the value of the readonly attribute in Metabox is being saved as an empty value during editing.
This is a bug report concerning the post editing screen, and we plan to investigate it immediately. WP5.8 + Metabox is version 5.4.6.
October 6, 2025 at 1:41 PM #49088Yumikom
ParticipantHi,
Previously, I mentioned read-only fields where values disappear upon saving in the frontend. After prolonged use, the checkbox in the save field remains permanently unchecked.
Regarding this save field, as previously reported, unless the default behavior is changed, critical customer data is being destroyed daily, causing significant issues.
→ Due to frequent problems, the plugin's auto-update feature has been disabled.The issue in this thread pertains to the hide_from_front, so we kindly ask for your continued cooperation.
October 6, 2025 at 10:41 PM #49095Peter
ModeratorHello,
Here is the new test site info:
URL: https://processhot.s2-tastewp.com
Username: admin
Password: lMCvLSdfyV0You can setup a WordPress site with TasteWP within a few clicks. Let me know if you can reproduce the issue on the test site.
October 7, 2025 at 8:39 AM #49096Yumikom
ParticipantHi Peter,
Thank you for building the test site so many times!
Thanks to your support, I figured out the cause.
When I used AI generation to write a report form with a large number of fields, the readonly syntax was incorrect.After checking the syntax on your test site and adjusting it, the readonly + hide_from_front fields were successfully saved without being deleted, retaining their stored values.
Thanks and regards,
Yumiko -
AuthorPosts
- You must be logged in to reply to this topic.