FilterController is used for filtering search results. it is not responsible for filtering following actions.
<li>Suggested Keyword Action</li> <li>Keyword Filter Action</li> <li>Category Filter Action</li> <li>Manufacturer Filter Action</li> <li>Attribute Filter Action</li>
FilterController also manages the searc and display trail of user filtered searches.
Located in /controllers/FilterController.php (line 28)
Zend_Controller_Action | --BaseController | --FilterController
Inherited from BaseController
BaseController::$endtime
BaseController::$starttime
attributeAction is used to filter search based on the attribute selected.
attributeAction provide support to filter absolute and non-absolute attributes.
It get the SearchTrail obejct from previous request and add the selected attribute in trail.
Attribute data retrieve from GET parameters by using 'attributefilter' as the parameter name. It contians concatenated string with attribtue id and value. If select attribute us absolute then 'absoluteOperator' also retrieve from GET parameters list. *
Modified SearchTrail with filtered search is then set in the REQUEST as a string with parameter name 'trail'. 'trail' parameter is then used in the view to generate the display search trail.
DisplaySearch trail list the selected filters.
This action uses web service model classes to perform the web services requests. WSFactory is used to create different keyword search requests. WSRequest is used to encapsulate the search keywords. WSRequest instance is than passed to WSGateway which passed send request to spexlive client and finally request is send to http://ws.spexlive.net.
WSResponse object is created for the response of http://ws.spexlive.net. WSResponse object contains the XML data returned from hosted web services. This XML data is converted into a php object and then forwarded to view. Successfull response is forwarded to view that generate different filters and search results table with pagination.
For any reason web service call is failed (even after retries) than request is forwarded to the ErrorController.
Following objects are set for the view depending on the filtered search results:
<li>categoryFilter, It is used to create categories filter.</li> <li>manufacturerFilter, It is used to create manufacturers filter.</li> <li>attributeFilter, It is used to create attributes filter.</li> <li>trail, It is used to display search trail.</li> <li>productSummary, It is used to display product summarized information.</li> <li>page, It is used to display page no.</li> <li>count, It is used to display result count.</li>
categoryAction is used to filter search based on the category selected.
It get the SearchTrail obejct from previous request and add the selected category in trail.
Cateogry Id retrive from GET parameters by using 'id' as the parameter name.
Modified SearchTrail with filtered search is then set in the REQUEST as a string with parameter name 'trail'. 'trail' parameter is then used in the view to generate the display search trail.
DisplaySearch trail list the selected filters.
This action uses web service model classes to perform the web services requests. WSFactory is used to create different keyword search requests. WSRequest is used to encapsulate the search keywords. WSRequest instance is than passed to WSGateway which passed send request to spexlive client and finally request is send to http://ws.spexlive.net.
WSResponse object is created for the response of http://ws.spexlive.net. WSResponse object contains the XML data returned from hosted web services. This XML data is converted into a php object and then forwarded to view. Successfull response is forwarded to view that generate different filters and search results table with pagination.
For any reason web service call is failed (even after retries) than request is forwarded to the ErrorController.
Following objects are set for the view depending on the filtered search results:
<li>categoryFilter, It is used to create categories filter.</li> <li>manufacturerFilter, It is used to create manufacturers filter.</li> <li>attributeFilter, It is used to create attributes filter.</li> <li>trail, It is used to display search trail.</li> <li>productSummary, It is used to display product summarized information.</li> <li>page, It is used to display page no.</li> <li>count, It is used to display result count.</li>
keywordAction is used to filter search based on the keyword entered.
It get the SearchTrail obejct from previous request and add the selected keyword in trail.
keyword retrive from GET parameters by using 'keywords' as the parameter name.
Modified SearchTrail with filtered search is then set in the REQUEST as a string with parameter name 'trail'. 'trail' parameter is then used in the view to generate the display search trail.
DisplaySearch trail list the selected filters.
This action uses web service model classes to perform the web services requests. WSFactory is used to create different keyword search requests. WSRequest is used to encapsulate the search keywords. WSRequest instance is than passed to WSGateway which passed send request to spexlive client and finally request is send to http://ws.spexlive.net.
WSResponse object is created for the response of http://ws.spexlive.net. WSResponse object contains the XML data returned from hosted web services. This XML data is converted into a php object and then forwarded to view. Successfull response is forwarded to view that generate different filters and search results table with pagination.
For any reason web service call is failed (even after retries) than request is forwarded to the ErrorController.
Following objects are set for the view depending on the filtered search results:
<li>categoryFilter, It is used to create categories filter.</li> <li>manufacturerFilter, It is used to create manufacturers filter.</li> <li>attributeFilter, It is used to create attributes filter.</li> <li>trail, It is used to display search trail.</li> <li>productSummary, It is used to display product summarized information.</li> <li>page, It is used to display page no.</li> <li>count, It is used to display result count.</li>
manufacturerAction is used to filter search based on the manufacturer selected.
It get the SearchTrail obejct from previous request and add the selected manufacturer in trail.
Manufacturer Id retrive from GET parameters by using 'id' as the parameter name.
Modified SearchTrail with filtered search is then set in the REQUEST as a string with parameter name 'trail'. 'trail' parameter is then used in the view to generate the display search trail.
DisplaySearch trail list the selected filters.
This action uses web service model classes to perform the web services requests. WSFactory is used to create different keyword search requests. WSRequest is used to encapsulate the search keywords. WSRequest instance is than passed to WSGateway which passed send request to spexlive client and finally request is send to http://ws.spexlive.net.
WSResponse object is created for the response of http://ws.spexlive.net. WSResponse object contains the XML data returned from hosted web services. This XML data is converted into a php object and then forwarded to view. Successfull response is forwarded to view that generate different filters and search results table with pagination.
For any reason web service call is failed (even after retries) than request is forwarded to the ErrorController.
Following objects are set for the view depending on the filtered search results:
<li>categoryFilter, It is used to create categories filter.</li> <li>manufacturerFilter, It is used to create manufacturers filter.</li> <li>attributeFilter, It is used to create attributes filter.</li> <li>trail, It is used to display search trail.</li> <li>productSummary, It is used to display product summarized information.</li> <li>page, It is used to display page no.</li> <li>count, It is used to display result count.</li>
removeAction is used to remove sleted filter frm search based on the id and filter passed in request paramters.
It get the SearchTrail obejct from previous request and remove the selected filter from trail.
Modified SearchTrail with filtered search is then set in the REQUEST as a string with parameter name 'trail'. 'trail' parameter is then used in the view to generate the display search trail.
DisplaySearch trail list the selected filters.
This action uses web service model classes to perform the web services requests. WSFactory is used to create different keyword search requests. WSRequest is used to encapsulate the search keywords. WSRequest instance is than passed to WSGateway which passed send request to spexlive client and finally request is send to http://ws.spexlive.net.
WSResponse object is created for the response of http://ws.spexlive.net. WSResponse object contains the XML data returned from hosted web services. This XML data is converted into a php object and then forwarded to view. Successfull response is forwarded to view that generate different filters and search results table with pagination.
For any reason web service call is failed (even after retries) than request is forwarded to the ErrorController.
Following objects are set for the view depending on the filtered search results:
<li>categoryFilter, It is used to create categories filter.</li> <li>manufacturerFilter, It is used to create manufacturers filter.</li> <li>attributeFilter, It is used to create attributes filter.</li> <li>trail, It is used to display search trail.</li> <li>productSummary, It is used to display product summarized information.</li> <li>page, It is used to display page no.</li> <li>count, It is used to display result count.</li>
suggestAction is used to perform search with suggested keyword.
It initialize a new SearchTrail for every suggested search and gets suggested keywords and searched keyword from GET parameters by using 'suggestedKeyword' and 'keyword' as the parameter name.
Newly initiated SearchTrail is then set in the REQUEST as a string with parameter name 'trail'. 'trail' parameter is then used in the view to generate the display search trail.
This action uses web service model classes to perform the web services requests. WSFactory is used to create different keyword search requests. WSRequest is used to encapsulate the search keywords. WSRequest instance is than passed to WSGateway which passed send request to spexlive client and finally request is send to http://ws.spexlive.net.
WSResponse object is created for the response of http://ws.spexlive.net. WSResponse object contains the XML data returned from hosted web services. This XML data is converted into a php object and then forwarded to view. Successfull response is forwarded to view that generate different filters and search results table with pagination.
For any reason web service call is failed (even after retries) than request is forwarded to the ErrorController.
Following objects are set for the view:
<li>categoryFilter, It is used to create categories filter.</li> <li>manufacturerFilter, It is used to create manufacturers filter.</li> <li>attributeFilter, It is used to create attributes filter.</li> <li>trail, It is used to display search trail.</li> <li>productSummary, It is used to display product summarized information.</li> <li>page, It is used to display page no.</li> <li>count, It is used to display result count.</li>
Inherited From BaseController
BaseController::getAllCategories()
BaseController::getAllManufactures()
BaseController::getChildCategories()
BaseController::populateSearchResults()
BaseController::postDispatch()
BaseController::preDispatch()
BaseController::renderDynamicTemplates()
BaseController::serviceRequest()
BaseController::setCompareProductPage()
BaseController::setFooter()
BaseController::setHeader()
BaseController::setHomePage()
BaseController::setSearchResultsPage()
BaseController::setWSRequestFailed()
Documentation generated on Wed, 13 Feb 2008 01:57:35 +0500 by phpDocumentor 1.4.0a2