This is not an easy module to set up due to the reliance on other modules - Some clear instructions are needed.
Here's the steps I found were needed to set up coder:
* Download the latest dev versions of the projects coder, libraries, grammer_parser_library and untar them in sites/all/modules (or equivalent).
* Download the latest dev version of grammer_parser and untar it in sites/all/libraries (or equivalent).
* Go to the modules page and enable the three modules in the coder section and the modules libraries and grammer_parser_library.
You're done!
NB - Don't worry about the 'Drush make' line. To me that instruction looks like it is in the grammer_parser_library as a tool to pull down the correct versions of the libraries and grammer_parser modules. I certainly never ran the command and coder works fine.
And an overview of how coder works is basically:
* Go to admin/config/development/coder
Here you will see two tabs - Review and Upgrade.
Review
The Review tab section is for reviewing modules which are in sites/all/modules (or equivalent). NB - This includes reviews of what needs to be changed to convert your code from one Drupal version to another if you tick the relevant box.
Upgrade
This errors on my current copy - but the idea is that this can go through a module which is in /sites/default/files/coder_review/old or in sites/all/modules and actually convert the code. This should produce a new version of the module and the diff file to convert the old module if that is preferred.
Comments
Comment #1
douggreen commentedYour instructions here are mostly for Coder Upgrade, which you say doesn't work and I haven't looked at coder upgrade in 7.x-2.x yet (that was developed by @ solotandem. The libraries and grammer parser are only needed for Coder Upgrade.
The instructions for coder review are ... well, nothing special really. Just download the module. Put it in your modules directory and enable. If you are a d.o. admin and you only want to use drush coder-review, then put it in your ~/.drush directory. Otherwise, currently, the best solution is to put it in your modules directory.
However, the one instruction you are missing, that I do think is kinda important, is that coder review now integrates with Drupal Code Sniffer. So that's a good project to download to your ~/.drush directory. Even if you don't use drush, please put it there. Then follow the instructions on that project on getting PHP_CodeSniffer setup.
Eventually, I hope we'll streamline the integration of DCS and give you a make command.
Comment #2
bailey86 commentedOK - point taken.
As coder upgrade is a part of this module I thought it was worth helping out to be able to get the full functionality running.
BTW - there is a good online tool for checking code at: http://ventral.org/pareview - and this is part of the docs at: http://drupal.org/node/1587704
Comment #3
douggreen commentedThanks for starting this documentation for others. I think it's time to expand the coder handbook on d.o. to include user level docs, and not just coder programmer docs. Currently we have http://drupal.org/node/144172. I may take a stab at starting the outline. And if you are interested, that would be a good place to talk about the installation.
Also, as we work towards a 7.x-2.x release (and an 8.x release), I'd appreciate feedback on making the installation easier, including for coder upgrade.
Comment #4
bailey86 commentedI'll be glad to help.
And as I'm using coder to upgrade my data_export_import module - http://drupal.org/node/1330454 - I'll supply feedback during the upgrade process.
Cheers,
Kevin
Comment #5
klausiCoder 7.x is frozen now and will not receive updates. Coder 8.x-2.x can be used to check code for any Drupal version, Coder 8.x-2.x also supports the phpcbf command to automatically fix conding standard errors. Please check if this issue is still relevant and reopen against that version if necessary.