Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By indian1985 on
I built my drupal 7 site in acquia, and I just migrated the site onto my remote server. All of the pages exist but aren't all printing content.
When I go to the content section in the admin panel I have all these errors:
I've tried reuploading the root modules and includes folder and that didn't resolve anything.
Notice: unserialize() [function.unserialize]: Error at offset 10269 of 23571 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Notice: unserialize() [function.unserialize]: Error at offset 6894 of 18582 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Notice: unserialize() [function.unserialize]: Error at offset 14944 of 39419 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Notice: unserialize() [function.unserialize]: Error at offset 8136 of 20171 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Notice: unserialize() [function.unserialize]: Error at offset 5032 of 11801 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Notice: unserialize() [function.unserialize]: Error at offset 2253 of 6005 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Notice: unserialize() [function.unserialize]: Error at offset 1942 of 4793 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Notice: unserialize() [function.unserialize]: Error at offset 6571 of 18790 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Notice: unserialize() [function.unserialize]: Error at offset 7744 of 22634 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Notice: unserialize() [function.unserialize]: Error at offset 9333 of 24993 bytes in DrupalDatabaseCache->prepareItem() (line 405 of includes/cache.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Warning: Invalid argument supplied for foreach() in field_attach_load() (line 644 of modules/field/field.attach.inc).
Comments
clear caches
Always try running cron. In this case clearing caches should fix both. If clear caches button under performance does not work, do it more completely with drush, the contrib module admin toolbar, the devel module, or by emptying the relevant tables via phpmyadmin.
Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors
Hi, Indian! I have same
Hi, Indian!
I have same errors.
Please, tell me, how you have beat it?
can't clear cache or update database
hey i have exactly these errors after trying to set up a performance version of my site. I can't seem to clear my caches or update my database. Does anyone know what I could do to remove these errors?
Thanks
What is a performance
What is a performance version?
Only in the past few days I had a site on its own server where cron would not run. Neither server nor site faulty. The server was just not beefy enough to handle the site (until I tuned it). So first check the quality of the server you are using. But would know if this was an issue because you would start seeing 'mysql server has gone away' errors in the server logs. The server logs often give a clue.
Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors