installation fails

[okjim3GH]

I am just starting out with cfwheels and tying to follow along with Chris Peters' CFWheels DBMigrate Create Operations video on Vimeo. (https://vimeo.com/channels/cfwheels/40902756) I got the default app installed no problem. Then I downloaded the dbmigrate plugin and placed it in the plugins directory and restarted the app. I got this error:

Could not find the ColdFusion component or interface migration-demo.plugins.cfwheels.cfwheels.
Ensure that the name is correct and that the component or interface exists.
The error occurred in /Users/jokeefe/Sites/migration-demo/wheels/Plugins.cfc: line 129

The initial zip file "cfwheels-dbmigrate-plugin-master.zip" is still in the plugins directory, but a cfwheels directory has been created and inside that a cfwheels-dbmigrate-plugin-master directory with all the juicy plugin bits inside. I suspect that the path with cfwheels in it twice was composed and that the two parts are not aligned. Would anyone have an idea what is going on here? (cf11,OSX,cfwheels 1.4.2, dbmigrate? latest version)

[tdm00]

Use the latest version from the cfwheels plugin page, not the download ZIP here.

On Oct 2, 2015, at 10:41 AM, okjim3GH notifications@github.com wrote:

I am just starting out with cfwheels and tying to follow along with Chris Peters' CFWheels DBMigrate Create Operations video on Vimeo. (https://vimeo.com/channels/cfwheels/40902756) I got the default app installed no problem. Then I downloaded the dbmigrate plugin and placed it in the plugins directory and restarted the app. I got this error:

Could not find the ColdFusion component or interface migration-demo.plugins.cfwheels.cfwheels.
Ensure that the name is correct and that the component or interface exists.
The error occurred in /Users/jokeefe/Sites/migration-demo/wheels/Plugins.cfc: line 129

The initial zip file "cfwheels-dbmigrate-plugin-master.zip" is still in the plugins directory, but a cfwheels directory has been created and inside that a cfwheels-dbmigrate-plugin-master directory with all the juicy plugin bits inside. I suspect that the path with cfwheels in it twice was composed and that the two parts are not aligned. Would anyone have an idea what is going on here? (cf11,OSX,cfwheels 1.4.2, dbmigrate? latest version)

—
Reply to this email directly or view it on GitHub.

[okjim3GH]

Unless I'm missing something, the cfwheels plugin page links here and doesn't have a separate version.

[tdm00]

@okjim3GH I'm sorry for the delay. I've moved on to a different role within my organization and so I no longer have the joy of working with CFWheels any longer. It seems that during my time away the ecosystem has changed slightly on how to install these plugins. In the past you would download the ZIP file from the cfwheels.org website and drop it into your /plugins directory. It seems that is no longer the case.

I've updated this projects README file with two possible installation methods. I hope that gets you up and running with this plugin.

[okjim3GH]

Troy, thanks for all you've done for the community. After some fumbling I figured out what had to be where and got things working. It's a shame that the original simplicity of grab the zip file and drop it in the plugins directory has been lost, but since everything runs on github now it makes sense to host plugins there as well. Cloning from github seems pretty close to that in terms of convenience.

[geirman]

Since you figured it out, maybe you could document it here for anyone who
has the same issue and stumbles upon this thread

On Tue, Oct 6, 2015 at 7:15 AM, okjim3GH notifications@github.com wrote:

Troy, thanks for all you've done for the community. After some fumbling I
figured out what had to be where and got things working. It's a shame that
the original simplicity of grab the zip file and drop it in the plugins
directory has been lost, but since everything runs on github now it makes
sense to host plugins there as well. Cloning from github seems pretty close
to that in terms of convenience.

—
Reply to this email directly or view it on GitHub
#84 (comment)
.

[okjim3GH]

Basically I put the zip file I got from github in the plugins directory and let cfwheels do it's thing. Cfwheels creates a directory for the plugin (by what mechanism I'm unclear) and then puts the unzipped folder of the plugin into that. This results in a directory structure that is too deep. I copied the contents of the unzipped directory one level up into the root of the directory that cfwheels created for the plugin.Once you do that the plugin works. You could clean up and delete the unzipped folder as it is now redundant. tdm00 says it differently in the README file on github so you might want to read that, as he has countless hours working with cfwheels and I am just starting.

[chrisdpeters]

The easiest way to document this would be to point people to the "releases" tab of the GitHub repo. Each release includes the proper zip file to use.

The core team is currently working out how to have a good package directory for CFWheels again, so hopefully we can help sort this out in the near future.