Bug #23189 See Comments

Layout Publish `field_layout` doesn’t always survive EE2 -> EE3 upgrade

Version: 3.5.9 Reporter: obfuscode

EE2 exp_layout_publish table has 70 rows all with serialized field_layout data.

After upgrade, EE3 exp_layout_publish table has 70 rows but 45 of them have empty serialized field_layout data.


  • Can you export and share your exp_layout_publish table, please? Thanks!

    Derek Jones
    31st July, 2017 at 1:03pm
  • EE2/EE3 exp_layout_publish tables exported: https://www.dropbox.com/s/nm61ynywxry9u6f/exp_layout_publish.zip?dl=0

    31st July, 2017 at 1:13pm
  • In case it’s relevant, some of the fieldtypes may not have been available for EE3 or had their extensions disabled. If that’s the case, would the upgrade conversion fail?

    31st July, 2017 at 2:05pm
  • No, the layout conversion doesn’t validate or check for installed fields, the updater assumes that your existing layouts are valid and just changes them to the new storage format. I’ve followed up privately to get some additional information.

    Derek Jones
    31st July, 2017 at 4:51pm
  • Thanks for the tables and extra info. I’m unable to replicate with this data, however. Stepping through the updater, all layouts are being converted and saved properly. From a code point of view, the only way I can see an empty array resulting is if PHP is unable unserialize you existing field layout. However in the tables you provided, the serialized content is all valid.

    I’d be curious to see if in your environment you have PHP errors. Are you comfortable in your dev environment to reset the process? In system/ee/installer/updates/ud_3_00_00.php if you exit; rather than return from do_update(), that will halt the update at the end of 3.0.0. PHP warnings are non-fatal, so if that’s what happened, you may not have seen them before the updater redirected to the next step maybe.

    Derek Jones
    01st August, 2017 at 5:15pm

You must be signed in to comment on a bug report.

ExpressionEngine News

#eecms, #events, #releases