Forum Replies Created
-
AuthorPosts
-
John Chvatal
ParticipantPeter, I got the date time field to save. However, the front-end form remains broken when I update to the latest Meta Box version.
Currently running Meta Box 5.10.3 & Metabox AIO 1.30.2. Broke after updating to Metabox 5.10.3 & Meta Box AIO 1.31.0.
John Chvatal
ParticipantHello Peter,
I think I found the root(s) of the problem.#1. The save format on the Date/Time field was Y-M-D. Once I removed this, the saving posts returned to normal.
#2. During the troubleshooting I updated Metabox to the latest version. It appears this update broke the front-end update form I added to the single post template via the shortcode. All field data that was previously added were set back to the default/blank fields. When viewing on the back-end, the data was still in those fields.
I double-checked this by restoring the site to a date prior to Sunday. Removed the save format. Verified that the date/time field was saving correctly. Then proceeded to update the Metabox plugins. It was at this point that the front-end forms broke.
So I suspect there were two concurrent problems that made things hard to diagnose... My input of the save format which at the time seemed to function normally but now it didn't. Then possibly a bug in the Metabox plugin.
John Chvatal
ParticipantHello Peter,
Since my last post, I made a copy of the site and installed it on Local. The same issue occurred again. I just boosted input vars to 40000. I tried this on a site with a default WordPress theme and only Metabox plugins active. Other fields I tried worked normally.It is as if the date/time field saves to something random (not what I input). One thing I noticed is the minutes seem to save to the current time. For example: it is currently 3:35pm here. It saved as 21:35. If I waited a few minutes, it'd save as 21:37.
I went ahead and created another field group with date/time field and attached it to the Post post type. I found the field saved correctly both on the initial save and subsequent updates. I am thoroughly confused to what is going on here.
John Chvatal
ParticipantHello Peter, here is the JSON that I shared via a pastebin link: https://pastebin.com/H98vzPP5
September 24, 2024 at 8:13 AM in reply to: Bug in Bricks Builder Front End Submission Form Element #46523John Chvatal
ParticipantHello Peter, I added the shortcode. I the page is no longer disfigured. However, when trying to modify/add text to a field before saving does not result in it saving to the field group in the post when viewing it in the post editor.
This is the shortcode that I added to the CPT single post template: [mb_frontend_form id="accidents-cpt-editable"]
My intention is to set a Bricks condition to hide the MB front end form from logged out users. Do I need to do anything else to actually save the updates to the post?
August 17, 2024 at 4:07 AM in reply to: ✅WP All Import Lat Long Coordinates Do Not Show On Map #46168John Chvatal
ParticipantPeter, thank you for sticking with me on this. Your last explanation helped me to connect the dots on what I was missing. I was able to run another import with WP All Import. What was tripping me up is the WP All Import Metabox addon doesn't support the Open Street Map field (airport_map field). I got around this by adding a custom field targeting the airport_map field and adding the data field columns from the CSV import formatted like: lat,long,zoom in decimal format. I purposely associated a text field with the Open Street Map field that does not exist because I do not want this field to be updated on accident.
A piece of feedback to the Metabox team... it'd be nice if the associated text field handled lat and long. Its more confusing than I think it needs to be. Advanced Custom Fields's Google Maps address field handles the lat,long no problem.
August 16, 2024 at 3:04 AM in reply to: ✅WP All Import Lat Long Coordinates Do Not Show On Map #46157John Chvatal
ParticipantPeter, there is no text field associated with airport_map. It is just the map.
There is the option to associate a text field with airport_map. I did this and associated airport_address with airport_map. I added the formatted lat, long, zoom to the airport_address field.
Would it be possible for you to modify the field group that I uploaded? Possibly using the airport_address field for the formatted lat long zoom?
August 15, 2024 at 7:31 AM in reply to: ✅WP All Import Lat Long Coordinates Do Not Show On Map #46153John Chvatal
ParticipantPeter, I tried adding lat long zoom in the format you suggested: latitude,longitude,zoom in the airport_address field and made sure to pass its ID to the map's "Address field". Unfortunately this is not updating the OSM map field location pin. I am not sure what I am doing wrong?
April 4, 2023 at 1:17 AM in reply to: Placing A Metabox Field Above A Metabox Tab Breaks The Edit Interface In A CPT #41320John Chvatal
ParticipantPeter, this creates another issue... I cannot easily use conditional logic to show / hide tab fields based on the three fields in a separate field group. Do you have a workaround for this?
John Chvatal
ParticipantAnh, how do I get this working? Where do I add this code?
I have a member survey that has the first 6 fields set to hide questions. I need to delete the hidden field data when a logged in user saves the form.
John Chvatal
ParticipantThank you Long! This worked like a charm!
-
AuthorPosts