This is what I call "fixtures". Yes, still vapour, but it wil be there, as part of sympal scripts. Op vrijdag 9 juni 2006 15:37, schreef Barry Jaspan:
I do (a), but it is annoying and error prone. If someone has a better system, I'd love to hear it.
I try to extract, one by one all content that is considered part of a "configuration". This can potentially be users, and nodes too. As well as categories etc. These are then dumped into PHP files, as PHP. nodes.fixture $node->title = 'My Cool Frontpage'; $node->body = 'This is printed on my frontpage node'; $node->name = 'Site Administrator'; $nodes[] = $node; .... users.fixture $user->name = 'Site Administrator'; etc note that we do not have stufff like Dates, uids and even nids. This is what makes fixtures far better then SQL dumps. A SQL dump is so much intertwined that it is near impossible to select only one or two tables and not all the others. Nodes need users; users need roles. Nodes need terms; terms need a whole range of tables. Nodes need revisions. Users need counters. Nodes need counters; etc etc etc. I guess you can go on untill you have.... A full SQL dump ;) Now, still vapourware, in that matter, that I really want to find a central way to halde all tis, but Drupal is very incosistent. So the result is that I need to develop a wrapper around all 'objects' (users, terms, nodes etc) S that my fixtures are consistent and unified, while the backend (Drupal) can remain inconsistent. Bèr -- PGP ber@webschuur.com http://www.webschuur.com/sites/webschuur.com/files/ber_webschuur.asc Drupal upgrade repareert kritiek beveiligingslek: http://help.sympal.nl/drupal_upgrade_repareert_kritiek_beveiligingslek