The following warnings occurred: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Warning [2] Undefined array key "avatartype" - Line: 783 - File: global.php PHP 8.1.31 (Linux)
|
![]() |
Editing the Database Columns clears my Field Pass settings - Printable Version +- Form Tools (https://forums.formtools.org) +-- Forum: Form Tools (https://forums.formtools.org/forumdisplay.php?fid=1) +--- Forum: General Discussion (https://forums.formtools.org/forumdisplay.php?fid=5) +--- Thread: Editing the Database Columns clears my Field Pass settings (/showthread.php?tid=1601) |
Editing the Database Columns clears my Field Pass settings - russellfeeed - Sep 6th, 2011 Hi in 2.0.6 if I add a new column using the Database tab, all my 'Pass On' checkboxes get cleared. I have to try to remember which of my 90-odd fields need to be checked again. ;-( I can get it to remember the Pass On settings, only if I select Pass On when adding the new Database Columns. Is this a feature or a bug? Cheers Russell RE: Editing the Database Columns clears my Field Pass settings - Ben - Sep 6th, 2011 Hi Russell, Yeesh, no that's definitely a bug. However, this never occurred for me. Would you mind installing the Database Integrity module and running it on your system? I just want to find out if there's a deeper problem: http://modules.formtools.org/database_integrity/ - Ben RE: Editing the Database Columns clears my Field Pass settings - tinman - Sep 8th, 2011 Yes, I have a similar problem on a new 2.1.1 install. All enabled Pass On boxes get cleared once I click the update button but it seems that it will still pass the field. I'm just never sure if the pass on feature is on or off since I can't see it. RE: Editing the Database Columns clears my Field Pass settings - Ben - Sep 9th, 2011 *Drat*, this is a bug. I'll release a patch release today for this (it's a pretty serious problem!). - Ben RE: Editing the Database Columns clears my Field Pass settings - Ben - Sep 10th, 2011 Hi guys, I just released 2.1.2, which includes a fix for this problem. Thanks for letting me know! - Ben |