Project: Update Drop-Down Warning Message

Start Date: October 29, 2010

11/4/10-

Find the SQL query for the location ()hopefully in a cfc), look for that cfc name in xhr.js. Hopefully that is the AJAX call

11/1/10-
Notes from George: 
The address location field sends out a JSON service to get the listing data.
The MLS field adds the number to a new URL and goes there. If you want the drop-down to act just like the other one, then you have to invoke a service for the MLS numbers too
11/1/10-
Location:
  1. Type in a specific address and you get the detail page of that result. The map is somewhat zoomed into that result. The map extents create additional results which are displayed on the map and on the Listings tab.
  2. Type in a general address and the map zooms to that area and shows all results within the extents. Listings tab is shown. Detail tab has no specific result.
  3. Type in a very general address and you might get the drop-down asking you to choose something more specific. Results of the click act like #2.
MLS:
  1. Type in an MLS that has only one result and you get the Listings tab. The map shows the one result with the map zoomed out.
  2. Type in an MLS that returns multiple and you get the Listings tab. The map shows the one result with the map zoomed out. Detail tab has no specific result.
10/29/10-

When you click the search button on the home page (dspHomePageMessage.cfm), it fires off triggerSearch(document.hp_search_form).
Which is in (/js/refresh/front_page.js) and then fires off either LOCATION_GATEWAY.findLocation or LOCATION_GATEWAY.targetMls
LOCATION_GATEWAY is defined in /Views/vGeography/dspInteractiveMapControlLocationSearch.cfm

Made a change to /js/refresh/front_page.js
Put on second line: "Please try your search again."
Changed "[Cancel]" to "Close"
Changed "state name below" to "state map"
Changed "change the Search By menu" to "use the Search by MLS field."

To get the scripts to point to the local file that I can update:
/root/CustomTags/resource/srcScripts.cfm
I commented out the cf path attribute
<!---<cfparam name="attributes.path" default="#request.page.jssourcefilepath#">--->
And put in my own literal path
<cfparam name="attributes.path" default="js/">


Stephen Lloyd 03/07/2011