The Contentout module creates CSV files from Drupal nodes. It uses a
hierarchical structure in the CSV file to preserve node hierarchy. For defaults,
Field/subfield columns are separated by three underscores and muti-value fields
are separated by two underscores. The default delimiter is a comma.

Date fields are exported in DateTime format (i.e. not Unixtime) for easier
migration into Drupal.

https://www.drupal.org/sandbox/iribarne/2461613

git clone --branch 7.x-1.x http://git.drupal.org/sandbox/iribarne/2461613.git contentout

CommentFileSizeAuthor
Contentout.png56.94 KBiribarne

Comments

iribarne created an issue. See original summary.

PA robot’s picture

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

pankajsachdeva’s picture

Automated Review

Found issues in pareview.sh. Follow link: http://pareview.sh/pareview/httpgitdrupalorgsandboxiribarne2461613git

Manual Review

Individual user account
[Yes: Follows] the guidelines for individual user accounts.
No duplication
[No: cause] module duplication and/or fragmentation.

Can you specify that how your module is different from Node Export

Master Branch
[Yes: Follows] the guidelines for master branch.
Licensing
[Yes: Follows] the licensing requirements.
3rd party assets/code
[Yes: Follows] the guidelines for 3rd party assets/code.
README.txt/README.md
[Yes: Follows] the guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
[Yes: Follows] the guidelines for project length and complexity.
Secure code
[Yes: Meets the security requirements.
Coding style & Drupal API usage
Few suggestions:
  1. Provide a configure path in .info file: 'admin/config/content/contentout'
  2. Implement hook_help() in your module.
  3.  $items['admin/config/content'] = array(
        'title' => 'Content authoring',
        'page callback' => 'contentout_intro',
        'weight' => 33,
        'access callback' => TRUE,
        'expanded' => TRUE,
      );
      $items['admin/config/content/contentout'] = array(
        'access arguments' => array('administer contentout configuration'),
        'page callback' => 'drupal_get_form',
        'weight' => 35,
        'page arguments' => array('contentout_readwrite'),
        'title' => 'Content out',
        'description' => 'Configure the settings for Contentout.',
      );

    Provide proper 'access callback' so that the config form can be only accessible by the admin. This cause a security velnerbility. So please update.

This review uses the Project Application Review Template.

pankajsachdeva’s picture

Status: Needs review » Needs work

Thanks for your contributions.I would suggest you to take a review bonus to speed up the process. Please help reviewing and put yourself on the high priority list.

klausi’s picture

Status: Needs work » Needs review

Duplication and the minor issues you found are not application blockers, anything else or should this be RTBC instead?

pankajsachdeva’s picture

Hi @klausi,

I didn't find any major blocker issue. And this module works fine.

We should move it RTBC.

pankajsachdeva’s picture

Status: Needs review » Reviewed & tested by the community
iribarne’s picture

I added the default branch.

As per how this module differs from the Node Export module, The Contentout module creates a CSV file preserving the node hierarchy: Fields/subfields in header row, and multi-value fields in the content cells. The hierarchy of the node is preserved so it can be easily imported using the migrate module. Examples of this were presented at DrupalCamp Atlanta last October (video: http://drupalcampatlanta.com/2015-drupalcamp-atlanta/sessions/no-code-co...), and Florida DrupalCamp (Slides: https://www.fldrupal.camp/sessions/approved/florida-drupalcamp-2016/deve...) this past weekend.

I still have some work to do on the contentout_session_streams.inc file (I already implemented the code sniffer recommendations for the contentiout.module and contentiout.info files). When I started implementing the function name changes suggested by code sniffer in the contentout_session_streams.inc file, it broke the functionality of the module. I have to investigate further before implementing the code sniffer changes suggested for the contentout_session_streams.inc file.

I will keep looking at the recommendation provided in the comments to improve this module. This is my first experience in requesting full project status for a module and I appreciate the prompt and detailed feedback form everyone.

Thank you all!

pankajsachdeva’s picture

Thanks for your contributions.I would suggest you to take a review bonus to speed up the process. Please help reviewing and put yourself on the high priority list, then Git Admins will take a look at your project right away :-)

damienmckenna’s picture

Status: Reviewed & tested by the community » Fixed

Thanks for your contribution, Hector!

I updated your account so you can 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:

You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!

Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

Thanks to the dedicated reviewer(s) as well.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.