Warning: Invalid argument supplied for foreach()

Support has been upgraded!



The Support Forum is closed. Not to worry!  Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.

Premium Support

Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?

Please open a Support Ticket in your user account.

Click here to open a support ticket.

Free Support

Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.

Please open a new support topic in the WordPress support forums for Connections.

Click here to open a support topic.

This topic is: resolved

Tagged: , ,

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • 01/15/2019 at 10:21 pm #481772
    Rebecca Hagen
    Participant

    I am receiving the following warning on a live website:

    Warning: Invalid argument supplied for foreach() in

    /home/content/83/12215383/html/wp-content/plugins/connections/includes/class.retrieve.php on line 709

    here is the website and page: https://pinellascma.org/members/

    I have seen this error frequently in the forum. The data is pretty clean now, so I don’t know what is generating this warning, or why it doesn’t fail more gracefully (test the data before executing the foreach). As far as I can tell, the actual search results appear pretty complete.

    Using PHP 5.6, the most recent version of WP, and the cMap template.

    Attachments:
    You must be logged in to view attached files.
    01/16/2019 at 12:06 am #481778
    Steven Zahm
    Keymaster

    @ Rebecca

    RE: I have seen this error frequently in the forum

    An update which addresses this warning was released earlier today, please navigate to the WordPress Plugins admin page and update to 8.36.1.

    Once in a great while testing does not cover a scenario in which an warning might be issued by PHP makes thru to release. A quick search of the forums shows about 20 instances over roughly 5 years with most posts being from multiple users for the same occurrence.

    I do my best to make sure that none ever slip through but it does happen. I apologize for the trouble and inconvenience this has caused you!

    The best solution to ensure PHP errors and warnings are not displayed publicly. This is considered to be a best practice for live websites.

    Here’s a link to a tutorial which you can use to ensure these are not publicly displayed:

    https://connections-pro.com/faqs/hide-php-warnings-notices/

    Hope this helps! Again, apologies for the trouble!

    01/16/2019 at 9:14 am #481839
    Rebecca Hagen
    Participant

    Steven: Thanks for your blindingly fast response, and the quick update. This repaired the issue. Definitely a sign of professionalism in your work.

    01/16/2019 at 9:53 am #481845
    Steven Zahm
    Keymaster

    @ Rebecca

    Thanks! I do endeavor to resolve issues as quickly as I can when they are encountered.

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)

You cannot reply to this support topic. Please open your own support topic.