Having some issues on the new AIO update.
Support › Meta Box AIO › Having some issues on the new AIO update.
- This topic has 11 replies, 2 voices, and was last updated 6 days, 19 hours ago by
Peter.
-
AuthorPosts
-
October 8, 2025 at 5:01 AM #49099
Robert
ParticipantSeems like the new AIO update has some weird bugs. When editing custom fields, I get same random fields prompting me to fill in values now. The URL field shows [“”],[“”] that I have to erase each time I want to make a field change in the custom fields.
Video: https://share.zight.com/WnunvNrnMy current post type was working great until shortly after the update, where now I see a blank white screen. When duplicating that same post, I get to access the post editor.
Video: https://share.zight.com/04uZjKPeMy error log has also exponentially grown as well since the new update which I've shared in the video. I also shared this on Facebook in case others have this issue as well minus the videos.
I'd like to send website access, but how? Perhaps it is not necessary, but for future reference, do I use the contact form link in the footer for sensitive login info, etc. outside of support forums?
Also, and unrelated to this specific issue (maybe), but how can I have a custom taxonomy connect to a CPT via a tax / advanced tax field? I've tried iterations of making the group that tax field is in cloneable, making the tax field cloneable, or making both cloneable but nothing.
Here is a video further showing: https://share.zight.com/rRuRY6jXOctober 8, 2025 at 5:01 AM #49100ParticipantBy the way, I love Metabox!!! Happy day to you 🙂
October 8, 2025 at 5:07 AM #49101ParticipantI also tried deactivating everything and switching themes from Bricks Builder.
Latest Metabox AIO update (with tax reordering) / WP: 6.8.3 / PHP: 8.4 / Brave BrowserThis is a big priority for me since this is my portfolio website that I need to get a job / get contract work since I've been laid off recently 🙁
I tried several things in those videos I recorded with Zight, so thank you for your patience viewing them!
October 8, 2025 at 7:24 PM #49106ParticipantGood day! 🙂
I was exploring reasons why the taxonomy advanced field doesn't set the post term, and I learned that if I set my custom fields as below for a CPT, my original CPT item white screen goes away and becomes viewable:
|-Clonable Group
|--Text Field
|--Cloneable Taxonomy(color) (only allow one taxonomy to be selected) value=red
__________________
|--Text Field
|--Cloneable Taxonomy(color) (only allow one taxonomy to be selected) value=blueIf I remove the clone ability from the taxonomy advanced field, the white screen for the original item goes away. Is this expected behavior?
October 8, 2025 at 7:26 PM #49107ParticipantEdit for above post: if I set my fields as cloneable as above, it makes my original CPT item non-editable with a blank white screen.
If I set my fields without a cloneable tax. adv. field, I can edit my original CPT item without a blank white screen.
Does not seem to fix the need to fill in my fields to save when editing the fields however.
October 8, 2025 at 7:47 PM #49108ParticipantRegarding "how can I have a custom taxonomy connect to a CPT via a tax / advanced tax field", it is not a bug.
I learned there are nuanced differences between tax. and adv. tax fields, its placement requirements, and how it saves data from this post: https://support.metabox.io/topic/how-to-set-taxonomy-terms-from-multiple-taxonomy-fields/#post-38573
However, I tried using the code in this forum answer from Peter: https://support.metabox.io/topic/syncing-group-taxonomy-advanced-field-with-a-taxonomy-field/
Does the code presented on March 28, 2023 at 7:38 PM work for cloneable groups or have internal workings changed? It doesn't seem to work for me.
October 8, 2025 at 7:58 PM #49109ParticipantRegarding "When editing custom fields, I get same random fields prompting me to fill in values now.", I realized some findings that might be helpful.
I had 2 clone-able URL fields with conditions that were both placed in different areas, but each of those conditions were set to a field that didn't exist. I deleted both of these URL fields completely before realizing that maybe having a condition set to a non-existent field might be the culprit but I don't know.
I also removed the "required" validation from the text and WYSIWYG fields. I lastly refresh the cache entirely (LSCASHE, OBJECT, etc.).
The form now works without it prompting me to fill in the details when editing the custom fields in Metabox.
Is this all expected behavior?
October 8, 2025 at 10:58 PM #49112Peter
ModeratorHello Robert,
Thanks for reaching out.
Glad to hear you can solve some issues on your own. I'm not totally sure what happens with the field group. If you know how to reproduce the issue with clear steps, please let me know. Or simply, export the field group that has the problem and share the JSON file with me. I will help you check the issue.
Following the documentation https://docs.metabox.io/extensions/meta-box-builder/#export--import
Regarding the taxonomy custom code, it is an example of how you use the action hook https://docs.metabox.io/actions/rwmb-after-save-field/
You can request a customization service to fix the custom code by submitting this contact form https://metabox.io/contact/October 9, 2025 at 1:22 AM #49117ParticipantSure thing, here is goes (first time using pastebin)
October 9, 2025 at 8:27 PM #49122ModeratorHello,
Can you please re-upload the file using the JSON format? The txt format isn't correct because all curly brackets are removed.
Or you can upload the file to Google Drive, Dropbox ... and paste the URL here.
October 9, 2025 at 8:57 PM #49124ParticipantOf course. My apologies, I didn't notice it in the rush.
October 11, 2025 at 9:06 AM #49131ModeratorI can see the issue with the URL field and conditional logic. I'm going to escalate this to the development team to check and fix the issue.
Thanks.
-
AuthorPosts
- You must be logged in to reply to this topic.