Meta Box

Support Forum » User Profile

Forum Replies Created

Viewing 3 posts - 16 through 18 (of 18 total)
1 2
  • Author
    Posts
  • July 29, 2020 at 10:45 PM in reply to: ✅Last update breaks my wordpress #21016
    DFMDFM
    Participant

    Hi @long

    I can confirm that fix works for me. Many thanks.

    July 29, 2020 at 6:55 PM in reply to: ✅Last update breaks my wordpress #21007
    DFMDFM
    Participant

    Just the same: I've just upgraded to MB Builder 3.3.5 and it's hosed the wordpress install, s reported by WordPress ( 5.4.2 )

    Version 3.3.5 | By MetaBox.io | Visit plugin site

    This plugin failed to load properly and is paused during recovery mode.

    An error of type E_COMPILE_ERROR was caused in line 66 of the file [redacted]/www/wp-content/plugins/meta-box-builder/vendor/composer/autoload_real.php. Error message: require(): Failed opening required '[redacted]/www/wp-content/plugins/meta-box-builder/vendor/composer/../meta-box/mbb-parser/src/functions.php' (include_path='.:/usr/share/php')

    check on the filesystem that file does indeed not exist at

    [redacted]/www/wp-content/plugins/meta-box-builder/vendor/meta-box/mbb-parser/src/functions.php

    ls -l [redacted]/www/wp-content/plugins/meta-box-builder/vendor/meta-box/mbb-parser/
    total 0

    ls -l /srv/sites/chisenhale.org.uk/www/wp-content/plugins/meta-box-builder/vendor/meta-box/
    total 4
    drwx---r-x 2 www-data www-data 4096 Jul 29 12:52 mbb-parser

    I've tried to remove the plugin and re-install and the problem persists. Permission are all correct for nginx and php-fpm to load the files if they exist. The file it's looking for is simply not there.

    Fix needed asap.

    September 18, 2019 at 10:35 PM in reply to: ✅Migration Issue #16189
    DFMDFM
    Participant

    I've just hit this exact same issue, and given I've taken over the site the person above posted about I thought Id mention it here, in case someone else hits it.

    The field group had been built using the Metabox Builder, but the subsequent code wasn’t in functions.php whis means that it’s relying on the data in wp_posts.

    The config in wp_posts is serialized data and contains the string //dev.host

    When database migrations are run it does a dirty search and replace for all occurrences of //dev.host - that works fine, but in PHP serialised data the length of the value (jn characters) remains unchanged, so the if//dev.host is replaced with //live.host data in wp_posts can no longer be unserialised.

    This would usually throw an error when an invalid value was attempted to be unserialized, but meta-box-builder suppresses those by using @unserialize

    So the solutions are

    1) Make sure anything built with MB Builder are later hard coded into the thems functions.php (this makes sense, but I assume for this site it was left with the builder in place for convenience if requirements changed)
    or
    2) Fix the serialized data in those wp_posts on migration - as migration is a separate tool that would require some post processing and validation

    It's kind of ott to hard code host names in meta data, to be honest, as it hurts portability. I know this is something that WP do but if you could avoid it would b great.

    I'm going to go for solution 1 moving forward.

  • Author
    Posts
Viewing 3 posts - 16 through 18 (of 18 total)
1 2