Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Provides the ability to export content in human readable export files with the help from YAML. It's independent from any PHP module, because the module uses the symfony's YAML component. The module contains PHPUnit testing and object-oriented code.
I'm the maintainer of the Ubercart Auction module for D6.
git clone --branch 7.x-1.x jepSter@git.drupal.org:sandbox/jepSter/2312091.git yaml_content_migrate
cd yaml_content_migrateSandbox project page: https://www.drupal.org/sandbox/jepster/2312091
Comments
Comment #1
jepster_Comment #2
PA robot commentedGit clone command for the sandbox is missing in the issue summary, please add it.
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.
Comment #3
jepster_Comment #4
jepster_Comment #5
jepster_Git clone command for the sandbox added.
Comment #6
jepster_Status update.
Comment #7
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxjepSter2312091git
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #8
jepster_Hi,
I've runned the module's code trough phpcbf with the following command:
to editit for being compatible to the drupal code standards. But the big amount of code standard violations, which http://pareview.sh/ reports, is still quite the same. Also my module contains the php package manager "composer" and it's autoloader, which is mentioned by pareview.sh. Editing composer's code, is like a "corehack".
Is there any way to receive a Drupal full project, without touching composer's code? Does anybody know a command for phpcbf to edit the code in such a way, that my module's code fits in the Drupal code standards?
The amount of reported code standard violations is quite huge and I'm a bit lost now in finding a reasonable way for fixing them. Your help would be appreciated.
Thanks!
Comment #9
jepster_I've reviewed the module also with the Coder module. It brings far less mentioned problems than http://pareview.sh/ and isn't mentioning the files from composer or symfony components, which are part of this module. Just a few comment and space issues.
Which suggestions shall I follow now? Is it ok, if I just edit my .module and .inc files like coder module mentioned or shall I also "corehack" composer and the symfony components, which are mentioned as coding standard violating from http://pareview.sh/?
Thanks in advance.
Comment #10
klausiThe Libraries API module is a recommended method for adding 3rd party dependencies without directly including the code on Drupal.org. Or maybe the composer manager module in your case https://www.drupal.org/project/composer_manager
Comment #11
jepster_Thanks for your reply! Composer and the other third party code are now moved into the libraries folder. Please review.
Comment #12
jepster_* Status update *
Comment #13
PA robot commentedProject 1: https://www.drupal.org/node/2325361
Project 2: https://www.drupal.org/node/2312097
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #14
avpaderno