Nowhere is it indicated that coder upgrade does not work in the beta release and that you have to use the dev version.
I wasted half a day trying to find what I was doing wrong. It is incredibly misleading because there is an option to generate drupal 7 code.

Please put info about this in the README.txt and on the projects page.

Comments

solotandem’s picture

solotandem commented

My apology to you for the inconvenience. For future reference, your issue title and summary are a bit all inclusive in their claims but lacking in detail. Looking at the commit history, there has only been one "bug fix" since the beta6 release. This fixed a logic error that displayed the message "no upgrade routines have been run" when in fact they had. This error only occurred with certain settings enabled.

The module does output code that conforms to the Drupal 7 APIs. What exactly did (or did not) happen when you used the beta6 release? Were you able to get output from the dev release? What OS are u running?

We should be releasing a new version in the near future. I agree this module is one that should recommend using the dev release.

diricia’s picture

diricia commented

I would put the module to upgrade in the old/ directory, choose, upgrade from 6.x to 7.x. The module that would be generated in the new/ directory would be exactly a copy of the old drupal 6 version.

I did this many times, I certainly chose the correct settings.

solotandem’s picture

solotandem commented

Would you be able to indicate a public module that you tried which came out unchanged? Or, would you send me (from my contact page) a private module that you tried?

NROTC_Webmaster’s picture

NROTC_Webmaster commented

Is there a way to configure where the coder puts the upgrade files? It is defaulting to where my backups are but I would like to change this. The module works great for identifying code that needs to be upgraded but that automatic file generation seems to be failing and I believe it is because it is trying to write to a private directory.

solotandem’s picture

solotandem commented

Let's be serious, you're private files directory is sites/default/files/coder_upgrade/new?

There is a setting for where the old and new directory is for this module. The default is, of course, beneath sites/default/files/coder_upgrade.

Also, please use the dev release of this module.

solotandem’s picture

solotandem commented
Status: Active » Fixed

Closing as this is no longer an issue in newer releases.

Status: Fixed » Closed (fixed)

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