Demo Data

This install profile currently does create dummy data. Please reopen if you aren't getting dummy contacts when running the install profile.

I had the same issue. I tried 3 times on 2 different servers (local Win7 / Xampp and remote Debian Squeeze).

The final install step "RedHen Demo Post Install Tasks" remained ghosted out. Once it got to the second-last step "Finished" the only option was to "visit your new site" where I was presented with the message "The content access permissions need to be rebuilt. Rebuild permissions."

See attached screenshot.

After rebuilding permissions, there's no demo data.

Is there any way I can trigger demo data installation manually?

I should add that I've had no trouble with demo data installation in other distributions (e.g. aGov, Commerce Kickstart, Commons) on the same server.

A plus one for this issue- I have exactly the same problem.

Same issue for me.

If you want to play with the demo site before this issue is fixed, a workaround is to trigger the post-installation setup manually.

1. Go to profiles/redhen_demo/redhen_demo.install
2. Around line 25, replace function redhen_demo_post_install(&$install_state) { with function redhen_demo_post_install() {
3. In the terminal, enter the following drush command: drush eval "include_once 'profiles/redhen_demo/redhen_demo.install'; redhen_demo_post_install()"

The site should now have switched theme and have a bunch of demo data.

Please feel free to submit a patch.

@torrance123 (#5):
Thank you, your tipp works with version = "7.x-1.0-alpha3+0-dev".

Wusel

No permissions of the roles are imported.

Wusel

No permissions or roles are defined in the install profile.

This is intended to be a very simple demo install profile. It doesn't do much out of the box. We'd encourage you to play and consider developing your own RedHen distros to share on D.O.

As already noted before, the problem is that the extra install task that is added by the install profile is added at the end of the task array in the alter hook. This means it is never executed, because the finish task is the last step Drupal gets to, naturally (technically, I suspect this is simply because that task does not provide a "Next" button).

Attached is a patch that changes the alter hook somewhat, so that the finish step is first taken off, the custom task that installs the demo content is inserted, and then the finish task is added back on.

BTW, I've set this to "bug report" (because this *is* a bug, #5 is a workaround, not a solution) and to "major" because the whole point of this installation profile is to provide a demo site. Failing to actually install the demo content, in that case, seems pretty major to me :)

BTW, it's worth noting that after making this change and getting the task to execute, I got a bunch of notices, which would probably warrant an issue in their own right. However, there didn't seems to be any major problems with the generated content, at first glance.

Patch applied at commit #7956a35. Fixed index errors at the same time.

It would be great if we could get some community testing and then we can roll a new stable release.

Thanks everyone, especially eelkeblok.

-s

Eelkeblok, I'm so sorry. Somehow I copy/pasted the wrong committer email address into my commit log for your patch, so you didn't get attribution. Unfortunately, there's no way to change a commit on D.O.

I really appreciate your patch. Thank you for taking the time to submit it.

It's generally a bad idea to change pushed commits anyway, so no sweat. By the way, you may want to look at the commit message guidelines: http://drupal.org/node/52287. I do believe that a commit is also attributed to a user when they are mentioned this way as well.