Skip to main content
August 26, 2007
Question

CFCs Not Recognized by Dreamweaver 8

  • August 26, 2007
  • 1 reply
  • 352 views
Am using Dreamweaver 8 and CF MX 7. All the CFCs I've created were created manually, not using Dreamweaver. I then copy the CFC, and modify it as needed for other applications in different folders. But all apps are part of the same SITE. By the way, the main site is in a virtual folder on my developement PC, same as the production server.

However, when I click IN and OUT of a template that contains a CFINVOKE to a CFC, I get a quick pop-up message that says:
"The required component could not be found at the specified location." I just click OK, the message goes away. The programs, templates and CFCs work fine. I probably have a dozen report forms that INVOKE a CFC (all part of the same site) but I did not create any of the CFCs in Dreamweaver, just coded them manually.

Is there some way to get rid of this repeating message? Or is this normal when you DON'T create the CFC with Dreamweaver? When I click on APPLICATIONS/COMPONENTS, it tells me "THERE ARE NO CFCs DEFINED IN THE CURRENT SITE." But they are there, and I'm using them.

I'd like to (but not totally necessary) inspect/modify the CFCs in Dreamweaver. But it tells me the first thing I need to do is "CREATE A SITE FOR THIS FILE", followed by the other 3 instructions related to DOCUMENT TYPE, TESTING SERVER, and RDS LOGIN.

I've already created the site in Dreamweaver. So I guess the question is: "HOW DO YOU -ADD- A CFC, SO YOU CAN WORK WITH IT IN DREAMWEAVER, WHEN YOU'VE ALREADY CREATED THE SITE? Every time I experiment, Dreamweaver seems to always want me to create a SITE. But my application has been using the same "site" for 5 years, it's already created. So not sure what is wrong.

Would appreciate any advice on either how to get rid of the repeating error messages, or how to get Dreamweaver to recognize a "manually-created" CFC when you've already created the site. Any advice would be greatly appreciated. Thank you.

Gary
This topic has been closed for replies.

1 reply

chucknado
Participating Frequently
August 27, 2007
I'm not sure, but it might have something to to with your testing server settings. In certain cases, Dreamweaver looks for the components on your testing server, not your local site. For more info, see http://livedocs.adobe.com/en_US/Dreamweaver/9.0/WScbb6b82af5544594822510a94ae8d65-7871.html.

Charles Nadeau
Dreamweaver
Adobe Systems