Forum Replies Created
-
AuthorPosts
-
February 2, 2026 at 3:58 PM in reply to: Error loading block: The response is not a valid JSON response. #49709
Key_Webdesign
ParticipantLooks like it's a memory thing. Still, this indicates that the block renderer uses too much memory in the proces. I'm constantly reaching the limit of 1 GB, which should be more than sufficient.
Here some lines from the error log:[Fri Jan 30 16:08:55 2026] Memory cgroup stats for /lve2428: [Fri Jan 30 16:08:55 2026] oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=/,mems_allowed=0,oom_memcg=/lve2428,task_memcg=/lve2428,task=lsphp,pid=3954594,uid=2428 [Fri Jan 30 16:08:55 2026] Memory cgroup out of memory: Killed process 3954594 (lsphp) total-vm:744688kB, anon-rss:80104kB, file-rss:15232kB, shmem-rss:4kB, UID:2428 pgtables:860kB oom_score_adj:0ParticipantAlright, but I do need the second value, since this is the playing time of a music album.
How should I format this with Meta Box fields to make it work, then?December 30, 2025 at 10:55 PM in reply to: Error loading block: The response is not a valid JSON response. #49568ParticipantWell, the thing is, the problem does not always occur. Also, not always on the same blocks... This makes it very hard to investigate, of course.
It seems to me it has something to do with the block-renderer, when you have several (more than 5) custom MB blocks in a page. The more custom MB blocks there are in a page, the higher the chance that one or more blocks will have this error. Sometime when I reload other blocks have the issue, sometimes all the errors are gone.I've seen this behaviour in multiple websites where I integrate custom blocks into a custom-made theme, using the MB Blocks extension of Meta Box.
Do you have any other ideas than the ones you proposed?
ParticipantUpdate: with Meta Box AIO 3.3.1, the issue seems to be fixed!
ParticipantI'm pretty sure it has to do with the combination of Meta Box MB Blocks and WPML. This is the stack trace I got:
[06-Nov-2025 15:23:49 UTC] PHP Fatal error: Uncaught TypeError: MetaBox\Integrations\WPML::get_translated_value(): Argument #2 ($field) must be of type array, false given, called in *path*/public_html/wp-includes/class-wp-hook.php on line 326 and defined in *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/src/Integrations/WPML.php:110 Stack trace: #0 *path*/public_html/wp-includes/class-wp-hook.php(326): MetaBox\Integrations\WPML->get_translated_value() #1 *path*/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() #2 *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/inc/functions.php(162): apply_filters() #3 *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/mb-blocks/src/functions.php(6): rwmb_get_value() #4 *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/mb-blocks/src/Loader.php(119): mb_get_block_field() #5 *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/mb-blocks/src/Loader.php(92): MBBlocks\Loader::prepare_render_callback_data() #6 *path*/public_html/wp-includes/class-wp-block.php(586): MBBlocks\Loader->MBBlocks\{closure}() #7 *path*/public_html/wp-includes/blocks.php(2359): WP_Block->render() #8 *path*/public_html/wp-includes/blocks.php(2431): render_block() #9 *path*/public_html/wp-includes/class-wp-hook.php(324): do_blocks() #10 *path*/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() #11 *path*/public_html/wp-includes/post-template.php(256): apply_filters() #12 *path*/public_html/wp-content/themes/giethoornvillage/page.php(16): the_content() #13 *path*/public_html/wp-includes/template-loader.php(106): include('*homepath*/d...') #14 *path*/public_html/wp-blog-header.php(19): require_once('*homepath*/d...') #15 *path*/public_html/index.php(17): require('*homepath*/d...')November 7, 2025 at 1:28 AM in reply to: Version 5.10.16 – 2025-11-05 not working with WPML sites #49289ParticipantYes, I got the same problem and error with Meta Box AIO.
I just went back to a previous version because of this.ParticipantHi there,
It might have something to do with the Redis Object Cache. I manually flushed the cache and now the svg icons have been renewed.
Good to know for other Redis users!ParticipantWould be great if the WPML issue would be addressed. It has not been working properly for quite some time now, and some of my client websites are having issues.
It's been over a month now...ParticipantWill the WPML issue be addressed?
I still have a few production sites that cannot be translated properly due to this issue.ParticipantWell, at least it's working, now.
The only thing that is not working still, are the WPML translations. Everything in the data of the MB Block is not showing up in the translation editor of WPML. This used to work fine.ParticipantHaving the same issue. All blocks are registered using the json method.
I have about 12 client sites that are broken because of this...ParticipantI'm experiencing the same issue on dozens of websites with Meta Box AIO installed. The Front End Submission is turned off everywhere.
April 20, 2023 at 7:39 PM in reply to: ✅Inline script does not fire inside render_template in the WP Block Editor #41564ParticipantFollowing up, what about dynamically rendered javascript?
For example, I want to make a slider block and this slider needs to be initialized. Depending on the Block settings, different javascript should be generated. Now, I can add inline javascript beneath the rendered block HTML but this doesn't fire, as Nicholas already pointed out.
Any ideas?ParticipantRight, I feared this was the case. Thanks for your explanation!
ParticipantI see the issue has been resolved.
Only now, the complete fontawesome css is loaded in the front-end too.
This should of course be limited to the back-end, right? -
AuthorPosts