Hi,
Could you please release Revision 1.2.2.8 of the drupal 5 matrix module and check the compatibility patch that I've included?
Details:
The current drupal 5 release of matrix.module (Revision 1.2.2.4 2007/08/30) does not handle revisions correctly (same issue as in http://drupal.org/node/203359).
The drupal 5 Revision 1.2.2.8 of the matrix module in the CVS repository does handle revisions correctly,
however it suffers from 2 incompatibility issues:
(1) Existing matrix field instances (created with matrix.module Revision 1.2.2.4) store the field row and column labels as array elements but Revision 1.2.2.8 stores these labels as one long delimited string for the row labels and another string for the column labels.
(2) Existing matrix data in the "node_field_matrix_data" DB table (created with matrix.module Revision 1.2.2.4) are 1-indexed but Revision 1.2.2.8 expects 0-indexed data.
Converting from the old to the new data formats is not possible using some update code in the install.php file, but I've included a simple patch for Revision 1.2.2.8 that will make the matrix module automatically convert old data on the fly.
The patch allows the matrix module to use either format. Also, each time a matrix field instance in the old format is saved, it will be saved in the new format and each time a node with matrix data is saved, it will be changed from 1-indexed to 0-indexed data.
Once all matrix field instances and nodes with matrix data are saved once, the patch can be removed since all data is in the new Revision 1.2.2.8 format.
Marc
| Comment | File | Size | Author |
|---|---|---|---|
| Compatibility for Revision 1228.patch | 6.13 KB | mmcdougall |
Comments
Comment #1
mmcdougall commentedUpdate
What I wrote about the install.php file is not true:
"Converting from the old to the new data formats is not possible using some update code in the install.php file"
It can be done with PHP code and mysql, but it's not trivial.
Marc
Comment #2
intrafusion