In Embedded Media Field configuration>Import Settings
/admin/content/emfield/import
the error message appears as below.

warning: Invalid argument supplied for foreach() in /virtual/mysite/public_html/sites/all/modules/emfield/contrib/emimport/emimport.module on line 148.

Comments

aaron’s picture

Assigned: Unassigned » aaron
Status: Active » Fixed

fixed in the latest update (was a bug in the emfield module, actually, giving an empty array if no types were defined for a contributed module). thanks for bringing it to my attention.

ryo’s picture

Confirmed the fix. Thanks.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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

thomas_b’s picture

Status: Closed (fixed) » Active

Hi,
I'm having the exact same error as pasted above (three times one after the other!).
Any idea to solve this, or plans to solve this in the future?
Cheers,
T

mkrakowiak’s picture

I get the same error. Also displayed 3 times, one after another.

sonicthoughts’s picture

Same error for me. just one time at "import settings" I'm using flickr import.

mikeybusiness’s picture

Everything seems to work fine, however on selecting import settings, the following error appears.
warning: Invalid argument supplied for foreach() in /virtual/mysite/public_html/sites/all/modules/emfield/contrib/emimport/emimport.module on line 148.

In Embedded Media Field configuration>Import Settings
/admin/content/emfield/import

What was done for the original fix? Maybe a simple patch or user error?
Thanks for the great module by the way!

funana’s picture

On feed pages we notice the following error:

Invalid argument supplied for foreach() in /home/www/doc/1111/mysite.com/sites/all/modules/emfield/emfield.module in line 535.

alex ua’s picture

Title: warning: Invalid argument supplied for foreach() » warning: Invalid argument supplied for foreach() in embedded media import
Status: Active » Fixed

This is not the same issue. Please open up a separate ticket for this.

Please also confirm that you are using the latest dev release.

funana’s picture

Sorry, updated the module, seems to be fine now...

Anonymous’s picture

Status: Fixed » Closed (fixed)

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