3. Frequently Asked Questions
The default public facing site is styled using Twitter Bootstrap for which [documentation is available] (http://twitter.github.com/bootstrap/).
Alternatively you can create your own template. [Documentation for using FW/1 layouts and views can be found here] (https://github.com/seancorfield/fw1/wiki). You can put your image, stylesheet and JavaScript files in the assets directory.
By default Xindi will assume your datasource and project directory have the same name. For example, if you installed Xindi to [http://localhost/foobar/] (http://localhost/foobar/) Xindi will assume your datasource is named "foobar". To override this open the Application.cfc file and find the line that reads:
this.datasource = ListLast( this.applicationroot, "\/" );
Change this to:
this.datasource = "your-datasource-name";
By default the enquiry form doesn't appear in the navigation, but can be accessed at [http://localhost/xindi/index.cfm/enquiry] (http://localhost/xindi/index.cfm/enquiry). To make the enquiry form part of the navigation you need to create a routing from a content managed page to the enquiry form as follows:
- In the content management system add a page that will become the contact page.
- Browse to the page in the public site and make a note of the last part of the url. For example, if the page url is [http://localhost/xindi/index.cfm/contact] (http://localhost/xindi/index.cfm/contact) we'll need the "contact" bit of the url.
- Open the Application.cfc file and find the commented out bit of code that reads
,routes = [ { ""="", hint="" } ]. Remove the "//" from the start of the line to uncomment the code. - In the first set of empty quotation marks enter the last part of your page url (e.g. "contact") and in the second set of empty quotation marks enter "enquiry".
- That's it! Now when you browse to your page it will redirect to the enquiry form. If it doesn't you may need to reload your application by requesting [http://localhost/xindi/index.cfm?reload=true] (http://localhost/xindi/index.cfm?reload=true).
[More information about FW/1 URL Routes can be found here.] (https://github.com/seancorfield/fw1/wiki/Developing-Applications-Manual)
By default the news feature doesn't appear in the navigation, but can be accessed at [http://localhost/xindi/index.cfm/news] (http://localhost/xindi/index.cfm/news). To make the news feature part of the navigation you need to create a routing from a content managed page to the news feature as follows:
- In the content management system add a page that will become the news page.
- Browse to the page in the public site and make a note of the last part of the url. For example, if the page url is [http://localhost/xindi/index.cfm/latestnews] (http://localhost/xindi/index.cfm/latestnews) we'll need the "latestnews" bit of the url.
- Open the Application.cfc file and find the commented out bit of code that reads
,routes = [ { ""="", hint="" } ]. Remove the "//" from the start of the line to uncomment the code. - In the first set of empty quotation marks enter the last part of your page url (e.g. "latestnews") and in the second set of empty quotation marks enter "news".
- That's it! Now when you browse to your page it will redirect to the news feature. If it doesn't you may need to reload your application by requesting [http://localhost/xindi/index.cfm?reload=true] (http://localhost/xindi/index.cfm?reload=true).
[More information about FW/1 URL Routes can be found here.] (https://github.com/seancorfield/fw1/wiki/Developing-Applications-Manual)
The underscore indicates that the directory should not be transferred to the production environment.
To improve performance the query that populates the navigation is cached for 1 minute.
If you have a question that is not answered here please [visit our Google Group] (https://groups.google.com/forum/?hl=en&fromgroups#!forum/getxindi) for help and advice.