Forum Replies Created
-
AuthorPosts
-
April 3, 2026 at 11:17 AM in reply to: ℹ️Bug Report - Block Editor Field: missing list-item-block / Styling h2 #49883
Anh Tran
KeymasterIn your video, I already see that the list item is available in the breakgrams below the editor. In my test, it is available automatically. You don't have to choose that.
Regarding the lists automatically created, I couldn't replicate that. I thought maybe you clicked "saved as" button that saves the list. I can't see it in the video, so I don't know what happened.
Anh Tran
KeymasterHi Francois,
From your video I saw that the connection is lost. So I think there must be something wrong with the connection. Maybe the internet or your server. In that case when builder is sending data to save or doing something, maybe REST API request, the request is dropped or interrupt and cannot be completed, which caused the error.
In this case, I will check the debug log or the PHP error log. I'm not familiar with XCloud, so I can't tell you where to look at, but you can reach out to them to ask for where is the PHP error log.
It's best to frequently save field groups to avoid connection issues like that, especially when working with large groups.
April 2, 2026 at 4:04 PM in reply to: ℹ️Bug Report - Block Editor Field: missing list-item-block / Styling h2 #49873Anh Tran
KeymasterHi,
For the first issue, WordPress only needs the list block to be available, then on the list item block is automatically added to the allowed list. You can see that when you see the block navigation at the bottom of the field, when you put the cursor inside a list item, it will show Document \ List \ List item.
For the styling (2, 3), currently our implementation doesn't use iframed content for the block editor field, so all the styles of the content inside the block editor field is inherited or mixed with the styles of the WordPress admin. That's why you see the list doesn't have bullet points and the heading two has very small font size. We are working on that to see if we can use the iFrame for the content the same as WordPress does.
Regarding the footnote error in the console, it doesn't affect anything. It's just when we register blocks for the block editor field, it registers the same blocks that WordPess core already did. We have to do that again because for some post types the editor is not block editor but classic editor.
We'll add class field for the custom HTML field. Thank you for your feedback.
March 23, 2026 at 8:47 AM in reply to: Error loading block: The response is not a valid JSON response. #49832Anh Tran
KeymasterHi @[email protected],
Your issue is a different one, which relates to how the builder loads. Please send us a temp. login via our contact form, so we can take a closer look into it. Perhaps a simple warning/deprecated message from other plugins can break the JSON responses for the builder.
March 21, 2026 at 9:37 AM in reply to: Error loading block: The response is not a valid JSON response. #49826Anh Tran
KeymasterHi,
I have fixed this issue and sent you an email to test the new version. Can you please try this?
November 11, 2025 at 11:08 AM in reply to: Contribution (pt_BR Translation) + Report on Non-Internationalized Strings #49312Anh Tran
KeymasterHi Jayron,
Thanks a lot for your contribution. We've updated the translations for the plugins that you sent.
Regarding the translation format, since WordPress 6.5, it supports a new and more performant format for translation file
.l10n.phpinstead of the old-fashioned.mofile. We use this format in our plugins to have a better performance. We also converted all of your translations to this new format, so you don't have to do that and send us again.Regarding translations for strings in JavaScript (which is used in UI), we have updated our
.potfile. When you create a translation for it, please follow this step:- Create a
.pofile from.pot
- Run the following command to create JSON file:cd /path/to/plugin/folder wp i18n make-json languages --no-purgeUnfortunately, I know the only way to do that is via
wp-cli. I'm not sure if plugins like Loco Translate or WPML support creating JSON file for translating strings in JS.Anh Tran
KeymasterIn the latest version, we remove the inline HTML above. They were used for media and upload fields.
For the inline CSS, there is no way to change this behavior. However, you can remove them (and also inline CSS for WP blocks) using this snippet:
add_filter( 'styles_inline_size_limit', '__return_zero' );
August 14, 2025 at 3:04 PM in reply to: JavaScript error on admin pages without Meta Box dashboard elements #48727Anh Tran
KeymasterHi Nick,
We only enqueue
dashboard.json the Dashboard page, as you can see the source code here. We run the enqueue styles and scripts onload-$page_hook, which fires only on that admin page.Is there any special set up on your site? Can you please try with a fresh install?
Anh Tran
KeymasterWe added support for outputting inline style, to improve the site's performance. See more details here.
FYI: inline style is not that bad 🙂
Anh Tran
KeymasterHi, we have a fix for this bug here. Can you please try it and let us know if that fixes?
Anh Tran
KeymasterHi, we have a fix for this bug here. Can you please try it and let us know if that fixes?
August 6, 2025 at 9:54 PM in reply to: ℹ️Add localhost prefix support to detect-dev-staging-domain.php #48660Anh Tran
KeymasterHi,
"localhost" is always treated as dev domain (note, we verify by domain, not port, so "localhost" will work for all hosts like "localhost:8080", etc.). You can see the source code here.
We also added ".localhost" suffix so all domains *.localhost will be treated as dev domains.
May 28, 2025 at 10:43 AM in reply to: Unintended auto-update crashes custom fields and causes fatal error #48333Anh Tran
KeymasterHi Yumikom,
I guess you were referring to the constants
RWMB_CSS_URL(added since the beginning of Meta Box) andRWMB_CSS_DIR(added 17 months ago). Probably you were using a very old version of Meta Box, and WP auto updates an extension that usesRWMB_CSS_DIR.Let us work on the auto update and will fix this issue.
May 21, 2025 at 9:17 AM in reply to: ✅Upgraded to AIO, now meta fields won't display unless free MB is activated #48302Anh Tran
KeymasterThe problem is that Meta Box AIO loads Meta Box at
inithook (with priority -5). If you put the snippet to definerwmb_metafunction in your theme'sfunctions.php, then it will load **before**, which defines an emptyrwmb_metafunction.This method was usually used for themes that are sold like on ThemeForest, to prevent errors of undefined function
rwmb_metawhen they haven't installed Meta Box yet.In your case, I'd recommend removing that snippet, and it will work fine.
November 8, 2024 at 5:11 PM in reply to: ✅Fontend submission : classic type content -- convert to blocks? #46892Anh Tran
KeymasterHi pixluser,
This feature is done and will be included in the next version of MB Frontend Submission.
-
AuthorPosts