Having errors and images not showing.
 

I am having issues with vbgallery. I am getting this error:
Warning: Invalid argument supplied for foreach() in [path]/gallery/gallery_global.php on line 314

I was running beta 3 and the errors were worse so I upgraded to the stable release. I am running 4.04 currently. Line 314 in gallery_global.php is this line:
foreach ($gallery_modcache AS $moderator)

I have recently had APC cache installed on my server and vb4 is setup to use it. I need to get this fixed asap as our members use the gallery a lot.

Thanks,

It is working now. I don't really know what fixed it other then waiting for vbgallery cache to clear out.

I am still having trouble with this now. I did the 4.08 update to the live site yesterday and I am having the same error on line 314. It doesn't show for administrators, just everyone else.

Here is the exact error that gets printed out:
Warning: Invalid argument supplied for foreach() in [path]/gallery/gallery_global.php on line 314

I have reuploaded the file also and still no go.

It definitely has to do with having cache. I disabled apc via the vb config file and the error went away. Can someone tell me what to update so I can turn the cache back on?

Any suggestions or help on this? Would really like to enable apc again on vb.

Nobody has any ideas? I would really like to be able to enable apc again on vb4. Every little bit helps.

Well there have been some errors with xcache, but they were of completely different nature, the whole vbgallery datastore was vanishing on every cache update...


IF that line is the only issue, it could be, (i dont know) that the cache sets an empty array to '' or simply unsets it.
To see if its that issue.. define a moderator for any category. then the array should not be empty.


If the error persists with a moderator defined, do following:
open gallery/gallery_global.php
find:
replace with:
Luc

Thank you for the response. I did notice the error wasn't showing for me as admin and thought everything was alright until members started pointing it out and then I logged in as a normal user and seen the error. I will check also with a moderator user. Will let you know the results.