Installing plugins

[Mark Jones]

Thanks to the other image-related thread, I found the CF8
farcrycfimage plugin:

http://code.google.com/p/farcry-cfimage/

Hopefully this will solve some of the issues I've had with the stock
image manipulation. However, I'm having trouble getting FarCry 5.1 to
actually use the plugin. The instructions on the page above talk
about 4.0, but I think I've covered the equivilant in 5.

* Move files from download to /farcry/plugins/farcrycfimage
including /farcry/plugins/farcrycfimage/install, /farcry/plugins/
farcrycfimage/formtool, etc
* Update /Application.cfc and added farcrycfimage to:
<cfset THIS.plugins = "farcrycms,farcrygreybox,farcrycfimage" />
* Update application

I've checked spellings and run a few more updates, etc, but my image
types are still using the core formtool. What do I look at next?

[Jeff Coughlin]

Try refreshing the docs page. The instructions have been updated.

Although with the steps you mentioned, you shouldn't be having a
problem. Try editing again.

--
Jeff Coughlin
Web Application Developer
http://jeffcoughlin.com

[Mark Jones]

> Try refreshing the docs page.  The instructions have been updated.

I saw that. I should have just waited 5 more minutes :)

I'm still seeing the old behavior. Is there a way to see what plugins
FarCry is *currently* aware of? I've had no luck getting the scope
dump tool to work, so I haven't tried that yet.

[modius]

Does anyone get the "scope dump" tool to work? Am trying to work out
if its something that broke in 5+ or something that broke remoting in
cf8.

You can tell what FarCry has registered as plugins by dumping
#application.plugins# and #application.stplugins# -- unfortunately its
not really going to tell you whether or not your plugin loaded
successfully. Where is the "plugin explorer" when you need it?

Make sure that you have a plugins folder that is directly underneath
the root /farcry folder, ie. /farcry/plugins. Then check that your
plugin is simply ./plugins/pluginname and the unpacking of the zip
hasn't accidentally added another intermediary folder, eg. ./plugins/
myplugin/myplugin.

Last but not least.. you could simply grab Jeff's image.cfc and place
it in your project directly under ./projectname/packages/formtools/
image.cfc (the plugin is essentially just a single component).

-- geoff
http://www.daemon.com.au/

(Plugin Explorer TM coming soon)

[Jeff Coughlin]

> (Plugin Explorer TM coming soon)

"Wishin', and hopin', and thinkin', and prayin'"

It would definitely be nice, but I'm not holding breath just yet :)

[Mark Jones]

> You can tell what FarCry has registered as plugins by dumping
> #application.plugins# and #application.stplugins#

I figured something like that existed. I tried dumping application
itself, but got the java heap-size error I was expecting.

> unfortunately its not really going to tell you whether or not your plugin loaded successfully.

Aw, nuts. Possibly unrelated, but what is supposed to be in
stPlugins? Mine's empty.

> Last but not least.. you could simply grab Jeff's image.cfc and place
> it in your project directly under ./projectname/packages/formtools/
> image.cfc (the plugin is essentially just a single component).

That makes a lot of sense. ...and, now that you say that, I think I
know exactly what's wrong.

You know, I usually hold back from using forums like this because
almost invariably problems like this end up being my own damn fault
and I feel like a fool. This is one of those times. It turns out the
formtool I was testing the image upload routine against was the one I
had created myself, which extended
farcry.core.packages.formtools.image directly... so of course it won't
get the behavior of the plugin version.

I changed that to extend the plugin, reloaded the app, and everything
works as expected. Thanks for knocking my brain onto the inheritance
track.

[modius]

On Feb 26, 1:23 pm, Mark Jones <markevanjo...@gmail.com> wrote:
> > You can tell what FarCry has registered as plugins by dumping
> > #application.plugins# and #application.stplugins#
>
> I figured something like that existed.  I tried dumping application
> itself, but got the java heap-size error I was expecting.

Hah! FarCry application scope is getting a bit large. We want to
refactor things and move everything into the private scope of a few
components -- sigh, one day.

> > unfortunately its not really going to tell you whether or not your plugin loaded successfully.
>
> Aw, nuts.  Possibly unrelated, but what is supposed to be in
> stPlugins?  Mine's empty.

This is where plugin developers can store information if they need to;
stplugin["pluginname"]. Some plugins use it, many don't.

> > Last but not least.. you could simply grab Jeff's image.cfc and place
> > it in your project directly under ./projectname/packages/formtools/
> > image.cfc (the plugin is essentially just a single component).
>
> That makes a lot of sense.   ...and, now that you say that, I think I
> know exactly what's wrong.
>
> You know, I usually hold back from using forums like this because
> almost invariably problems like this end up being my own damn fault
> and I feel like a fool.  This is one of those times.  It turns out the
> formtool I was testing the image upload routine against was the one I
> had created myself, which extended
> farcry.core.packages.formtools.image directly... so of course it won't
> get the behavior of the plugin version.
>
> I changed that to extend the plugin, reloaded the app, and everything
> works as expected.  Thanks for knocking my brain onto the inheritance
> track.

Great to hear you're playing with the whole extension caper! We've
tried to make this an aspect of all componentry. My favourite
inheritance wizardry is in the way in which Views are managed. One of
these days someone will right a little piece on just why its so
marvellous ;)

All the best,

-- geoff
http://www.daemon.com.au/

[Marco van den Oever]

Yes i am using the scope dump tool, FC 5.1, CF 8 locally on pc.

> -- geoffhttp://www.daemon.com.au/