I have a website upgraded to 7.7 that for some reason is now displaying error messages at the bottom of the screen.
On my development site, the message is:
Fatal error: Cannot access empty property in \modules\field\field.multilingual.inc on line 275.
I have found a few posts that are way over my head and seem to consist largely of an ongoing argument about how serious this problem may be but do not hint at what a solution is. They do seem to agree that it is a problem in core.
Two interesting facts that may be helpful. 1) It seems to be a benign condition as it causes no problems in the admin tasks, except when attempting to manually check for upgrades. Then this message occurs:
Error checking available update data.
Please continue to the error page
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?id=126&op=do StatusText: OK ResponseText: {"status":true,"percentage":"3","message":"Trying to check available update data ...\u003cbr \/\u003eChecked available update data for \u003cem class=\"placeholder\"\u003eSEO Checklist\u003c\/em\u003e."} Fatal error: Cannot access empty property in modules\field\field.multilingual.inc on line 275
And 2) The message at the bottom of the pages only appears if a user is logged in.
Also, I did delete all files in the drupal 7.7 installation except for the sites folder, and replaced with fresh copies.
I'm really lost. I love Drupal, but to keep a site online that has this error message on the bottom of every page is like telling the world I'm a doofus and the company is not so swift. Bad marketing communications.
Anyone have any ideas. It's obviously a widespread problem as when I google it many pages come up for sites with this same error message inscribed at the bottom when google last crawled the page.
Thank you for you attention.
Comments
[Solved] sql database backup helped
After replacing the Drupal 7.7 files with fresh versions of 7.4 and 7.2 and then 7.7 again with no positive result, it dawned on me that the problem was embedded in the database.
I did use the built in capabilities of PHPMYADMIN to check and repair all the tables, but that did not fix the problem.
The solution consisted of importing a two-week old sql backup of the database. More recent backups produced the same error messages. So, some mysterious database corrupting event apparently occurred approximately two weeks earlier and was contained in all subsequent backups.
I then brought the newly restored database up to date with the latest content by exporting the following tables from the corrupted database and importing them one at a time to the newly restored version and testing to see if each new import would bring back the problem.
Very luckily, it did not. These are the few tables that I dared to restore: node, node-revision, page-title, field-data-body, and field -revision-body. At that point the restored database was still not producing the error and I had most of my data back and I considered myself a lucky guy.
Not sure if this was the optimal way to solve this problem. Any comments would be welcome.
Thanks.
I can confirm, that I have
I can confirm, that I have this problem too.
I've updated my site to D7 and now I can't run cron because of this error. I don't know what to search in my DB to fix it.
Fatal Error: modules\field\field.multilingual.inc on line 275
Hi Teri,
I searched by Google and within these forums and found nothing that actually helped solve the problem. As I said above, the only way I got rid of it was to restore an earlier backup of the DB.
You may get lucky searching the system table and making sure that the paths listed to the modules are correct. Make sure you backup your database, or at least that table, beforehand.
Good Luck!!!
Dave M
Thank you Dave! I've analyzed
Thank you Dave!
I've analyzed my Node and Node Revisions tables, but now you give me little hope, that I can find the problem in System table. Thanks!
same problem
I have the same problem but could not solve yet.
Anyone found the solution, please kindly advise.