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

Support archive

Low Variable Groups issue after EE 2.10.1 Update

Tyson 29 Jun 2015 23:18 problem, complete

After updating EE to 2.10.1, I am unable to view LV Groups with two or more variables with variable types of Wygwam. The variable themselves are still intact and display on the site, but we are unable to edit the variables within groups of more than one wygwam field type.

The message we get when trying to view a group's assigned variables is the following:
"This page was intentionally left blank.
To Regenerate your Image Sizes and see your Legacy Settings click on the corresponding menu item in the upper right corner."

We are running the latest Wygwam version of 3.3.3 as well as the latest version of Low Variables.

Thanks!

Replies

  1. Low 30 Jun 2015 07:34

    Do you have a screenshot of this? I cannot reproduce (although I'm not on the latest version of Wygwam), which leads me to believe this might be more of a Wygwam issue than a LV one...

  2. Tyson 30 Jun 2015 19:35

    Thanks for the reply Low!

    Below is the screenshot. It's a weird issue. The message appears to be from DevDemon's Channel Images because it refers to "legacy settings" and i believe the only module we have that has that button value is Channel Images. But then, the field type that's selected in LV is of a Wygwam type. This issue only arises with multiple Wygwam field types. If I convert the type into a textarea, LV works as normal.

    Thankfully this problem is on a staging server to test before moving over to our production server. Needless to say, we'd like to solve this issue before impementing the EE 2.10.1 update before going implementing it on our live environment.

    I'll also post this issue on Pixel&Tonic's support system per your suggestion that it may be a Wygwam issue.



    Thanks for looking into this Low!

  3. Low 1 Jul 2015 07:31

    I just released a new version of LV. Can you try and upgrade? Make sure you delete the old files before replacing them with the new files (rather than a merge).

  4. Tyson 1 Jul 2015 21:39

    Thanks Low! The update solved our issues. Thanks again for a great product!