[eluser]ebcms[/eluser]
Thanks Randy.
Sorry my post was light on details.
Some background: The search tool spiders the site and creates a set of files which are saved (or FTP'd) to the domain/directory location designated. These files include search.php (which handles processing the search query and the results display), plus all the data files from the indexing, which are used by search.php. We added a custom search form to our main header/navigation view that passes the search term via GET to the search.php file for processing. Search.php is receiving the query term properly. Our results are good and the output to search.php is working correctly.
Our issue is in how to integrate search.php into our MVC structure.
In a traditional php environment, we'd simply wrap search.php with header and footer includes and be done.
But in our CI site, we're trying to figure out how best to wrap these results with our header and footer views (both of which use dynamic data from our model). Can we call the search.php file via the controller? Should we include search.php in it's own view and call that view via the controller?
I guess the larger question here too, is what are some best practices for incorporating external data and/or files into CI generated "pages" for display.
Thanks,
David