Meta Box

Thank you Peter! What a good note to read. Much appreciated! Say hi to your lovely team

Hi Peter! Switching to PHP version 7.4 did solve this particular problem. Thanks for this! However, I can't really say this solution is viable, as I must use a more recent PHP version for security and performance reasons. 7.4 on the other hand End of Life since Nov '22 and increases risks of security vulnerabilities, performance degradation, and application instability.
My request is therefore if you can aks MB's developers to update this functionality to work with the more recent PHP versions? Version 8 came out in Nov '20, 8.1 in Nov '21, 8.2 in Dec '22, 8.3 in Nov '23 and 8.4 just recently (although I understand that the latest version is too recent for many people). I hope your team is able to make Meta Box fully compatible with PHP 8 at the minimum, and so I can use this particular functionality again.

I will have to stick to PHP 8 and so will have to deactivate the text-limiter function although that is an important reason for why I went for Meta Box. I am afraid to run into more PHP 8 issues :s.

Please let me know if your developers will pick this up.

Thanks so much for your presence, Peter. You are helping a ton!

My text-limiter extension was on, and when turning it off the error disappears...

I've been able to produce a debug.log:

[22-Jan-2025 15:18:50 UTC] PHP Fatal error:  Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in /home/u412395423/domains/mydomain.com/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/text-limiter/text-limiter.php:85
Stack trace:
#0 /home/u412395423/domains/mydomain.com/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/text-limiter/text-limiter.php(85): str_contains()
#1 /home/u412395423/domains/mydomain.com/public_html/wp-includes/class-wp-hook.php(326): MB_Text_Limiter->get_value()
#2 /home/u412395423/domains/mydomain.com/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#3 /home/u412395423/domains/mydomain.com/public_html/wp-content/plugins/meta-box/inc/functions.php(162): apply_filters()
#4 /home/u412395423/domains/mydomain.com/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/mb-rest-api/src/Base.php(64): rwmb_get_value()
#5 /home/u412395423/domains/mydomain.com/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/mb-rest-api/src/Base.php(49): MetaBox\RestApi\Base->get_values()
#6 /home/u412395423/domains/mydomain.com/public_html/wp-includes/rest-api/endpoints/class-wp-rest-controller.php(439): MetaBox\RestApi\Base->get()
#7 /home/u412395423/domains/mydomain.com/public_html/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(2070): WP_REST_Controller->add_additional_fields_to_object()
#8 /home/u412395423/domains/mydomain.com/public_html/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(635): WP_REST_Posts_Controller->prepare_item_for_response()
#9 /home/u412395423/domains/mydomain.com/public_html/wp-includes/rest-api/class-wp-rest-server.php(1292): WP_REST_Posts_Controller->get_item()
#10 /home/u412395423/domains/mydomain.com/public_html/wp-includes/rest-api/class-wp-rest-server.php(1125): WP_REST_Server->respond_to_request()
#11 /home/u412395423/domains/mydomain.com/public_html/wp-includes/rest-api.php(576): WP_REST_Server->dispatch()
#12 /home/u412395423/domains/mydomain.com/public_html/wp-includes/rest-api.php(2957): rest_do_request()
#13 [internal function]: rest_preload_api_request()
#14 /home/u412395423/domains/mydomain.com/public_html/wp-includes/block-editor.php(756): array_reduce()
#15 /home/u412395423/domains/mydomain.com/public_html/wp-admin/edit-form-blocks.php(77): block_editor_rest_api_preload()
#16 /home/u412395423/domains/mydomain.com/public_html/wp-admin/post-new.php(72): require('/home/u25520214...')
#17 {main}
  thrown in /home/u412395423/domains/mydomain.com/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/text-limiter/text-limiter.php on line 85

The Open Street Map field and the text field starting with 'address' for its ID is a subgroup of a group. I tried moving them one level up (so that they were no longer a subgroup of a group, but just a group). This didn't help. The tiles still do not render well.

I tried taking both fields out from group level to just be unnested fields (so not under any group). This also did not help. The tiles still do not render well.

The conditional logic itself is set up correctly: the osm field and the text field both should only become visible if another field, a 'work setting' field (select field type) is set to the value 'on-site'. The conditional logic in itself is working correctly: the osm and address field show when intended. But the conditional logic somehow produces the side effect that the tiles of the OSM do not load properly. The majority remains not rendered. When I move the map around with my mouse, some of the new tiles that come into view do render. Most do not. Zooming in and out on the map also leads to some tiles rendering, others (most) won't load. Entering the address also produces the same behaviour.

When the conditional logic is turned off, the tiles do load properly. However this can't be the solution: I really do need the map and address field to show only when the other field is set to 'on-site'.

This behavior is confirmed to not have to do anything with the max_input_vars, because since our last exchange of thoughts I have increased the max_input_vars and the whole custom group has now become larger....
I can't share the entire custom fields group here though...

What could be the problem here?

Dear Peter, Thank you so much! This worked! Increasing the max_input_vars value to something higher allows me to add my form with some more form fields.

I did have a small issue with the tutorial you linked to, and I have a work around. I learned it is wise to not have a phpinfo.php that the public can reach because it gives away site configuration information to possible attackers. I could also not locate the php.ini file through something like Filezilla. The solution for both issues was to go to my webhosting environment. There I could find the max_input_vars value through (and this might be different for everyone, depenidng on how your host sets it up) 'Manage your website' > there was a sidebar ‘Advanced’ > PHPinfo. There you can see ‘max_input_vars´. You can change it through Advanced > PHP configuration > PHP options > maxInputVars. I set it from 5000 to 10000, and tested the form and it now works. Thanks Peter and Meta Box!

This topic can close.

There is another issue going on, too. I made a separate topic about it here (https://support.metabox.io/topic/custom-fields-broken/). It seems I have reached some sort of limit in terms of custom fields group. I can't add more fields, and the post type my custom field group is associated with always defaults back to the standard WordPress 'post' post type. As a matter of fact, I can't even set geo = true in the custom settings of the field group. Clicking 'update' doesn't change that.

At the moment I can't continue working on my field group... . Thanks for any help.