Discussion:
book anomalies in the Drupal 6 upgrade
Gábor Hojtsy
2009-01-28 19:57:10 UTC
Permalink
Dear doc team, Gerhard, Peter and Chx,

We run into problems with the book upgrade on the Drupal.org Drupal 6
upgrade. There are these node ids, which have missing entries in the
book table for some reason, so they will not end up as nodes in the
book, and they will therefore break the chain of relationships (they
are not a child of their parents, they don't have children pages).

We run into serious upgrade problems with these nodes, and needed to
apply the attached patch to work around and let the upgrade run. One
option to fix this is to wait until the upgrade is done, and manually
fix the placement of these nodes and their children (based on data
from the current DB). The other option is to find out why there is no
such data in the DB, while the current live site shows these nodes
perfectly in the book hierarchy.

The node ids are: 82661, 101736, 101735, 92375, 62470, 62462, 62462.
They emit errors for all their children.

I think it might be best to fix it in the DB before the upgrade :)

Gábor
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/
Gábor Hojtsy
2009-01-28 20:00:20 UTC
Permalink
Ups, forgot the patch.

Gábor
Post by Gábor Hojtsy
Dear doc team, Gerhard, Peter and Chx,
We run into problems with the book upgrade on the Drupal.org Drupal 6
upgrade. There are these node ids, which have missing entries in the
book table for some reason, so they will not end up as nodes in the
book, and they will therefore break the chain of relationships (they
are not a child of their parents, they don't have children pages).
We run into serious upgrade problems with these nodes, and needed to
apply the attached patch to work around and let the upgrade run. One
option to fix this is to wait until the upgrade is done, and manually
fix the placement of these nodes and their children (based on data
from the current DB). The other option is to find out why there is no
such data in the DB, while the current live site shows these nodes
perfectly in the book hierarchy.
The node ids are: 82661, 101736, 101735, 92375, 62470, 62462, 62462.
They emit errors for all their children.
I think it might be best to fix it in the DB before the upgrade :)
Gábor
Gerhard Killesreiter
2009-01-28 23:13:57 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eeek. That is bizarre. I agree that fixing them before the upgrade is
the better path to follow. I've no ideas on what is causing this though.
No idea what causes this, but shouldn't we be able to just put the
nodes at some place in the hierarchy and then see whether that helps?

Cheers,
Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmA5rUACgkQfg6TFvELooQr6gCfdV3dS3sHwp+heGUG/yrwtHv/
mucAnjFEm9ssk3DD3H7FWVT0A/OmSl8y
=0BZj
-----END PGP SIGNATURE-----
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/
Gábor Hojtsy
2009-01-28 23:21:27 UTC
Permalink
Well, if we can do queries on these on the book table (see my patch on
what query fails, because it does not find rows). Let's see whether
that is a problem on the live DB, and if so, how can we add the
missing data.

Gábor

On Thu, Jan 29, 2009 at 12:13 AM, Gerhard Killesreiter
Post by Gerhard Killesreiter
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eeek. That is bizarre. I agree that fixing them before the upgrade is
the better path to follow. I've no ideas on what is causing this though.
No idea what causes this, but shouldn't we be able to just put the
nodes at some place in the hierarchy and then see whether that helps?
Cheers,
Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkmA5rUACgkQfg6TFvELooQr6gCfdV3dS3sHwp+heGUG/yrwtHv/
mucAnjFEm9ssk3DD3H7FWVT0A/OmSl8y
=0BZj
-----END PGP SIGNATURE-----
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/

Loading...