These started popping up today when I am logged in as a Content Administrator (not admin). I've found fixes for specific modules put this appears more generic.
sitename/home

Warning: Invalid argument supplied for foreach() in element_children() (line 6400 of...includes/common.inc).
Warning: Illegal string offset '#children' in drupal_render() (line 5867 of .../includes/common.inc).
Warning: Illegal string offset '#children' in drupal_render() (line 5877 of ...includes/common.inc).
Warning: Illegal string offset '#children' in drupal_render() (line 5915 of ...includes/common.inc).
Warning: Illegal string offset '#printed' in drupal_render() (line 5922 of..../includes/common.inc).
Not sure when it appeared, trying to figure that out. Tried disabling the last few modules enabled with no luck.

CommentFileSizeAuthor
#12 Screenshot_3_27_14_1_28_PM.png652.46 KBjaperry

Comments

ezra-g’s picture

Status: Active » Postponed (maintainer needs more info)

You selected Commons version 3.0. The most recent official release of Commons is 3.2.

Can you specify which version you're running?

markbannister’s picture

Version: 7.x-3.0 » 7.x-3.2

My mistake. Installed 3.2. Keep up to date with drush. All commons modules are 3.0 - 3.2.
Changed version in this post to 3.2

markbannister’s picture

Error went away then I hit the "follow" icon on a group on the home page and when it refreshed it came back. Next refresh it was gone.
Also got an error from flag module when hitting follow icon.....

eric imthorn’s picture

Subscribing

RobKoberg’s picture

This is a php5.4 related issue, I believe. I get it in my local environment running php54, but not a server running php53

ezra-g’s picture

Title: Groups Home screen errors » Groups Home screen errors with php 5.4
jpontani’s picture

Just to make sure everyone is on the same page, PHP 5.4 and higher is not officially supported by Commons just yet.

epruett’s picture

Title: Groups Home screen errors with php 5.4 » Attend an Event page errors to screen.
Version: 7.x-3.2 » 7.x-3.3
Issue tags: +Drupal Commons

I can confirm similar error per this thread.
Also I am running PHP 5.5.1 locally.
While trying to attend an event I get these errors to screen:

• Warning: Invalid argument supplied for foreach() in element_children() (line 6395 of ../commons733/includes/common.inc).
• Warning: Illegal string offset '#children' in drupal_render() (line 5862 of ../commons733/includes/common.inc).
• Warning: Illegal string offset '#children' in drupal_render() (line 5872 of ../commons733/includes/common.inc).
• Warning: Illegal string offset '#children' in drupal_render() (line 5910 of ../commons733/includes/common.inc).
• Warning: Illegal string offset '#printed' in drupal_render() (line 5917 of ../commons733/includes/common.inc).

timwee’s picture

Subscribing

ezra-g’s picture

Adding to the 3.4 radar. @timwee - You can subscribe by clicking the "follow" button - There's no need to commend on the thread, which generates an email notification.

ezra-g’s picture

Title: Attend an Event page errors to screen. » PHP 5.4 Attend an Event page errors to screen
Category: bug » support
Status: Postponed (maintainer needs more info) » Active
Issue tags: -Commons 7.x-3.4 radar +PHP 5.4

As jpontani points out in #7, PHP 5.4 isn't officially supported in Commons. The recommended version of PHP for Commons is 5.3, per the system requirements for Drupal 7 core.

We'd happily accept patches to resolve this issue for PHP 5.4 users. Marking as a support request.

japerry’s picture

Version: 7.x-3.3 » 7.x-3.x-dev
Issue summary: View changes
StatusFileSize
new652.46 KB

Indeed this is reproducible on php 5.4 with the dev version.

Since D8 requires 5.4 now, and most linux distros are now including 5.4 by default, I think it'd be good if we fixed this issue.

  • Commit cf65619 on 7.x-3.x by japerry:
    Issue #1995834 by japerry: Refactor attendee_count to remove php 5.4...
japerry’s picture

Status: Active » Fixed

Fixed! Had to do a little bit of refactoring of the attendee_count, it shouldn't have been just placed flat on the node build array. The commit above has the fix.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.