How your cf is set up does little to effect how the javascript will communicate with other forms. JS will traverse your page in the usual way. The fact that one form is in a different file than another form doesn't matter to JS since by the time it gets to the client browser it's all "one page" as it were.
How are you trying to get JS to target the forms now? What code is failing? On Fri, Dec 31, 2010 at 1:06 PM, Eric Roberts < ow...@threeravensconsulting.com> wrote: > > I have been running into an issue with not being able to read across forms > on a site I am working on. The site is set up so that instead of using > cfinclude, they address pages as custom tags (ie header.cfm is called as > <cf_header url_val="xx">. The basic setup is there is an index.cfm that > acts like a driver page that calls the "tags" and the called pages may also > call "tags" as well. We have a dropdown to select with all of the > properties or an individual property (Hotel properties). We are adding the > ability for the hotels, if they take this into account, count the number of > infants. This form field (itself a dropdown) is in a different form that > is > physically located in a different file (which is the parent page that is > calling the file that the above dropdown live on). In the rendered html > and > javascript, the property section comes before the form that has the number > of infants. What I am trying to accomplish is that when I change the hotel > property, I want it to check against a session var that determines whether > or not that property does an infant count and check a hidden form field to > see if the value of infants is greater than 0. The problem I am having is > that the hidden field that I have in the form isn't showing up. Does this > have something to do with the fact that pages are being used as custom > tags? > I have never seen a site structured like this.it's pretty unique and not a > bad idea, but I am wondering what effects on how variables are available to > other tags/pages this structure has. > > > > Here's the basic structure: > > > > Index.cfm calls call_index.cfm as <cf_call_index.cfm>..call_index.cfm calls > call_index2.cfm as <cf_call_index2>. Form 1 with the property dropdown > physically resides on call_index2.cfm and form 2 that has the infant count > dropdown physically resides on call_index.cfm. > > > > > > Anyone have an experience dealing with this kind of structure? > > > > Eric > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:340338 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
