Support Forum ยป User Profile

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • Juan FernandezJuan Fernandez
    Participant

    Hi Peter

    Yes, I know that the documentation says that, but that makes no sense, I think you should put an effort in make it possible. There is a risk that using the latest version breaks things in automated environments, and that increases the cost of maintenance. This is B2B we're talking about.

    The documentation is saying "yet" since the first time I used MetaBox, at least one year ago, is there any plan to implement it?

    Meanwhile I guess the only solution is to keep it in a private repo and disabling installing from your repo directly.

    Thanks!

    Juan FernandezJuan Fernandez
    Participant

    Hi all

    Sorry I was previously mistaken, it's not a PHP version problem, but somehow in the last MetaBox-AIO package its showing all errors on the site, which previously hadn't. And then it breaks a lot of things.

    I could solve it by setting in wp-config.php the following setting

    define('WP_DEBUG', false);
    define('WP_DEBUG_DISPLAY', false);

    Please check that I had to set WP_DEBUG_DISPLAY because it somehow was set even when WP_DEBUG was set to false.

    Thanks!

    Juan FernandezJuan Fernandez
    Participant

    Hi all

    I've continued investigating this issue and found out that both versions of Metabox are breaking, the problem lies in the PHP version.

    It works ok with PHP version 8.2.17, but if upgraded to version 8.2.18, this deprecation error hits and breaks the sites. This PHP version has been pushed 12 days ago on the DockerHub WordPress image 6.5.2-php8.2.

    What is the suggested solution?

    Thanks!

Viewing 3 posts - 1 through 3 (of 3 total)