Forum Replies Created
-
AuthorPosts
-
June 9, 2025 at 11:20 PM in reply to: Meta Box lost ability to update Custom Table Group fields via API after 1.30.5 #48415
Cameron
ParticipantHi Peter, any chance this has been implemented yet? I've been holding off upgrading and have tried to follow the changelog, but I am unsure.
April 1, 2025 at 9:34 PM in reply to: Meta Box lost ability to update Custom Table Group fields via API after 1.30.5 #47977Cameron
ParticipantHi Peter, any chance this has been addressed in one of the more recent updates? I am sticking with 1.30.5 in the meantime to not run into issues I have to correct and rollback.
March 6, 2025 at 12:26 AM in reply to: Meta Box lost ability to update Custom Table Group fields via API after 1.30.5 #47787Cameron
ParticipantPeter, see if this will work. I modified it to remove everything but the HighlightGroup field.
https://drive.google.com/file/d/11HVVQrtw646-myPbRVFWirwMKRUgyaQs/view?usp=drive_link
Cameron
ParticipantCan we mark this as not resolved?
Cameron
ParticipantHello, this is still an issue in AIO 1.31.1.
I send this payload:
{ "meta_box": { "HighlightsGroup": [ { "highlight": "This is a Test" } ] } }...the response received will be correct and seems to be updated, but when you view the actual post or database, nothing has changed.
Roll back to 1.30.5 and it works!
Tan, I double checked that
cloneis set to true when I tested with both versions. It will work correctly in 1.30.5, just not 1.31.0 or 1.31.1.Cameron
ParticipantPeter, any chance this was fixed in 1.31.1?
Cameron
ParticipantHi Peter,
I have a Group called
Highlights Groupwith fields calledHighlightswithin. This Custom Field is stored in a Custom Table.I've previously been updating it successfully like this:
{ "meta_box": { "HighlightsGroup": [ { "highlight": "This is a test" } ] } }The output payload shows as successful, but using a GET command right after the field will not be updated.
This stopped working in 1.31.0 but works in 1.30.5 .
Cameron
ParticipantSwitching to One column (not two) is the only solution for now besides using another browser.
Cameron
ParticipantGreat Peter, thank you. That's what I needed.
Cameron
ParticipantInteresting. I'd checked Chrome before and that is fine, but Safari is suddenly consistently as seen in the screenshot and happened after upgrading to Safari 18 with Mac OS Sequoia.
Cameron
ParticipantSame here. This is on 5.9.7 (today's update) and AIO 1.26.1:
https://drive.google.com/file/d/16CBVvoCFlgUkEEFgMYRSPnhTEcGkMAOy/view?usp=drive_link
April 18, 2024 at 1:07 AM in reply to: ✅Issue with Meta Box v5.9.6 (layout issue for conditional fields) #45243Cameron
ParticipantI'm having similar issues on the "Edit Field Group" interface where the Duplicate and Trash buttons no longer work, and if I attempt to edit the Title directly (click to edit), it will not function properly.
April 11, 2023 at 12:25 AM in reply to: Updates from REST aren't applied when using Custom Table #41416Cameron
ParticipantPeter, do you see a fix for this coming in the next version update? I wanted to ask before I start looking into options to update the custom table database directly.
Updating Custom Tables via REST is a huge part of our use case.
April 8, 2023 at 12:26 AM in reply to: ✅Issues with Custom Field Groups not saving to Custom Table #41390Cameron
ParticipantThank you Peter, that was it. We can mark this as Resolved. The only issue I have now is updating Custom Table via REST is not working, but there are other threads for that.
April 6, 2023 at 11:36 PM in reply to: Updates from REST aren't applied when using Custom Table #41372Cameron
ParticipantSeeing the same issue here.
My existing Custom Fields in Custom Tables will only update via the Admin section, but not REST.
Also possibly related: for any new Custom Fields Groups created with Custom Tables, Metabox will not create the table in the database and will simply save the data the standard way to wp_postmeta.
-
AuthorPosts