[DUG-TO] Help finding lost page after error: field 'body' doesn't have a default value
Philip Kiff
pkiff at iwh.on.ca
Tue May 19 13:19:40 EDT 2009
Toronto Drupal folks,
Wondering if anyone might be able to help me with this.
Running Drupal 6.10 on IIS 7. During a standard page edit, I received the
following PHP error (replaced elements indicated by [--]):
Field 'body'; doesn't have a default value query: INSERT INTO node_revisions
(nid, uid, title, teaser, log, timestamp, format) VALUES (644, 4,
'[--correct title of page appears here--]';, '', 'Added PDF of full paper.',
1242321716, 0) in [--correct path to includes appears here--]\common.inc on
line 3422.
And now the page does not show up in Drupal at all: the path alias returns a
page-not-found and so does the actual node where that the page originates
from.
In the MySQL db, I can find the node in the "node" table, and under nid it
shows 644 (the correct node) but under vid it shows 0 instead of a number,
whereas all the others I see have a number showing for vid. I've no idea
what that means or whether there is a way for me to fiddle with this or any
other table directly to bring the page back again.
Can I recover the lost page somehow and make it show up again via the
regular Drupal editing interface (published or not)?
I'm using the diff module, and I thought perhaps I could pull data out of
that somehow if necessary, but I wouldn't know where to go to find a copy of
the previous body text. And the specific edit that resulted in the error
does not show up in the "node_revisions" table. Currently when I try to pull
up the node or page alias all I get is a page not found so I can't revert
whatever changes were made. Not all my modules are up-to-date, but the diff
module is at 6.x-2.0.
I posted this question over on the Drupal.org forums, but got no reply:
error on edit - field body doesn't have a default value - find lost page
again?
http://drupal.org/node/462804
I am a little bit concerned that maybe the error is a sign of some
incompatibility or database corruption that I am otherwise unaware of. I'm
planning on upgrading up to 6.12 later today or tomorrow.
Any ideas?
This e-mail may contain confidential information for the sole use of the intended recipient.
Any review or distribution by anyone other than the person for whom it was originally intended is prohibited.
If you have received this e-mail in error please delete all copies.
Opinions conclusions or other information contained in this e-mail may not be that of the organization.
More information about the DUG-TO
mailing list