Low Variables 2.6.0, Grid 1.0, EE 2.7.3 - PHP errors when selecting Grid field type.
Low Variables 2.6.0, Grid 1.0, EE 2.7.3 - PHP errors when selecting Grid field type.
onfigure Grid
What data do you want to collect?
A PHP Error was encountered
Severity: Notice
Message: Undefined variable: form_base
Filename: views/settings.php
Line Number: 27
A PHP Error was encountered
Severity: Notice
Message: Undefined variable: settings
Filename: views/settings.php
Line Number: 35
A PHP Error was encountered
Severity: Notice
Message: Undefined variable: settings
Filename: views/settings.php
Line Number: 40
A PHP Error was encountered
Severity: Notice
Message: Undefined variable: settings
Filename: views/settings.php
Line Number: 45
A PHP Error was encountered
Severity: Notice
Message: Undefined variable: screen_name_field_errors
Filename: views/settings.php
Line Number: 45
A PHP Error was encountered
Severity: Notice
Message: Undefined variable: settings
Filename: views/settings.php
Line Number: 51
A PHP Error was encountered
Severity: Notice
Message: Undefined variable: title_field_errors
Filename: views/settings.php
Line Number: 51
A PHP Error was encountered
Severity: Notice
Message: Undefined variable: settings
Filename: views/settings.php
Line Number: 56 
Replies
Low 30 Apr 2015 17:43
That's looking like an add-on conflict. Grid is loading the wrong view file here. Possibly one that has to do with user management.
As the native Grid field is responsible for generating those settings, it’s not something LV can influence...
TechNinja 26 Sep 2015 06:13
I thought 2.6.1 will fix this with the new naming convention. but it didn't.
still cant use grid with LV.
bump
TechNinja 26 Sep 2015 06:26
Hi Low,
I found the culprit is zoo_visitor.
I simply temporarily renamed the settings.php in the views folder under
/system/expressionengine/third_party/zoo_visitor/views
and it worked just fine. can you help me figure what causing this error and how can I make these two co-exist peacefully ?
Low 26 Sep 2015 08:39
I think you saw this bug report: https://support.ellislab.com/bugs/det... -- the issue addressed there is the same, but outside of LV.
This means it's not something LV can fix. It's basically due to EE's add-on system and the way it loads up views.
I'm hoping and thinking this will be solved in EE3.