Hi Jordan, et al:

This is the error generated by OBD:

CFML Runtime Error
Invalid Request
Request    /themachineryworks/admin2/index.cfm
File Trace    /Volumes/Durandal/jetty-openbd 
Folder/webapps/openbd/themachineryworks/admin2/index.cfm
|
+-- /Volumes/Durandal/jetty-openbd 
Folder/webapps/openbd/themachineryworks/app_globals.cfm
Type    Application
Detail    The file for the custom tag formurl2attributes could not be 
located
Missing File    formurl2attributes
Tag Context    CFINCLUDE (/Volumes/Durandal/jetty-openbd 
Folder/webapps/openbd/themachineryworks/admin2/index.cfm, Line=14, Column=1)
|
+-- CFIF (/Volumes/Durandal/jetty-openbd 
Folder/webapps/openbd/themachineryworks/app_globals.cfm, Line=33, Column=1)
    |
    +-- cf_formurl2attributes (/Volumes/Durandal/jetty-openbd 
Folder/webapps/openbd/themachineryworks/app_globals.cfm, Line=34, Column=2)
Source   
31:
32: <cfif NOT IsDefined("attributes.fuseAction")>
33:   <cf_formurl2attributes>
34: </cfif>
35:
^ Snippet from underlying CFML source

Note: app_globals.cfm is the site's Application.cfm template.
And "formula2attributes" is the custom tag

* JB *


Jordan Michaels wrote:
> Out of curiosity, what was the error that it bombed with?
>
> Warm regards,
> Jordan Michaels
> Vivio Technologies
> http://www.viviotech.net/
> Open BlueDragon Steering Committee
> Adobe Solution Provider
>
>
> J.B. Mentzer wrote:
>   
>> Hi
>>
>> I was using the /customtags/ directory with OBD 1.0. Upgraded tonite 
>> (funky changes ... can't wait to try the video tag!). Where's the 
>> correct spot for the directory? I placed it in the same relative spot as 
>> 1.0, but the site that uses server-side customtags bombed.
>>
>> Thank you!
>>
>> * JB *
>>
>> J.B. Mentzer
>>
>>
>>
>>
>>     
>
> >
>
>
>   



--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
 http://groups.google.com/group/openbd?hl=en
 official site @ http://www.openbluedragon.org/

!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to