All Low add-ons are now owned by EEHarbor. Read the blog post.

Support archive

LV issue after upgrading to EE 3.5.6

DennisDerammelaere 23 May 2017 18:57 problem, complete

After upgrading to EE 3.5.6 (from 2.11.9), I am getting the following error when trying to create a new custom field.

No such property: 'low_variables_group_model' on EllisLab\ExpressionEngine\Legacy\Facade

ee/EllisLab/ExpressionEngine/Legacy/Facade.php:107


Someone at EllisLab helped me to temporarily fix the issue, but he suggested contacting you for a proper fix. Below is what he did. Any help with this is greatly appreciated!


I don't know Low Variables well enough to debug it. So for the moment, I've hacked it to remove that field type from the field type options when creating new fields. It doesn't look like you had any existing low variable field types, so I don't think this is a critical issue.

What I did was simply 'return' in on line 105 of /zamp/user/addons/low_variables/ft.low_variables.php. You'll need to contact Low for a permanent fix. I'm just not sure what's going on in there. But I was able to add and then delete a custom field after making the temp fix.

Replies

  1. Low 23 May 2017 20:07

    Hmm. Can you check if the Low Variables extension is enabled? Looks like it might not be.

    In the CP, check Developer > Utilities > Debug extensions.

    If no extensions are found, the 'allow_extensions' setting in the config is probably set to 'n' (should be 'y').

    If there are extensions, make sure the Low Variables extension is enabled.

  2. DennisDerammelaere 23 May 2017 21:40

    You are absolutely right. I changed that config setting to "y" and then removed the hack that the EE support person created. I am now getting the following error.

    Invalid argument supplied for foreach()
    user/addons/low_variables/helpers/low_variables_helper.php, line 66


    Any thoughts?

  3. DennisDerammelaere 24 May 2017 00:10

    The EllisLab support person says he figured it out. He didn't explain what he did, but it seems to be working as expected now.
    Thanks,
    Dennis