This patch updates some UUID API calls and resolves the issue for me. Could someone please verify this code is sane?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | node_export_features-fix_uuid_issues.patch | 1.46 KB | James Andres |
This patch updates some UUID API calls and resolves the issue for me. Could someone please verify this code is sane?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | node_export_features-fix_uuid_issues.patch | 1.46 KB | James Andres |
Comments
Comment #1
James Andres commentedAnd, that didn't upload ... here's the patch.
Comment #2
danielb commentedThanks, I'll look into this soon.
Comment #3
danielb commentedActually lets figure out whether to keep uuid here at all
#1227214: Node export features improvements
More UUID problems; #1219874: Notice and PDOExeption with node_export_relation.module
Comment #4
James Andres commentedHaving a unique way to reference each object managed by the Features API is a requirement. I can't think of any other way to do it other than UUID. What do you propose?
Comment #5
danielb commentedOK I didn't know that, nevermind.
Comment #6
danielb commentedComment #7
danielb commentedcommitted to repository for 6 and 7
Comment #8
danielb commentedreverted in 6