Generate content scripts don't generate projects

As an experiment, I changed that line to:

  $possible_types = array("project", "project_release", "project_issue", "page");

Although releases and issues are created, no projects are (presumably because of missing data) and therefore, the test data is useless.

So looks like we'll need custom content creation functions for these types.

Teehee. It's project_project, not project. ;)

This patch extends the create_nodes() function so you can pass in an array of additional allowed types, and then passes project_* types in.

I would've assumed that I should patch generate-content.php upstream in devel module, but it no longer seems to be around. :(

Meh. While this works, it's not ideal, because all the relevant metadata info (project category, status/priority for issues, etc.) aren't there. Back to the drawing board...

dww, I moved your last comment to its own issue... http://drupal.org/node/143803 because, while important, it doesn't have specifically to do with bootstrapping project* data.

Here is a script that auto-generates a sample project in each category (other than modules -- need to figure that out some other time when it's not 1am ;)).. I broke function _drupalorg_testing_get_tid_by_term($term) { into its own function because this is the second time I've had to do that now (also in project admin settings).

$values['Drupal project'] = array (
  'title' => 'Drupal',
  'body' => 'Drupal is an open-source platform and content management system for building dynamic web sites offering a broad range of features and services including user administration, publishing workflow, discussion capabilities, news aggregation, metadata functionalities using controlled vocabularies and XML publishing for content sharing purposes. Equipped with a powerful blend of features and configurability, Drupal can support a diverse range of web projects ranging from personal weblogs to large community-driven sites.',
  'uri' => 'drupal',
);

$values['Installation profiles'] = array(
  'title' => 'Drupal.org Testing',
  'body' => 'This profile installs a site with the structure, content, permissions, etc of Drupal.org to facilitate the reproduction of bugs and testing of patches for the project modules.',
  'uri' => 'drupalorg_testing',
);

$values['Theme engines'] = array(
  'title' => 'PHPTAL theme engine',
  'body' => 'This is a theme engine for Drupal 5.x, which allows the use of templates written in the PHPTAL language. This engine does most of its work by calls to the <a href="/node/11810">PHPtemplate engine</a>, just replacing the underlying template engine with the one from phptal.sourceforge.net.',
  'uri' => 'phptal',
);

$values['Themes'] = array(
  'title' => 'Zen',
  'body' => 'Zen is the ultimate <em>starting theme</em> for Drupal 5. If you are building your own standards-compliant theme, you will find it much easier to start with Zen than to start with Garland or Bluemarine. This theme has LOTs of documentation in the form of code comments for both the PHP (template.php) and HTML (page.tpl.php, node.tpl.php).',
  'uri' => 'zen',
);

$values['Translations'] = array(
  'title' => 'Afrikaans Translation',
  'body' => "This page is the official translation of Drupal core into Afrikaans. This translation is currently available for Drupal 4.6's and Drupal 4.7's (cvs) core. Modules are being added as we progress with the translation effort.",
  'uri' => 'af',
);

// TODO: Modules...

foreach ($values as $category => $project) {
  $project['project_type'] = _drupalorg_testing_get_tid_by_term($category);
  $project['mail'] = variable_get('site_mail', 'a@a.a');
  $project['name'] = 'a'; // Assign projects to admin account.
  drupal_execute('project_project_node_form', $project, array('type' => 'project_project'));
}

function _drupalorg_testing_get_tid_by_term($term) {
  $terms = taxonomy_get_term_by_name($term);
  return $terms[0]->tid;
}

Good news! Here's a patch that auto-generates several projects when pasted into a PHP node body. WOOHOO.

Bad news! It doesn't work on install. :( The projects create, but they are not assigned any taxonomy. :( :( I have no idea how to get around this problem. On the Sony Multisite work, we did a hack in a hook_menu() of a specic install.module, but we can't upload modules to the /profile directory so I have no idea what to do. :(

dww suggested it might be because we're trying to use drupal_execute rather than node_save, so I switched the code around a bit... same result. :( Works fine when pasted into a PHP node, but category assignment fails when run at install time...

Ok. Enter the cheesy hack patch. ;)

This one does raw db manipulation to get the term associations in there. It's ugly. But it works.

I'm also changing the title to deal only with projects. This was a big enough pain in the rear, that I don't want to even try and do releases and issues on the same ticket. ;)

There was some deal with the CVS fields... I didn't have a repository to select, so it wouldn't submit the name, I think. But if possible, I'd really rather handle that in a separate "initialize CVS starer data" patch. We can amend the create scripts here in the future.

Right you are about the stale copy and the random users. So this patch adds that.

Ok, here's a re-roll that ditches the random stuff and goes with names that will be generated in the other patch (dww's working on this atm). Still CNW because I can't test it until those are done, but we agreed on these naming conventions so hopefully it should "just work" once the users patch gets in.

I went with *1 as the names rather than mixing it up too much, because I thought that way we could test a few with more than one project. I don't really have a preference though. ;)

Ok, this should be ready to go.

Committed! :) Thanks, dww.