4 replies [Last post]
Nice Deli's picture
Offline
Joined: 11/05/2009
Juice: 124
Was this information Helpful?

warning: array_keys() [function.array-keys]: The first argument should be an array in /home/******/public_html/main/includes/common.inc on line 3360.
warning: Invalid argument supplied for foreach() in /home/******/public_html/main/includes/common.inc on line 3363.

I know there are already a few forums pertaining to these types of warnings but I've gone over them and none have helped me, i've disabled any unnecessary modules, flushed the caches numerous times, run cron, run update and this warning won;t go away and is on every page not just for admin.

This message began to appear after my site moved to a new server, please help!

Nice Deli's picture
Offline
Joined: 11/05/2009
Juice: 124
fatal errors

also getting these fatal errors on various pages when trying to logout, view different pages etc:

Fatal error: require_once() [function.require]: Failed opening required 'modules/modules/forum/forum.pages.inc' (include_path='.:/usr/lib/php') in /home/******/public_html/main/includes/menu.inc on line 346

www.nicedeli.com

GreyHawk's picture
Offline
Joined: 03/17/2009
Juice: 174
Deja vu

We just had to do an emergency server move, and some of the issues that we encountered had to do with similar messages.

For the modules that you're having trouble with that are showing up in the messages, we did the following:

1. Put site into maintenance mode
2. download fresh copies of the modules to the local machine, unzip, and prepare to FTP them back up
3. Connect with FTP; DELETE the individual contributed module folders that we're about to re-upload.
4. Upload the "fresh" copies of the modules
5. Run update.php and cron

What we'd experienced was corruption of files and incomplete copies -- we'd FTP'd the existing site down to our local machine, switched to the new host, then FTP'd the site contents back up. No errors reported, but once we flipped the switch we got inundated with those types of errors. A little investigation showed that even while some files appeared to copy, they were corrupt.

Deletion of the offending module and replacement with a fresh copy appeared to fix that.

Two other elements to look at:

1. Your /sites/default/files directory: ensure that you set it and all contents (files/folders) to be writable.
2. Be sure you set up a tmp/image (images?) folder in the root of the Drupal install (or wherever recommended) if you are using image modules that require it, and be sure to review permissions to ensure that the image directory and all contents are also fully writable, as above.

Good luck. Smiling

GreyHawk's picture
Offline
Joined: 03/17/2009
Juice: 174
Question: Are you sure you're putting modules in the right spot?

Are you putting your contributed modules and themes under "/sites/all/modules" and "/sites/all/themes", respectively, and not into the core Modules and Themes folders...?

That would be another potential cause for hiccups and crashes.

If you've done that, you should be able to simply move them to the right locations and then resolve with an update.php. (Yeah, been there / done that when uploading too quickly...seems like centuries ago, but you never forget the boneheaded boo-boos.) Eye-wink

Nice Deli's picture
Offline
Joined: 11/05/2009
Juice: 124
Re: Question: Are you sure you're putting modules in the right s

Not sure what caused it, had to go to an older backup and lose some new data (customers and orders), alls working now.

Thanks!