Blockexport

This module export all the blocks? or only selected blocks?

Good idea!

You have listed some reviews in your issue summary, but you did not do any manual reviews? Please read through the source code of other projects and report any issues that you find. And don't forget to add the review bonus tag if you did some actual manual reviews as outlined in #1410826: [META] Review bonus.

Hi @drupwash,

This is a great module, very handy! I was able to export all of the blocks from a test site and to import them back into the site. Everything is working correctly.

These are my suggestions for improving it:
1. Add a better description to the block_export.info. For instance:
description: Allows exporting of all blocks as a feature.

2. Add a requirements section to the README.txt for the requirements: Features and Chaos Tools.

3. Add to README.txt that you should check "Block: Export All Blocks" when creating the feature.

4. Add a couple screen shots to the project page. (Creating features can be confusing to end users so a screen shot could help illustrate instructions.) I've attached a picture of the create features page.

Thanks,
Bart

I changed the status back to "needs review", because the module works as intended but could just use a couple of documentation fixes. These minor things shouldn't block others from reviewing the module.

Thanks,
Bart

I have gone through the code base it actually works on entire block tables.
As far codes it seems to me very handy module but have one suggestion,
In the blockexport_settings_features_export_render function there are multiple quires to take the all block configuration.
Mostly common queries excepts those table & schema name so please make a class in .inc file
& put the logic in parameterised static function,

$results = db_query("SELECT * FROM ".$schema_name);
foreach ($results as $result) {
$data = array();
$schema = drupal_get_schema($schema_name);
$fields = array_keys($schema['fields']);
foreach ($fields as $field) {
$data[$field] = $result->$field;
}
$code[] = " \$export['$schema_name'][] = " . features_var_export($data) . ";";
}

load the module in info file & then call the function in module like,
Blockexport::methodname('schemaname');

Repository added

Only reviewers should assign issues to themselves.

There is still a master branch, make sure to set the correct default branch: http://drupal.org/node/1659588 . Then remove the master branch, see also step 6 and 7 in http://drupal.org/node/1127732

manual review:

1. blockexport_settings_features_revert(): you can insert multiple records at once, see Multi-insert form on http://drupal.org/node/310079 then you don't need the loops.
2. Did you try that module on a large drupal installation with many blocks? I could imagine that there might be scalability issues if there are a lot of block configurations.

Anyway, I find the idea to just dump whole database tables into Features export code kind of creative :-) . Looks RTBC to me. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.

Thanks for your contribution, drupwash!

I updated your account to let you promote this to a full project and also create new projects as either a sandbox or a "full" project.

Here are some recommended readings to help with excellent maintainership:

• Dries' post on Responsible maintainers
• Best practices for creating and maintaining projects
• Maintaining a drupal.org project with Git
• Commit messages - providing history and credit
• Release naming conventions.
• Helping maintainers in the issue queues

You can find lots more contributors chatting on irc in #drupal-contribute. So, come hang out and stay involved! Thanks again, and good luck! :)

See http://drupal.org/node/1068944

everyone gets this at the moment, probably site-maintenance.