We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

[3.4.0 DP] Toggle fieldtype bug in Grid

Developer Preview

Derek Hogue's avatar
Derek Hogue
316 posts
8 years ago
Derek Hogue's avatar Derek Hogue

When saving a Toggle field in the a Grid field, I’m getting this error:

Undefined index: field_default_value ee/EllisLab/Addons/toggle/ft.toggle.php, line 224

field_default_value is still saved correctly though.

       
Kevin Cupp's avatar
Kevin Cupp
791 posts
8 years ago
Kevin Cupp's avatar Kevin Cupp

I’m unable to reproduce this one, and we have automated tests making sure that field saves correctly inside Grid. Any add-ons installed? Or any more specific steps to reproduce?

       
Derek Hogue's avatar
Derek Hogue
316 posts
8 years ago
Derek Hogue's avatar Derek Hogue

Going through the steps again I’m finding that it only triggers when saving an existing Grid field which already had the Toggle column. It saves fine when you first add the new Toggle column to a Grid.

I do have add-ons installed, but I just tested this on two separate installs of 3.4.0, with different sets of add-ons installed.

       
Kevin Cupp's avatar
Kevin Cupp
791 posts
8 years ago
Kevin Cupp's avatar Kevin Cupp

Ah yes I see what’s happening now. It’s not a fatal PHP error, just a notice, so it was hidden by the redirect. I think it’s been that way for a while, but doesn’t look like it’s made anything functionally broken. Curious, how did you come across this? Did you happen to halt execution before it could redirect?

       
Derek Hogue's avatar
Derek Hogue
316 posts
8 years ago
Derek Hogue's avatar Derek Hogue

Not that I’m aware of - this is on two separate local installs, and I haven’t altered any core files.

It looks like it’s actually the EE_Exceptions::show_php_error() method that’s halting execution after this notice is thrown.

       
Kevin Cupp's avatar
Kevin Cupp
791 posts
8 years ago
Kevin Cupp's avatar Kevin Cupp

Maybe your error reporting levels are set differently, curious how this hasn’t come up before. Either way, it should be fixed in the next build. Thanks!

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.