I'm updating my site almost every day. Since I've applied the update released on 2/3/09 i get the following error:
Fatal error: Call to undefined function field_attach_load() in /home/public_html/7/modules/node/node.module on line 917
When I was logged in I had a similar error but in user.module.
I've applied all later updates but the site doesn't still come back. I've also emptied the cache tables.
Thanks for your help!

Comments

Frando’s picture

Frando commented

We support only updates from major version to major version, HEAD to HEAD updates are not supported. Empty your database and do a fresh install.

Frando’s picture

Frando commented
Priority: Critical » Normal
Status: Active » Fixed
nikemen’s picture

nikemen commented
Category: support » bug
Priority: Normal » Critical
Status: Fixed » Active
webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Category: bug » support
Priority: Critical » Normal
Status: Active » Fixed

No, Frando is right. You need to reinstall.

This is why we call Drupal 7 "unstable" :)

nikemen’s picture

nikemen commented
Category: support » bug
Priority: Normal » Critical
Status: Fixed » Active

This isn't a rebellion against Frando. I just think I've choosed the wrong category. I don't want you to fix my site and I can perfectly reinstall. Indeed my site isn't a production site but a continuous test. So, I'm collaborating with drupal by sharing the errors. I think this is why dev versions are released to the community: to test.
And I use critical cause is a fatal error that totally paralizes the installation, ok?

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Active » Closed (won't fix)

And I use critical cause is a fatal error that totally paralizes the installation, ok?

Yes, it does. For development sites running HEAD that are updating to other versions of HEAD. This is not supported. We only write upgrade paths from stable versions of Drupal. So maybe "won't fix" is the proper status for this issue.

The proper "fix" is to reinstall your development copy of HEAD.

nikemen’s picture

nikemen commented

OK, I've reinstalled. That makes you feel better? Now: could you please let me know wich is the way to let others know about a bug? Cause I used this one several times in the past and -though in almost all cases I've reinstalled- a solution was later found and that is a good thing for drupal code. Will you answer or just stay happy about reinstallation?

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Um. What's with the attitude?

Yes, the issue queue is the proper place to report bugs. What you did is fine. It's just that for this *particular* bug, it's a known issue caused by older versions of the database schema before the fields in core patch landed. Because this is Drupal 7, which is still in development, and not released yet, we are not writing upgrade paths at the present time, and therefore the fix for this bug is "reinstall." When an upgrade path is eventually written for fields in core, this issue will be fixed at that time. I'm not sure how else to explain it.

Despite the fact that we seem to have made you angry, I do appreciate you reporting bugs you find. So please keep it up.

nikemen’s picture

nikemen commented

OK then, we're clear. You just needed to say it.