Using this module for creating installation profiles with content

Seedling sounds more like what you're talking about with doing a DB dump. If you want to include nodes and bring them along I'd suggest making a feature using Features and UUID (and http://drupal.org/project/uuid_features )

There is a way to add nodes with Profiler but not really very easy. Uuid_features can work but tends to be a bit buggy.

This kind of a issue about content migration / deployment / installation / etc. is a fairly deep issue that I don't feel like Drupal has got a good solution on the table, yet.

would you be so kind to help me do the same thing? i want to copy my drupal directory and do a database dump and have that in the installation profile, please im desperate

This approach is not considered a good practice in the Drupal community. @btopro has a D6 module that does exactly what you are looking for drupal.org/project/seedling. Though no D7 version.

Depending on your skill set, you can export the content using node_export, then fairly easily reimport either manually or a simple hook during the installation.

I wrote seedling knowing it isn't a best practice. It's considered a non-bp because you are creating a sql dump specific to the db environment you were using. This could have conflicts if someone running pgsql tried to use your mysql generated profile. For personal usage though seedling is a fast way of getting things working. Seedling is an add-on to back up and migrate plus some minor code to load it up in the install profile.

Should be pretty easy to port if anyone is interested; as I build full profiles now I have no use for it but it's a unique solution.

There was a whole lively discussion awhile back when Lullabot did this "distro with db dump" practice. I don't have the reference at hand, but I recall the logic being around security, i.e. db pass security info in the open and people might fail to change passwords for example (and to a certain extent the inelegance of such a practice).

I guess obviously it depends on your situation. For an internal situation, a passed db will work. For someone looking to create a real drupal distro / installation profile, I wouldn't really trust someone using this approach.

article for reference -- http://www.lullabot.com/articles/5-step-drupal-distributions

Thanks for the vote of confidence mark ;)

I agree with that assessment though; internal usage / proof of concept to show someone else, perfect. Outside of that, potential security issue / in poor taste.

sarcasm?

In my case, the irony is that I don't really use profiler_builder anymore for building installation profiles with profiler library. I actually never did use it! It seems to do some funky things here and there. The module is a nifty little time saver for pulling out the site dependencies and a make file though :)

This issue about content migration and installation is a tough nut to crack. @btopro: I'm still waiting for you to build the skynet

If you look at the latest install profile in elms you'll see I use a technique similar to profiler builder but not it straight up, just for the dependency lists. Profiler's main issue is that it deep scans that ALL dependencies are there (which is overkill) hence profiles take A LONG TIME to process (in big installs like ours).

As for migration, this is my current solution

Feeds + http://drupal.org/project/feeds_ridmap = user migration w/ role even into groups
Feeds + http://drupal.org/project/feeds_node_helper + UUID = Content migration, also into groups if needed

ELMS bundles both of these up, content into elms_content_import and users into something that hasn't been released yet
For export, Views + Views Bonus pack which is bundled into a feature called elms_content_export

This gives us 1 click export and 1 click import as everything is kicked out to xml and relationally mapped via UUIDs. This is for portability, not retroactive updating / diff'ing of nodes into each other (at least not yet).

Interesting stuff. UUID still runs into a bunch of issues with Drupal 7, especially around entities. I had a buggy upgrade last due to issues there.

Thread has been cold for awhile, I'll accept patches for this functionality as it's kind of an edge case of building an install profile / distribution.

Going to create a lazy-load style plugin directory for the way that the info file is built out. This will allow for a definition of dependencies.inc which will have the hooks necessary to define that it's the first part of the file. It will then lazy load other .inc files in the info_plugins directory. If someone would write a way of assembling the content for export then it'll be in content.inc and be able to be included. This will make it a lot easier to add this functionality but I still won't be adding it in directly at this time.

API flexibility to add this functionality has been added to dev. This capability (exporting content) is not currently in this project but the API required to add that functionality in (basically just writing part of the file) is now in. I imagine content will be VERY specific to the site you are exporting from, plus is usually a no-no generally when spinning up a distribution / install profile.

Have you looked into http://drupal.org/project/defaultcontent . I need to check it out but this seems extremely interesting and will be VERY easy to migrate an entire site's content via the Features 2.x version's "select all" capability.

suggestion is to use another module to accomplish this though patches would be accepted to get this in given there are enough hooks for it to be possible.

Does the method in this article work with Drupal 7? http://www.lullabot.com/articles/5-step-drupal-distributions

I don't believe so though you could do something similar I guess. That is not the recommended method that's for sure.