1 2 Previous Next 67 Replies Latest reply on Oct 11, 2013 1:12 PM by Aegis Kleais

# Folder Directory Create

I recently Migrated our sharepoint from windows 2003 to 2008. In doing so I lost Cold fusion and a directory Wizard, This wizard was put in place to create a folder directory out on our network drive when used. Now I have Coldfusion 10 installed on my new sharepoint server, I have brought over all of these directory wizard files but it still does not work. Its like I am missing a certain link in the chain here. Can anyone shed some light on the topic?

The wizard opens up to the first page, which it says next to continue. You would select a company which the code is written to pull a companies list from the network drive, then it creates a folder directory with files in the on that network drive. Now when you lick the initital next button it buttons and takes us to a The website cannot display the page. I still have all the original code files, placed into the same exact directory on the sharepoint server. The sharepoint server is an identical match, but its like somewhere something isnt lined up correctly.

• ###### 1. Re: Folder Directory Create

Without knowing what this wizard is, I don't know how we could help.  Are you able to execute a CFM page with code on it to see if the service running CF has rights to create the directory?

<cfset directoryCreate( expandPath( '/path/to/new/directory' ) ) />

or

<cfset directoryCreate( 'C:\path\to\new\directory' ) />

I think ColdFusion 10 has a code analyzer built into it that you can run on the wizard files to see if it finds a problem with the code used in those files compared to the functionality that is available in CF10.

• ###### 2. Re: Folder Directory Create

Im sorry im still new to coldfusion. What do you mean by execute a CFM page? I am sitting here looking at my Coldfusion administration page and my Coldfusion builder, and for what you asked I feel I am not looking at the right thing.

• ###### 3. Re: Folder Directory Create

Where do I input

<cfset directoryCreate( expandPath( '/path/to/new/directory' ) ) />

or

<cfset directoryCreate( 'C:\path\to\new\directory' ) />

• ###### 4. Re: Folder Directory Create

This requires a level of familiarity with the basics of ColdFusion; the solution here will not be through the CF Admin.

What I wanted you to check was to create a ColdFusion page, such as 'test.cfm'.  Place it within the web root of your ColdFusion server, and ensure that the code I provided above is in it (but modify the paths to your local filesystem).

Then, simply navigate to the file in a browser; it will execute the page.  You can put a <cfoutput>All done!</cfoutput> at the end of the code so you have some visual indicator that the page executed, and then go check the directory you specified, and it should be created.

Sorry, I'm not familiar with Sharepoint, so I'm not sure what role it's playing in all this.  You said you have CF 10 installed, so I assume it's up and running and ready to serve CFM pages.

• ###### 5. Re: Folder Directory Create

Yeah I should of been more clear. Sharepoint doesnt have anything to do with this. What I am trying to do is migrate a WORKING Coldfusion 7 page into Coldfusion 10 which is running on a seperate server. I thought just copying and pasting it into the same directory path would work but it does not.

• ###### 6. Re: Folder Directory Create

Oh, dang.

CF10's Code Analyzer (available from CF Admin > Debugging & Logging > Code Analyzer) actually only goes back as far as CF8 to determine if there are deprecated content in the CFM.

I'd say chances are, this is the issue.  That's quite a bit of time between versions.  These wizard files which are failing; do you remember where you got them?  Maybe they can provide a CF10-compatible version.

• ###### 7. Re: Folder Directory Create

These files were already in place and running when I took the position, being access by our sharepoint, I recently migrated our sharepoint to a better server unaware it needed Coldfusion to operate a part of the webpage. Well we couldnt reinstall coldfusion 7 because its no longer supported so I had to purchase Coldfusion 10. So I now have 2 windows servers, one with Coldfusion 7 which runs the CFM pages fine, and on another server coldfusion 10 with the exact same Coldfusion files just moved over that are not working. Now I dont know if there if there is a setting in coldfusion I need to change as far as mapping or setting the directory?

The files themselves look hand coded. It operates in the way where it pulls a group of names from our network server, the user then selects one of those group names, then in the box below the user gives it a new project name which they would click next to complete it. This creates a folder inside that first selected group, and inside of that folder which also has folders and files inside of that. Its hard to explain over the forum but hopefully this draws a better picture.

>Created folder>word document

Group > Created folder inside that group >Created folder>word document

>Created folder>excel document

Also I hate to overload this post, but when I use the webserver configuration tool and Add a new configuration. After it completes it kills my Coldfusion administration page. I can not navigate out to it, I get a webpage cannot be displayed, and if I removed that added configuration my Admin page will come right back.

• ###### 8. Re: Folder Directory Create

When you were using the WSC tool, were you integrating ColdFusion into an IIS server, where it can capture requests off the default port of 80, or is ColdFusion running as standalone, where it usually runs off the default port of 8500?

What the WSC tool does is create a CFIDE and Jakarta folder in the sites you specify, and it creates Handler Mappings so that associated CFM/CFML/CFC/CFSWF/CFR files execute off the isapi_rewrite.dll located in the jakarta virtual directory.

Maybe if I understood a little more about your server setup I might be able to think of a thing you can check.

• ###### 9. Re: Folder Directory Create

Yes the coldfusion is integrated into an IIS server where it captures requests off the default port of 80. My sharepoint is running on the 80 port, I go into the WSC tool and add my sharepoint IIS to the WSC tool. Thats how I was able get the Coldfusion 7 working with my old sharepoint. I then tried to do the same thing on my Coldfusion 10 but it does not work and also it knocks off my coldfusion admin page.

• ###### 10. Re: Folder Directory Create

OK, I'm assuming IIS7+ or so here, but

1. Goto the site where the CF is running off of.  Is there a CFIDE and jakarta virtual directory off the root of the site?  (If not, create one called CFIDE and map it to {CF-INSTALL-PATH}\cfusion\wwwroot\CFIDE.  Ensure there is a folder called jakarta (if not, create one and map it to {CF-INSTALL-PATH}\config\wsconfig\1

2. Open up the site and select HANDLER MAPPERS.  Ensure you have an entry for .cfm, .cfml, .cfc, .cfswf, .cfr and that they point to: {CF-INSTALL-PATH}\config\wsconfig\1\isapi_redirect.dll

3. Open up the site and select ISAPI FILTERS.  Ensure you have an entry for CF (It'll probably call itself Tomcat) and that it points to: {CF-INSTALL-PATH}\config\wsconfig\1\isapi_redirect.dll

4. Open up the SERVER and select ISAPI AND CGI RESTRICTIONS.  Make sure that your tomcat ISAPI filter is set to ALLOWED for restriction.

Confirm these for me if you can.

• ###### 11. Re: Folder Directory Create

Okay now I feel were getting somewhere.

1. There was already a CFIDE folder in my cfusion directory. I did have to create the folder jakarta out under my C:\cfusion\config\wsconfig\1\jakarta.

2. All the HANDLERMAPPERS were added and pointing to the correct path.

3. ISAPI FILTERS are allowed and pointing to the correct path for Tomcat

4. There is nothing Restricted in my ISAPI AND CGI RESTRICTIONS. Tomcat is included along with ASP net

Now when I got out to my sharepoint and click the link I actually get the first page of my wizard. It shows up. It does say "welcome press next to continue" but when you press next the screen turns white, but i feel this is an improvement because before when I pressed next I would get " Webpage can not be displayed."

Also I dont know if these means anything but I was checking my old servers ISAPI AND CGI RESTRICTIONS and it has a macromedia server extentions which the path is pointed the Cfusion7 directory towards these .dlls. (Jrun_iis6.dll and Jrun_iis6_wildcard.dll) Their path was CfusionMX7\runtime\lib\wsconfig\

I cant seem to find those same .dll in my Cfusion10 directory

• ###### 12. Re: Folder Directory Create

CF10 does things differently; it has no need for the wildcard solution that previous versions of CF used.

OK, when you get to the website that displays a blank page, can you view the source through the browser and see if any code was actually generated?

Also, were there any other numerical folders in C:\cfusion\config\wsconfig ?  By default, each time you run the connector, it may create a new folder (2, 3, 4).  If the settings are internally set to a number other than 1, and we've pointed everything to '1', this could be a reason why things are not working.  CF relies on the jakarta virtual directory in order for CFML pages to generate.

Just for clarification on my side.  This isn't the CF wizard we're talking about, right?  Where after you install, the browser opens and you complete the rest of the installation setup process.  That's already been done, correct?  This "Sharepoint" is like you navigating out to a location like:

http://nameofServer/sharepointFilesFolder/file.cfm

Correct?

Also, can you goto START > CMD > services.msc and ensure that ll 5 CF services are running?  (At the least, The CF10 Application Server service needs to run, but let's just ensure those are correct as well).  Can you provide us with the URL of the page that is rendering for you?

• ###### 13. Re: Folder Directory Create

Okay comparing the first page that actually displays something to the second blank white page, the source is not what it should be. Here it is, minus the (//\\) I didnt want to mess up the post:

//\\ <!DOCTYPE HTML PUBLIC

//\\"-//W3C//DTD HTML 4.0 Transitional//EN">

//\\ <BODY></BODY></HTML>

Yes there was the number 1. Now when you say settings internally set, is this a setting set in the original code of my files or something out on the coldfusion admin page? Now this is the same code ran in my coldfusion 7 its just been moved over to my coldfusion10 server. So the code is the same. Ive gone through a lot of the code and have not seen a directory path with the number 1 in it.

No this is not the CF wizard, coldfusion has been installed and the first initial log in wizard has already been ran.

Yes that URL is correct, But to be specific here is what I see: http://sharepoint13.com/Divisions/ENGTECH/ProjectDirectoryWizard/dir_startup.cfm

Where Divisions is a folder in my sharepoint folder, this is my first page of my wizard which works, then you click next and the page goes white: http://sharepoint13.com/Divisions/ENGTECH/ProjectDirectoryWizard/DIRECTORY.CFM

Yes all 5 Coldfusion processes are running.

• ###### 14. Re: Folder Directory Create

So I have to ask now, Since the first page works, The source looks good, but then we go to the second page where we can see the source is clearly not what we need. What happens? What makes it go from reading that first .cfm file to attempting to read the next but it fails.

• ###### 15. Re: Folder Directory Create

Is the contents of the directory.cfm code too long to post here?  If it's private, I can understand and respect that.  I'd just like to inspect it to see if I can see any code which may not be working in the CF10 environment.

CF has to be running just fine, because the first page is a CFM, and it functioned and rendered just fine.  Chances are, though, it may be using rather simple CF that functions the same in CF7 as it does in CF10.

You're saying this second page generates a white page and there is no source code generated from it, so it is either failing to generate output, or is encountering some type of processing error.

• ###### 16. Re: Folder Directory Create

Here is the Code for the next page. Now from what I can tell this code has parts that it is recalling other pieces of code into it. Directory2 is another code file I have. But since nothing shows up there must be something wrong with this main piece. I dont think there is any sensitive information in any of them, but the information they pull from my network yes, which cant be seen unless its ran here.

<HTML>
<TITLE>C&I Engineering - Project Directory Wizard</TITLE>
<BODY>

<CENTER>

<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
<CFINCLUDE TEMPLATE="MAINAREA.CFM">

<!---
--->

<FORM ACTION="DIRECTORY2.CFM" METHOD="POST">

<TABLE WIDTH="100%" HEIGHT="100%" BGCOLOR="#D4D0C8">
<TR><TD>
Please select a company directory to place the new projects:<BR>

<CFDIRECTORY action="list" DIRECTORY="\\SERVERNAME\shared\PROJECTS"
NAME="myDirectory"
SORT="Name ASC">
<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">

<SELECT NAME="MAINDIRECTORY">
<OPTION>
<CFOUTPUT QUERY="myDirectory">
<CFIF TYPE IS "Dir">
<CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">
<OPTION VALUE="#NAME#" SELECTED>#Name#
<CFELSE>
</CFIF>
<OPTION VALUE="#NAME#">#Name#

</CFIF>
</CFOUTPUT>
</SELECT>
<BR>

<BR>
Project Name:<BR>
<INPUT TYPE="TEXT" MAXLENGTH="20" SIZE="20" NAME="DIRTOCREATE" VALUE="">

<BR><BR>

</TD></TR>
</TABLE>
<CFINCLUDE TEMPLATE="ACTIONBUTTONS.CFM">
</FORM>

</BODY>
</HTML>

• ###### 17. Re: Folder Directory Create

Well I see a lot of HTML errors here, but I'm going to go with the obvious.

Try wrapping the entire document (make a backup first) in <CFOUTPUT>

If the page is being requested and there is no error, but nothing is being generated, chances are, CF is not outputting it to the buffer.

And wow, is that a <center> tag I see?  That's a blast from the past!

• ###### 18. Re: Folder Directory Create

Maybe something like this:

<cfparam name="selectedDirectory" default="" />

<cfoutput><!DOCTYPE html>

<html>

<title>C&amp;I Engineering - Project Directory Wizard</title>

<body>

<cfinclude template="mainarea.cfm" />

<form action="directory2.cfm" method="post" enctype="application/x-www-form-urlencoded">

<p>Please select a company directory to place the new projects:</p>

<hr>

<cfdirectory

action="list"

directory="\\servername\shared\projects"

name="myDirectory"

sort="name ASC" />

<select name="mainDirectory">

<cfloop query="myDirectory">

<cfif type eq 'dir'

and name is uCase( VARIABLES.selectedDirectory )>

<option value="#name#" selected="selected">#name#</option>

<cfelse>

<option value="#name#">#name#</option>

</cfif>

</cfloop>

</select>

<hr>

<hr>

<p>Project Name:</p>

<p><input type="text" maxlength="20" size="20" name="dirToCreate" value="" /></p>

<hr>

<cfinclude template="actionbuttons.cfm" />

</form>

</body>

</html>

</cfoutput>

I couldn't understand the logic you're using for the select option list loop.  You default a variable called selectedDirectory to an empty string and then you loop over the list of files and folders from the specified value and check to see if they are a directory and have a name equal to the uppercase value of an empty string.

• ###### 19. Re: Folder Directory Create

Yeah I wish I was the one who wrote this code maybe I would better understand it, This was put into place YEARS and YEARS ago. My network Admin was telling me he could still remember the day they had to purchase CF7 for the guy who originally wrote the code. Unfortunately once they got this thing working on CF7 I don't think it has ever been looked at and now its time to upgrade and several people down the Tech position here I am trying to keep this code alive so my end users can still work and use it. Hence the jump from CF7 to CF10.

Okay so heres what happened. I backed up my original, plugged the modified code in and I got nothing. Im thinking something in CF has to be restarted? I log into my CF10 server stop CF, start it back up again and try to run this again still nothing. Still takes you to a blank white page with this for the source code:

<!

DOCTYPE HTML PUBLIC

"-//W3C//DTD HTML 4.0 Transitional//EN">

Now just for a test I tried to plug in the same exact code as my first page into this code were looking at, in theory, I press next and it takes me to the next page that should look identical to the first, right? Well it still goes to the white page with that above code. Now maybe I dont know if there is a restart and load what has changed button in CF, maybe there is? Im also thinking that the code is written seperatley for these Action buttons (back, next, and cancel) Could the (Next) button be coded in a way to not bring up the next page properly? Or is that just a default CF command.

BODY></BODY></HTML >

Okay I dont know why the code seperates like that, but all the code on this post should be together know that.

• ###### 20. Re: Folder Directory Create

Okay so it looks like the code updates automatically when I change things in the back end. Since nothing comes up when I press next, could that mean my "Next" button is wrong? Im not sure how to open up this file directly as a CFM, so I saved it as an HTML and the page does come up, with errors of course but something actually comes up in IE. So im losing something inbetween clicking next on the first page to grabbing the code that we just worked on.

UPDATE

Okay So I decided to plug our code directly into the first page code file, just to bypass the next button entirely and I do get a page displayed. There is errors, The drop down bar that should be displaying all the company names is blank, so it seems to not be pulling anything which there is another code file also I can look at, this code looks to pull all the directoy names that are present on the network drive and display them in an array in this drop down box. The Add new client button works, it takes you to the next screen and has a blank box to type in your client and press next, but of course when you press next the screen goes to a white page like before.

This is the code I have for my "actionbuttons.cfm"

<!--

BACK/NEXT/CANCEL Buttons

-->

</TR>

<TR BGCOLOR="#D4D0C8">

<TD COLSPAN="2">

<HR>

<TABLE BORDER="0" WIDTH="100%" BGCOLOR="#D4D0C8">

<TR>

<TD WIDTH="80%"></TD>

<TD><INPUT TYPE="BUTTON" DISABLED VALUE="  < Back  "></TD>

<cfif isdefined("FINALWIZPAGE")>

<TD><INPUT TYPE="SUBMIT" VALUE="Finish"></TD>

<CFELSE>

<TD><INPUT TYPE="SUBMIT" VALUE="  Next >  "></TD>

</CFIF>

<TD></TD>

<TD><INPUT TYPE="BUTTON" VALUE="  Cancel  "></TD>

</TR>

</TABLE>

</TR></TD>

And this is my first page that tries to Invoke the "actionbuttons.cfm"

<HTML>
<TITLE>C&I Engineering - Directory Wizard</TITLE>
<BODY>

<CENTER>

<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
<CFINCLUDE TEMPLATE="MAINAREA.CFM">

<!---
--->
<FORM METHOD="POST" ACTION="./DIRECTORY.CFM">

<TABLE WIDTH="100%" HEIGHT="100%" BGCOLOR="#D4D0C8">
<TR><TD>
<FONT SIZE="+2">
Welcome to the Project Directory setup program
</FONT><BR><BR>
This web-based wizard helps you to create the appropriate directories
for a particular project.<BR><BR>

</TD></TR>
</TABLE>

<CFINCLUDE TEMPLATE="ACTIONBUTTONS.CFM">

</FORM>

</BODY>
</HTML>

• ###### 21. Re: Folder Directory Create

How familiar are you with ColdFusion code and HTML?   Do me a favor...

1. If there is an application.cfc file in the main directory (or 'application.cfm') temporarily rename it as 'application.cfc.old' or 'application.cfm.old' so that its code does not execute.

2. Create a new page called 'test.cfm' and put this coded in it:

<cfset directoryPath = 'c:\windows' />

<cfdirectory

action="list"

directory="#directoryPath#"

recurse="false"

type="dir"

name="directories" />

<cfoutput>

<select name="directory" id="directory">

<cfloop query="directories">

<option value="#directory#\#name#">#name#</option>

</cfloop>

</select>

</cfoutput>

3. Put that file in the root of the site, but update the first line, where directory path is, to point the the location where you want to get a list of folders.

4. Open a browser and navigate out to this test.cfm page.  It should present you with a simple dropdown list, populated with folders from the specified directory path.

• ###### 22. Re: Folder Directory Create

I know enough to identify what Im looking at but now enough to truly code my own and work with something. Especially as Im looking at outdated code.

I plugged that in and get a blank drop down box.

I feel like I am only giving you bits and pieces to what Im working worth and I cant explain it well enough for you to understand. Ive uploaded a small zip file that contains the couple files Im looking at.

http://www.filedropper.com/cf_1

The wizard starts with the file Dir_startup, then click next, the next window is Directory which calls to Directory2 and AddNewclient. This window pulls all the folder directories from my network server and shows them in a drop down, allows me to select one. Then in the bottom text box to give my new project a name, then click next to create the folders in the selected directory.

Hopefully this gives you a better image of what I am looking at.

• ###### 23. Re: Folder Directory Create

OK, so dir_startup.cfm comes up, right.  You press NEXT to goto directory.cfm where you're expecting the dropdown to be populated with directories from the path you provided, no?

Are you getting to directory.cfm and is the dropdown populating with expected values?  Because directory.cfm has code on line 24 (the <cfdirectory> tag) which is looking for the path:

\\servername\shared\projects

That means, you have to have a server ON your network called servername, and the subsequent path (shared\projects) needs to exist as well.  Can you confirm this?

• ###### 24. Re: Folder Directory Create

Yes dir_startup comes first, which just says welcome etc please press next. Once you press next it takes you to DIRECTORY. (this is when the white screen comes up and I get nothing)

So no I am not getting anything once I get to directory, but yes I do have a server on my network called \\Servername with the directory path to where it should look to as \\servername\shared\projects.

Now all of this code, all those files, work flawlessly in CF7. It works exactly how I am trying to describe it. When I bring those files over to my CF10 server, and try to run it is when all these problems come up. I thought initially it could be my CF10 server set up, but I feel all of the setup is done automatically and just relies on the code of my files. Second I feel maybe the code is just too outdated?

Would it help you in in this picture im trying to paint if I gave you the running source code of my DIRECTORY ran on CF7? Like run the page and pull the source straight from my IE? Because when I view the source it displays all the extra fill in information.

Im just going to add it. This is the Source pulled from my CF7 when I run the DIRECTORY PAGE. Theres more than 4 companies i just shortended it, but you see how it pulls the list of folders and would display them all in the drop down box.

<HTML>
<TITLE>Project Directory Wizard</TITLE>
<BODY>

<CENTER>

<STYLE>

<!--
BODY
{
FONT: 8pt Arial;
}

.Title
{
FONT: 9pt Arial;
COLOR: WHITE;
}

-->
</STYLE>

<tr>

<td bgcolor=#0A246A align=left valign=top background="./images/topbarbg.jpg">

<font size="2" color="White" face="arial"><p class="title"><b> Project Directory Setup</b></font>
</td>
</tr>

<tr>
<td bgcolor=#D4D0C8>
<TABLE WIDTH="100%">
<TR>

<TD BGCOLOR="#000080" WIDTH="162">
<IMG SRC="./IMAGES/LEFTSIDE2.JPG">
</TD>
<TD BGCOLOR="#D4D0C8" WIDTH="100%">

<FORM ACTION="DIRECTORY2.CFM" METHOD="POST">

<TABLE WIDTH="100%" HEIGHT="100%" BGCOLOR="#D4D0C8">
<TR><TD>
Please select a company directory to place the new projects:<BR>

<SELECT NAME="MAINDIRECTORY">
<OPTION>

<OPTION VALUE="Company1">Company1
<OPTION VALUE="Company2">Company2
<OPTION VALUE="Company3">Company3
<OPTION VALUE="Company4">Company4
<OPTION VALUE="Company5">Company5
</SELECT>
<BR>

<BR>
Project Name:<BR>
<INPUT TYPE="TEXT" MAXLENGTH="20" SIZE="20" NAME="DIRTOCREATE" VALUE="">

<BR><BR>

</TD></TR>
</TABLE>
<!--
BACK/NEXT/CANCEL Buttons
-->
</TR>
<TR BGCOLOR="#D4D0C8">
<TD COLSPAN="2">
<HR>
<TABLE BORDER="0" WIDTH="100%" BGCOLOR="#D4D0C8">
<TR>
<TD WIDTH="80%"></TD>
<TD><INPUT TYPE="BUTTON" DISABLED VALUE="  < Back  "></TD>

<TD><INPUT TYPE="SUBMIT" VALUE="  Next >  "></TD>

<TD></TD>
<TD><INPUT TYPE="BUTTON" VALUE="  Cancel  "></TD>
</TR>
</TABLE>
</TR></TD>

</FORM>

</BODY>
</HTML>

• ###### 25. Re: Folder Directory Create

From the message thread above, it sounds like you haven't customized the ColdFusion install beyond the defaults.  By default, the ColdFusion service will run as the Local System account. This account cannot access network resources.  You will need to go into the Windows Services applet and set the ColdFusion service to run under a Windows domain account that has permissions to your network server folder structure.

If your ColdFusion 7 server is still running somewhere, go check what account the ColdFusion service is running under.  Use the same account on your new ColdFusion 10 server.

HTH,

-Carl V.

• ###### 26. Re: Folder Directory Create

Sorry, volzc9802

I've been fighting this forum login bug on Adobe's forums.  Both Chrome (my preferred browser) and IE are now failing to log me in, so I opened Firefox and was able to get in)

Carl stole my thunder here *shakes fists at Carl* 8:)

You need to check the credentials that your ColdFusion application server service is running as.

START > CMD > services.msc

If it is LOCALSYSTEM then that is why it cannot get the directory listing off another machine.  Do you have an account that has such rights?  If so, set the service to that account and restart the service, then attempt the page again and report the result.

I'm not sure how much longer it's going to be until Adobe can fix their forums.

• ###### 27. Re: Folder Directory Create

Yeah when I read Carls Post I had that Facepalm moment, couldnt believe I forgot that. ha! But I feel my solution is right on the tips of my fingers and heres why.

Yes changing the local System to my network Login fixed the issue of the drop down bar not picking up my network directory, so that works. I am still having the issue of the blank white page when transissioning from one page to the next via the "Next button" Now What I did to test the drop down was replace the first welcome page ( Dir_startup ) code with my second page ( DIRECTORY ) code so when you click the link it goes straight to the page with the drop down selection box, so thats how I was able to confirm the drop down now works, but when I make my selection, then type in the name of the folder to add in that selection, click next, my next page is that dreaded white page again.

So it really seems now the issue is the clicking of the "Next" button and the transission to the next page that it is targetting. The URL is displaying the Correct page but the visual of the page is just blank white with the HTML source not pulling from the next .CFM page.

The URL goes from a working: http://sharepoint13.com/Divisions/ENGTECH/ProjectDirectoryWizard/dir_startup.cfm then you click next, the URL advances to http://sharepoint13.com/Divisions/ENGTECH/ProjectDirectoryWizard/DIRECTORY.CFM but the page is blank and it does not pull the source code from my DIRECTORY.CFM. I was able to confirm this happens on all "NEXT" button pushes by putting my DIRECTORY.CFM code into my DIR_STARTUP.CFM, so esentially my wizard starts on page 2, the actual page where you select where you want to create this new directory on the network, you click next to advance to third .CFM page http://sharepoint13.com/Divisions/ENGTECH/ProjectDirectoryWizard/DIRECTORY2.CFM and the page is completely white just like before.

UPDATE

I tried to remove the:

<CFINCLUDE TEMPLATE="ACTIONBUTTONS.CFM">

and replaced it with:

Trying to bypace that "Next" button code, it advances to the next page like it always has but still just displays a white page. I can not get it to go to the next page and pull the code from my DIRECTORY.CFM file.

• ###### 28. Re: Folder Directory Create

GRRR!

I am getting SO AGGRAVATED at Adobe with these damn forum login issues!  I've reset my password, cleared by cache, restarted by browser, and now Chrome and Firefox can't login!  Dangit, sorry volzc9802, for taking so long to get back; I've been fighting Adobe's forums just to respond.

Here's what I'm thinking.  Your site is operating off a subdirectory, not directory off the site root right?  So, as such.  Is there a chance that ColdFusion may be looking for an application.cfc file in the current directory, not finding it, and then traversing up the directory structure until it does find one (which was not designed for your files in question)?

If so, add an application.cfc and populate it with the bare necessities:

<cfcomponent>

<cfset THIS.name = 'testApplication' />

</cfcomponent>

Then re-request the first file and see if submitting a form gets any further.

Secondly, can you view the source on the first page and then validate it through this page:

http://validator.w3.org/

Clcik on VALIDATE BY DIRECT INPUT and then paste the code in.  If you could cut n paste the errors that come after it, one might be so severe as to cause us issues during the submit.  I know this code is FAR from valid, but it might find something we're overlooking as well.

You said you were using IIS right?  What version?

• ###### 29. Re: Folder Directory Create

But yea I created the application.cfc in my wwwroot directory along with all the other .cfm files with the code you gave me, and I still just get the first page and it will not advance to the next.

When I use the validater I do get a good amount of errors.

Im at a loss for what is wrong. I can put any page in the first page, but nothign we try will get it to execute and move on to the next page and execute the commands.

I took a CF10 example off adobe, it was 2 files, asks to load a picture, click submit, then says congrats its uploaded on the second page with the picture on the webpage. yeah that works. So it has to be my code in general.

• ###### 30. Re: Folder Directory Create

Is the sample code you tested from Adobe referencing itself in the <form> element's action attribute?

On the second page, can you insert the following code at the top of the page?

<cfdump var="#CGI#" />

<cfdump var="#FORM#" abort="1" />

Let me know if the page dumps any information when it executes.  If it does, please cut and paste the results so we can see.

• ###### 31. Re: Folder Directory Create

It is using <cfform> here is the link:

Here is the dump, now this is the Second page (DIRECTORY) being ran as the first page, so thats why is says dir_start.

struct

AUTH_TYPE NTLM

AUTH_USER DOMAIN\USER

CERT_FLAGS [empty string]

CERT_ISSUER [empty string]

CERT_KEYSIZE [empty string]

CERT_SECRETKEYSIZE [empty string]

CERT_SERIALNUMBER [empty string]

CERT_SERVER_ISSUER [empty string]

CERT_SERVER_SUBJECT [empty string]

CERT_SUBJECT [empty string]

CF_TEMPLATE_PATH C:\inetpub\wwwroot\wss\VirtualDirectories\80\Divisions\ENGTECH\ProjectDirectoryWizard\dir _startup.cfm

CONTENT_LENGTH 0

CONTENT_TYPE [empty string]

CONTEXT_PATH [empty string]

GATEWAY_INTERFACE CGI/1.1

HTTPS off

HTTPS_KEYSIZE [empty string]

HTTPS_SECRETKEYSIZE [empty string]

HTTPS_SERVER_ISSUER [empty string]

HTTPS_SERVER_SUBJECT [empty string]

HTTP_ACCEPT application/x-ms-application, image/jpeg, application/xaml+xml, image/gif, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*

HTTP_ACCEPT_ENCODING gzip, deflate

HTTP_ACCEPT_LANGUAGE en-US

HTTP_CONNECTION Keep-Alive

HTTP_HOST Sharepoint13.com

HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C; .NET4.0E)

PATH_INFO [empty string]

PATH_TRANSLATED C:\inetpub\wwwroot\wss\VirtualDirectories\80\Divisions\ENGTECH\ProjectDirectoryWizard\dir _startup.cfm

QUERY_STRING [empty string]

REMOTE_HOST X.X.X.X

REMOTE_USER DOMAIN\USER

REQUEST_METHOD GET

SCRIPT_NAME /Divisions/ENGTECH/ProjectDirectoryWizard/dir_startup.cfm

SERVER_NAME Sharepoint13.com

SERVER_PORT 80

SERVER_PORT_SECURE 0

SERVER_PROTOCOL HTTP/1.1

SERVER_SOFTWARE Microsoft-IIS/7.5

WEB_SERVER_API [empty string]

struct [empty]

• ###### 32. Re: Folder Directory Create

Well that doesn't make sense.

The SCRIPT_NAME shows dir_startup.cfm, which you said was your first page, but this code should have been placed on the second page.  I noticed that because the METHOD by which the CGI shows the page was invoked was a GET call, and not a POST.  The FORM scope won't have any information on this page.  We're interested in seeing the CGI information as well as the FORM once you've submitted the form.  Put the code I provided on the second page and let me know what outputs there for the CGI and FORM dump.

And how are you using <cfform>?  The page itself shows a <form> tag, not a <cfform> tag.

I know you moved the 2nd page information into the first, but we need you to set that back as it was.  The FORM scope shows form information but it can only do so if you POST to the second page, not GET.

• ###### 33. Re: Folder Directory Create

This is the code I plugged in to get the previous post, I was trying to re-write it. I NEVER put the METHOD as GET, it has always been set as POST.

<cfFORM ACTION="DIRECTORY2.CFM" METHOD="POST" enctype="text/plain">
<TITLE>C&I Engineering - Project Directory Wizard</TITLE>

<CENTER>

<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
<CFINCLUDE TEMPLATE="MAINAREA.CFM">

<TABLE WIDTH="100%" HEIGHT="100%" BGCOLOR="#D4D0C8">
Please select a company directory to place the new projects:<BR>

<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"
NAME="myDirectory"
SORT="Name ASC">
<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">

<SELECT NAME="MAINDIRECTORY">
<OPTION>
<CFOUTPUT QUERY="myDirectory">
<CFIF TYPE IS "Dir">
<CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">
<OPTION VALUE="#NAME#" SELECTED>#Name#
</CFIF>
<OPTION VALUE="#NAME#">#Name#
</CFIF>

</CFOUTPUT>

</SELECT>
<BR><BR>
Project Name:<BR>
<INPUT TYPE="TEXT" MAXLENGTH="20" SIZE="20" NAME="DIRTOCREATE" VALUE="">

<BR><BR>

</TABLE>
<CFINCLUDE TEMPLATE="ACTIONBUTTONS.CFM">
</cfFORM>

Here is the original dump before I changed anything.

struct
AUTH_TYPENTLM
AUTH_USERDOMAIN\USER
CERT_FLAGS[empty string]
CERT_ISSUER[empty string]
CERT_KEYSIZE[empty string]
CERT_SECRETKEYSIZE[empty string]
CERT_SERIALNUMBER[empty string]
CERT_SERVER_ISSUER[empty string]
CERT_SERVER_SUBJECT[empty string]
CERT_SUBJECT[empty string]
CF_TEMPLATE_PATHC:\inetpub\wwwroot\wss\VirtualDirectories\80\Divisions\ENGTECH\ProjectDirectoryWizard\dir_ startup.cfm
CONTENT_LENGTH0
CONTENT_TYPE[empty string]
CONTEXT_PATH[empty string]
GATEWAY_INTERFACECGI/1.1
HTTPSoff
HTTPS_KEYSIZE[empty string]
HTTPS_SECRETKEYSIZE[empty string]
HTTPS_SERVER_ISSUER[empty string]
HTTPS_SERVER_SUBJECT[empty string]
HTTP_ACCEPTapplication/x-ms-application, image/jpeg, application/xaml+xml, image/gif, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*
HTTP_ACCEPT_ENCODINGgzip, deflate
HTTP_ACCEPT_LANGUAGEen-US
HTTP_CONNECTIONKeep-Alive
HTTP_HOSTSharepoint13.com
HTTP_REFERERhttp://Sharepoint13.com/Divisions/ENGTECH/index.htm
HTTP_USER_AGENTMozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C; .NET4.0E)
PATH_INFO[empty string]
PATH_TRANSLATEDC:\inetpub\wwwroot\wss\VirtualDirectories\80\Divisions\ENGTECH\ProjectDirectoryWizard\dir_ startup.cfm
QUERY_STRING[empty string]
REMOTE_HOST10.1.8.147
REMOTE_USERDOMAIN\USER
REQUEST_METHODGET
SCRIPT_NAME/Divisions/ENGTECH/ProjectDirectoryWizard/dir_startup.cfm
SERVER_NAMEintranet.cieng.com
SERVER_PORT80
SERVER_PORT_SECURE0
SERVER_PROTOCOLHTTP/1.1
SERVER_SOFTWAREMicrosoft-IIS/7.5
WEB_SERVER_API[empty string]
struct [empty]

And here is the code for said Dump:

<HTML>
<TITLE>C&I Engineering - Project Directory Wizard</TITLE>
<BODY>

<CENTER>

<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
<CFINCLUDE TEMPLATE="MAINAREA.CFM">

<!---
--->

<FORM ACTION="DIRECTORY2.CFM" METHOD="POST">

<TABLE WIDTH="100%" HEIGHT="100%" BGCOLOR="#D4D0C8">
<TR><TD>
Please select a company directory to place the new projects:<BR>

<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"
NAME="myDirectory"
SORT="Name ASC">
<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">

<SELECT NAME="MAINDIRECTORY">
<OPTION>
<CFOUTPUT QUERY="myDirectory">
<CFIF TYPE IS "Dir">
<CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">
<OPTION VALUE="#NAME#" SELECTED>#Name#
<CFELSE>
</CFIF>
<OPTION VALUE="#NAME#">#Name#

</CFIF>
</CFOUTPUT>
</SELECT>
<BR>

<BR>
Project Name:<BR>
<INPUT TYPE="TEXT" MAXLENGTH="20" SIZE="20" NAME="DIRTOCREATE" VALUE="">

<BR><BR>

</TD></TR>
</TABLE>
<CFINCLUDE TEMPLATE="ACTIONBUTTONS.CFM">
</FORM>

</BODY>
</HTML>

• ###### 34. Re: Folder Directory Create

The SCRIPT_NAME tells me that dir_startup.cfm is what was requested.   And look at the REQUEST_METHOD, it states GET.

This means, the page that has your dump of the CGI scope was called via GET, and not POST.  This is where I am getting confused now.

When you request a page, say http://hostname/folder/file.cfm

By default, you are performing a HTTP/1.1 GET /folder/file.cfm

When you are on a page and it has a form, the form's METHOD attribute is looked at as well as the ACTION.  If the method is POST and the action is directory2.cfm, the CGI dump (which should be on THAT page) should perform a:  HTTP/1.1 POST directory2.cfm

But your CGI dump is showing that the page which has the dump was requested by GET.  The FORM dump will NOT show any information unless it is on a page that you POSTed to, ie.

page1.cfm -> Has a <form> with a method="POST" and an action="page2.cfm"

When the user requests http://host/page1.cfm, then they just did: HTTP/1.1 GET page1.cfm

When they fill out the form and submit, the browser performs a: HTTP/1.1 POST page2.cfm

On page2.cfm, there should be a <cfdump var="#FORM#" />

This will be a structure that contains all the form elements (as well as some other info) from the previous page.

That's what I'm expecting to see.

• ###### 35. Re: Folder Directory Create

OK, let's try this.  Make a new page, test.cfm and put this code in it, then browse out to it.

<cfsetting showdebugoutput="false" />

<cfoutput><!DOCTYPE html>

<html>

<meta charset="utf-8">

<title>Example</title>

<body>

<form name="test_form" method="post" action="#CGI.script_name#" enctype="application/x-www-form-urlencoded">

<cfif CGI.content_length gt 0>

<p>A form was posted to this page.  Here is the data ColdFusion captured:</p>

<cfdump var="#FORM#" />

<p>To do that, simply <a href="#CGI.script_name#" title="Click on this link">click on this link.</a></p>

<cfelse>

<p>No form has been submitted yet.  Enter a value into the field below and submit it.</p>

<p>This will perform a HTTP/1.1 POST to this page, populating the ColdFusion FORM scope.</p>

<p><input type="text" name="myValue" id="myValue" /></p>

<p><input type="submit" id="submit" value="POST this to myself" /></p>

</cfif>

</form>

</body>

</html></cfoutput>

Upon visiting the page, you should have a form field.  When you submit the form, it actually POSTS back to itself and then should show you the FORM scope dump of information, providing you with a GET-based link to start all over again.

Does this page show you the information you entered in the input field when you submit it?

• ###### 36. Re: Folder Directory Create

Yes, It asks me to input a value, I put in 1 and then it spits back this:

A form was posted to this page. Here is the data ColdFusion captured:

struct
FIELDNAMESMYVALUE
MYVALUE1

To do that, simply click on this link.

I dont get why my page, which also asks you as the user to input something into it, when I add that dump line to the top, when you navigate to it just comes up with that long list of code I poste previously.

Every file I have is written with POST and not GET.

• ###### 37. Re: Folder Directory Create

OK, well, you CAN set a form's method to GET, it will simply append the values into the URL, for example, that request you made would goto:

test.cfm?myValue=1

From there, you'd dump the URL scope <cfdump var="#URL#" /> in order to capture the values that were sent.

OK, so this proves that form submission is working on your machine.  One thing you may/may not have noticed, is that the code I provided you is 100% HTML5 valid.  I had asked you earlier to validate the code, and you indicated there were a bunch of errors.  Well, we may just want to look into these to ensure that one of them is not gumming up the functionality.

• ###### 38. Re: Folder Directory Create

OKay since page 1 actually doesnt do anything I can skip that, and ill start on page 2 and the other esential code files that actually build the directory.

DIRECTORY.CFM

1. Unable to Determine Parse Mode!
2. The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
3. in Direct Input mode, no MIME Media Type is served to the validator
• No known Document Type could be detected
• No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
• No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
1. As a default, the validator is falling back to SGML mode.
2. No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.

No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.

The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.

Learn how to add a doctype to your document from our FAQ.

3. No Character encoding declared at document level

No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

See this tutorial on character encoding for techniques and explanations.

4. Using Direct Input mode: UTF-8 character encoding assumed

Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator's form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.

If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.

↑ Top

### Validation Output: 27 Errors

1. Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<HTML>

The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

2. Line 3, Column 11: cannot generate system identifier for general entity "I"
 <TITLE>C&I Engineering - Project Directory Wizard</TITLE>

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

3. Line 3, Column 11: general entity "I" not defined and no default entity
 <TITLE>C&I Engineering - Project Directory Wizard</TITLE>

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

4. Line 3, Column 12: reference to entity "I" for which no system identifier could be generated
 <TITLE>C&I Engineering - Project Directory Wizard</TITLE>

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

5. Line 3, Column 10: entity was defined here
 <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
6. Line 10, Column 21: there is no attribute "TEMPLATE"
<CFINCLUDE TEMPLATE="HEADER.CFM">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

7. Line 10, Column 33: element "CFINCLUDE" undefined
<CFINCLUDE TEMPLATE="HEADER.CFM">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
8. Line 11, Column 45: invalid comment declaration: found name character outside comment but inside comment declaration
<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->

9. Line 11, Column 1: comment declaration started here
<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
10. Line 12, Column 35: element "CFINCLUDE" undefined
<CFINCLUDE TEMPLATE="MAINAREA.CFM">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
11. Line 16, Column 3: invalid comment declaration: found name character outside comment but inside comment declaration
--->

12. Line 14, Column 1: comment declaration started here
<!---
13. Line 20, Column 28: there is no attribute "HEIGHT"
<TABLE WIDTH="100%" HEIGHT="100%" BGCOLOR="#D4D0C8">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

14. Line 24, Column 21: there is no attribute "ACTION"
<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

15. Line 24, Column 38: there is no attribute "DIRECTORY"
<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

16. Line 25, Column 10: there is no attribute "NAME"
    NAME="myDirectory"

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

17. Line 26, Column 10: there is no attribute "SORT"
    SORT="Name ASC">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

18. Line 26, Column 20: element "CFDIRECTORY" undefined
    SORT="Name ASC">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
19. Line 27, Column 15: there is no attribute "NAME"
<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

20. Line 27, Column 43: there is no attribute "DEFAULT"
<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

21. Line 27, Column 45: element "CFPARAM" undefined
<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
22. Line 31, Column 17: there is no attribute "QUERY"
<CFOUTPUT QUERY="myDirectory">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

23. Line 31, Column 30: element "CFOUTPUT" undefined
<CFOUTPUT QUERY="myDirectory">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
24. Line 32, Column 12: "TYPE" is not a member of a group specified for any attribute
<CFIF TYPE IS "Dir">

25. Line 32, Column 15: an attribute value literal can occur in an attribute specification list only after a VI delimiter
<CFIF TYPE IS "Dir">

Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

26. Line 32, Column 15: element "CFIF" undefined
<CFIF TYPE IS "Dir">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
27. Line 33, Column 8: an attribute specification must start with a name or name token
 <CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">

An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

28. Line 33, Column 8: element "CFIF" undefined
 <CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
29. Line 35, Column 9: element "CFELSE" undefined
 <CFELSE>

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
30. Line 54, Column 40: element "CFINCLUDE" undefined
<CFINCLUDE TEMPLATE="ACTIONBUTTONS.CFM">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
31. Line 57, Column 7: end tag for "CENTER" omitted, but its declaration does not permit this
</BODY>

• You forgot to close a tag, or
• you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

32. Line 7, Column 1: start tag was here
<CENTER>
• ###### 39. Re: Folder Directory Create

OKay since page 1 actually doesnt do anything I can skip that, and ill start on page 2 and the other esential code files that actually build the directory.

DIRECTORY.CFM

1. Unable to Determine Parse Mode!
2. The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
3. in Direct Input mode, no MIME Media Type is served to the validator

• No known Document Type could be detected
• No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
• No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
1. As a default, the validator is falling back to SGML mode.
2. No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.

No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.

The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.

Learn how to add a doctype to your document from our FAQ.

3. No Character encoding declared at document level

No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

See this tutorial on character encoding for techniques and explanations.

4. Using Direct Input mode: UTF-8 character encoding assumed

Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator's form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.

If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.

↑ Top

### Validation Output: 27 Errors

1. Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<HTML>

The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

2. Line 3, Column 11: cannot generate system identifier for general entity "I"
 <TITLE>C&I Engineering - Project Directory Wizard</TITLE>

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

3. Line 3, Column 11: general entity "I" not defined and no default entity
 <TITLE>C&I Engineering - Project Directory Wizard</TITLE>

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

4. Line 3, Column 12: reference to entity "I" for which no system identifier could be generated
 <TITLE>C&I Engineering - Project Directory Wizard</TITLE>

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

5. Line 3, Column 10: entity was defined here
 <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
6. Line 10, Column 21: there is no attribute "TEMPLATE"
<CFINCLUDE TEMPLATE="HEADER.CFM">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

7. Line 10, Column 33: element "CFINCLUDE" undefined
<CFINCLUDE TEMPLATE="HEADER.CFM">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
8. Line 11, Column 45: invalid comment declaration: found name character outside comment but inside comment declaration
<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->

9. Line 11, Column 1: comment declaration started here
<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
10. Line 12, Column 35: element "CFINCLUDE" undefined
<CFINCLUDE TEMPLATE="MAINAREA.CFM">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
11. Line 16, Column 3: invalid comment declaration: found name character outside comment but inside comment declaration
--->

12. Line 14, Column 1: comment declaration started here
<!---
13. Line 20, Column 28: there is no attribute "HEIGHT"
<TABLE WIDTH="100%" HEIGHT="100%" BGCOLOR="#D4D0C8">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

14. Line 24, Column 21: there is no attribute "ACTION"
<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

15. Line 24, Column 38: there is no attribute "DIRECTORY"
<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

16. Line 25, Column 10: there is no attribute "NAME"
    NAME="myDirectory"

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

17. Line 26, Column 10: there is no attribute "SORT"
    SORT="Name ASC">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

18. Line 26, Column 20: element "CFDIRECTORY" undefined
    SORT="Name ASC">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
19. Line 27, Column 15: there is no attribute "NAME"
<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

20. Line 27, Column 43: there is no attribute "DEFAULT"
<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

21. Line 27, Column 45: element "CFPARAM" undefined
<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
22. Line 31, Column 17: there is no attribute "QUERY"
<CFOUTPUT QUERY="myDirectory">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

23. Line 31, Column 30: element "CFOUTPUT" undefined
<CFOUTPUT QUERY="myDirectory">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
24. Line 32, Column 12: "TYPE" is not a member of a group specified for any attribute
<CFIF TYPE IS "Dir">

25. Line 32, Column 15: an attribute value literal can occur in an attribute specification list only after a VI delimiter
<CFIF TYPE IS "Dir">

Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

26. Line 32, Column 15: element "CFIF" undefined
<CFIF TYPE IS "Dir">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
27. Line 33, Column 8: an attribute specification must start with a name or name token
 <CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">

An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

28. Line 33, Column 8: element "CFIF" undefined
 <CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
29. Line 35, Column 9: element "CFELSE" undefined
 <CFELSE>

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
30. Line 54, Column 40: element "CFINCLUDE" undefined
<CFINCLUDE TEMPLATE="ACTIONBUTTONS.CFM">

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

• incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
• by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
• by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
31. Line 57, Column 7: end tag for "CENTER" omitted, but its declaration does not permit this
</BODY>

• You forgot to close a tag, or
• you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

32. Line 7, Column 1: start tag was here
<CENTER>
1 2 Previous Next