https://legacy.forums.gravityhelp.com/topic/bug-invalid-argument-supplied-for-foreach-forms_modelphp Gravity Support Forums Topic: BUG: Invalid argument supplied for foreach() forms_model.php en-US Sun, 19 Apr 2026 18:25:01 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/bug-invalid-argument-supplied-for-foreach-forms_modelphp#post-72313 Thu, 23 Aug 2012 12:56:38 +0000 Alex Cancado 72313@https://legacy.forums.gravityhelp.com/ <p>@infomedia, thanks for the heads up. The changes you have suggested make sense.<br /> Huw, I have a new version with the change. Send me an email to <a href="mailto:alex@rocketgenius.com">alex@rocketgenius.com</a> if you would like to try it and see if it fixes your issue. Make sure to include a link to this post. </p> https://legacy.forums.gravityhelp.com/topic/bug-invalid-argument-supplied-for-foreach-forms_modelphp#post-72268 Thu, 23 Aug 2012 10:12:00 +0000 Huw Rowlands 72268@https://legacy.forums.gravityhelp.com/ <p>I am getting this warning after upgrading and cannot see the entries of my form?</p> <p>Warning: Invalid argument supplied for foreach() in /home/inspired/public_html/dev/ukweddingawards/wp-content/plugins/gravityforms/forms_model.php on line 2612</p> <p>Can this be resolved? </p> https://legacy.forums.gravityhelp.com/topic/bug-invalid-argument-supplied-for-foreach-forms_modelphp#post-72092 Wed, 22 Aug 2012 10:45:53 +0000 infomedia 72092@https://legacy.forums.gravityhelp.com/ <p>In the function build_lead_array on line 2577 of forms_model.php, there is a check on line 2582 "if(is_array($results) &amp;&amp; sizeof($results) &gt; 0)", however the closing bracket is on line 2585, and on line 2588 there is a foreach loop on the $results variable, outside the check to see if it's an array. This throws an PHP WARNING. I'm not sure if this is the root of the problem, but by moving this loop inside the bracket (placing the bracket on line 2605), it causes the notice to go away. I'm not sure if this has been addressed or mentioned already, but wanted to bring it to the attention of the developers. </p>