Managed Hosting



onTap Framework
Project Home Blog Forums Wiki Known Issues Screenshots External Project Link Contact Project

onTap Framework Issue: Install Problem

Name: Install Problem
ID: 1
Project: onTap Framework
Type: Bug
Area: Documentation
Severity: Normal
Status: Closed
Related URL:
Creator: Lachie
Created: 01/16/08 1:17 PM
Updated: 07/07/08 2:51 PM
Description: Install Problem
01/07/08 11:29 AM


Looks like a pretty cool application but I am just having some install problems.

I have added a directory called "ontap" to the root of my server and have copied all the files there. So it will run off http://localhost/ontap/

I seem to be getting the CF error below about not finding the template because of an incorrect path. It is looking for the directory in the "tap" folder and not the "ontap" directory. I am assuming I missed something in the install but cant seem to find it reading the directions.



Could not find the included template /tap/_components/_pathsettings/000_default.cfm.
Note: If you wish to use an absolute template path (e.g. TEMPLATE="/mypath/index.cfm") with CFINCLUDE then you must create a mapping for the path using the ColdFusion Administrator. Using relative paths (e.g. TEMPLATE="index.cfm" or TEMPLATE="../index.cfm") does not require the creation of any special mappings. It is therefore recommended that you use relative paths with CFINCLUDE whenever possible.

The error occurred in I:\inetpub\wwwroot\ontap\_components\_pathsettings.cfm: line 4

2 : to allow dynamic inclusion of default path settings for plugin / add-on components --->
3 : <cfloop index="cfmod" list="#arrayToList(request.tapi.templateArray('_pathsettings','C','^.*\.cfm$',true,''))#">
4 : <cfinclude template="#cfmod#"></cfloop>
History: Created by lachie (Lachie) : 01/16/08 1:17 PM

Comment by lachie (Lachie) : 01/29/08 10:17 AM

Just to update this. I got it working but only after I changed the directory to "tap" not "ontap". It might be worth mentioning in the readme doc that the dir needs to be named this eg tap and not ontap



Comment by ike (Isaac Dealey) : 04/10/08 10:58 AM
Hi Lachie, sorry I didn't respond to this earlier... I must have overlooked it, expecting that I'd get an email or something to let me know when bugs got posted...

If you're running it on ColdFusion 8, it should work normally. You're having this problem because you're running it on a prior version and it's missing the /tap/ mapping -- changing your installation directory to "tap" allowed it to use the default webserver root mapping of "/" to find the application files.

Alternatively for these earlier versions of ColdFusion you would want to create a "/tap" mapping in the ColdFusion administrator, which is something I avoided in earlier versions of the framework because of multiple-instance problems. I decided to implement the mapping once Adobe released CF8 because it allowed me to simplify some of the code.

Thanks for the feedback! I'll have another look at the documentation and see if I can do something to eliminate some of the confusion on this issue.

Comment by ike (Isaac Dealey) : 04/10/08 10:59 AM
I just realized I didn't explain before that the framework creates the /tap mapping in the Application.cfc using the new application-specific mappings feature in CF8, so that's the reason for the change.

Updated by ike (Isaac Dealey) : 04/10/08 11:00 AM

Comment by ike (Isaac Dealey) : 04/10/08 11:45 AM
I've added some information to the wiki about this: http://ontap.riaforge.org/wiki/index.cfm?event=Main&path=Main.Installation

Comment by JeffSez (Jeff) : 07/07/08 2:51 PM
I just entered an issue under Members onTap because it reared it's ugly head whilst trying to install, but appears to be tied to any call to the tabset.cfc with JavaScript turned on.
Anyway, commenting because I was immediately notified that email had been sent to info@turnkey.to and bounced. Newer email address for those notification messages? (don't tell me, but update ontap.riaforge.org so you do get notified)Thanks for all the fish and a potentially fantastic framework!

To add a comment to this bug, please login using the link above.