Copy link to clipboard
Copied
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.
I also have downloaded Coldfusion builder also.
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
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:
<a href="Click" _mce_href="http://sharepoint13.com/Divisions/ENGTECH/ProjectDirectoryWizard/DIRECTORY.CFM">Cl... here to go to page b.</a>
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.
Copy link to clipboard
Copied
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:
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?
Copy link to clipboard
Copied
Yeah this Adobe log in error is crazy, Its kept me locked out all day.
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.
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
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_PASSWORD [empty string]
AUTH_TYPE NTLM
AUTH_USER DOMAIN\USER
CERT_COOKIE [empty string]
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_COOKIE MSOWebPartPage_AnonymousAccessCookie=80; WSS_KeepSessionAuthenticated=80
HTTP_HOST Sharepoint13.com
HTTP_REFERER http://sharepoint13.com/Divisions/ENGTECH/index.htm
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_ADDR X.X.X.X
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]
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
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="HEADER.CFM">
<!---<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>
<A HREF="./addnewclient.cfm">Add New Client</a> (if not listed)<br>
<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_PASSWORD | [empty string] |
AUTH_TYPE | NTLM |
AUTH_USER | DOMAIN\USER |
CERT_COOKIE | [empty string] |
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_COOKIE | MSOWebPartPage_AnonymousAccessCookie=80; WSS_KeepSessionAuthenticated=80 |
HTTP_HOST | Sharepoint13.com |
HTTP_REFERER | http://Sharepoint13.com/Divisions/ENGTECH/index.htm |
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_ADDR | 10.1.8.147 |
REMOTE_HOST | 10.1.8.147 |
REMOTE_USER | DOMAIN\USER |
REQUEST_METHOD | GET |
SCRIPT_NAME | /Divisions/ENGTECH/ProjectDirectoryWizard/dir_startup.cfm |
SERVER_NAME | intranet.cieng.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] |
---|
And here is the code for said Dump:
<HTML>
<HEAD>
<TITLE>C&I Engineering - Project Directory Wizard</TITLE>
</HEAD>
<BODY>
<CENTER>
<CFINCLUDE TEMPLATE="HEADER.CFM">
<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
<CFINCLUDE TEMPLATE="MAINAREA.CFM">
<!---
Main Content
--->
<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>
<A HREF="./addnewclient.cfm">Add New Client</a> (if not listed)<br>
<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>
Copy link to clipboard
Copied
Look at your CGI dump.
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.
Copy link to clipboard
Copied
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>
<head>
<meta charset="utf-8">
<title>Example</title>
</head>
<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>I can now, re-request this page without the submitted form data by performing a HTTP/1.1 GET of this page</p>
<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?
Copy link to clipboard
Copied
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 | |
---|---|
FIELDNAMES | MYVALUE |
MYVALUE | 1 |
I can now, re-request this page without the submitted form data by performing a HTTP/1.1 GET of this page
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.
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
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
<?xml version="1.0"?>
) could be found at the beginning of the document.<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
) could be found at the root of the document. 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.
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.
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.
<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.
<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 "&" (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 æ 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.
<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.
<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.
<TITLE>C&I Engineering - Project Directory Wizard</TITLE>
<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.
<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:
<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
<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:
--->
<!---
<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.
<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.
<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.
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.
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.
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:
<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.
<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.
<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:
<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.
<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:
<CFIF TYPE IS "Dir">
<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"
.
<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:
<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).
<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:
<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:
<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:
</BODY>
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.
<CENTER>
Copy link to clipboard
Copied
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
<?xml version="1.0"?>
) could be found at the beginning of the document.<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
) could be found at the root of the document. 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.
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.
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.
<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.
<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 "&" (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 æ 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.
<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.
<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.
<TITLE>C&I Engineering - Project Directory Wizard</TITLE>
<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.
<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:
<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
<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:
--->
<!---
<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.
<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.
<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.
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.
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.
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:
<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.
<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.
<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:
<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.
<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:
<CFIF TYPE IS "Dir">
<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"
.
<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:
<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).
<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:
<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:
<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:
</BODY>
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.
<CENTER>
Copy link to clipboard
Copied
WHOOPS Yeah I did that. Here Ill update the old post.
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:
<?xml version="1.0"?>
) could be found at the beginning of the document.<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
) could be found at the root of the document.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.
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.
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.
<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.
<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 "&" (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 æ 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.
<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.
<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.
<TITLE>C&I Engineering - Project Directory Wizard</TITLE>
<STYLE>
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type
are type="text/css"
for <style>
and type="text/javascript"
for <script>
.
<STYLE>
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
<td bgcolor=#0A246A align=left valign=top background="./images/topbarbg.jpg">
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
<td bgcolor=#0A246A align=left valign=top background="./images/topbarbg.jpg">
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.
…="White" face="arial"><p class="title"><b> Project Directory Setup</b></f…
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
<td bgcolor=#D4D0C8>
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
<IMG SRC="./IMAGES/LEFTSIDE2.JPG">
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type
are type="text/css"
for <style>
and type="text/javascript"
for <script>
.
<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.
<OPTION VALUE="LG&E">LG&E
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 "&" (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 æ 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.
<OPTION VALUE="LG&E">LG&E
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.
<OPTION VALUE="LG&E">LG&E
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.
<OPTION VALUE="LG&E">LG&E
<OPTION VALUE="LG&E">LG&E
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.
<OPTION VALUE="LG&E">LG&E
<OPTION VALUE="P&G">P&G
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 "&" (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 æ 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.
<OPTION VALUE="P&G">P&G
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.
<OPTION VALUE="P&G">P&G
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.
<OPTION VALUE="P&G">P&G
<OPTION VALUE="P&G">P&G
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.
<OPTION VALUE="P&G">P&G
</TR>
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. <FORM ACTION="DIRECTORY2.CFM" METHOD="POST">
</TR></TD>
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. <TABLE WIDTH="100%">
</FORM>
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
</BODY>
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. <TABLE BORDER=".5" CELLPADDING="3" BGCOLOR="#D4D0C8" WIDTH="550">
</BODY>
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. <CENTER>
Copy link to clipboard
Copied
Are you attempting to validate page code? You cannot validate page code, you need to render the page by navigating to it in a browser and then taking the code that was generated and pasting that into validation services.
Many browsers use CTRL + U as a shortcut, otherwise look at it's VIEW menu for "Page Source" or the equivalent. Then take that and validate it.
Copy link to clipboard
Copied
Yeah thats exactly what I did! whoops! I updated my old post
Copy link to clipboard
Copied
OK, so the page seems to be dumping XML. Rather than a DOCTYPE being specified first, it shows the XML DTD.
Remind me, if you just navigate out the the second page directory (don't go through the first page and submit a form, just request the second page directly) Do you still get a blank page?
Or do we only get the blank page on the second page once we visit the first and then submit a form through to it?
My thought is this. If you can just GET the second page, and something other than a white page generates, then I think it would behoove us to bring this application up to HTML5 standards as a process of elimination.
Copy link to clipboard
Copied
I can put ANY other source code from any of the other files I have, and dump it into the first page that we navigate to (dir_startup) It doesnt matter what source page code I put in there, That first page we navigate to will always show up. BUT it doesnt matter what I input into the form, when I click the "next" button the following page will be white, and whatever form I filled out will not process.
Im thinking the same thing to about recoding it. I mean I really just need this main directory page up and working and thatll give me some breathing room to fix the rest. I know enoough I should be able to get the generic page going to where it pulls the directory list from the network drive and presents it in a drop down box, allows the user to select a directory, and then in a textbox name a NEW project, click next and use another template file to generate the directory.
I was doing this the other day just on the first page and I guess this is what confused me. Heres the code:
<CFFORM ACTION="DIRECTORY.CFM" METHOD="POST" enctype="text/plain">
<TITLE>Directory Wizard</TITLE>
<CENTER>
<CFINCLUDE TEMPLATE="HEADER.CFM">
<CFINCLUDE TEMPLATE="MAINAREA.CFM">
Welcome to the Project Directory setup program
<BR><BR>
This web-based wizard helps you to create the appropriate directories
for a particular project.
<BR><BR>
Please click Next to continue
<BR><BR>
<cfinput type="Submit" name="formsubmit" value="NEXT">
</CFFORM>
The Page comes up just fine. Just to test it, I made the second page DIRECTORY.CFM but I just copied this code and placed it in there, Thinking Ill click next, and itll take me to the next page but it will look exactly as the first, just to break this whole (the next page is always blank white) streak Im having, but It still is just blank white. How can the first page come up fine, and the second page which has the EXACT same source code not load when scripted? Am I missing something?
Copy link to clipboard
Copied
UPDATE
Im not sure if this is useful information or not but Im just trying different options now to see what happens.
At the moment In my ColdFusion webserver configuration Tool, I have IIS: All, now If i go through the configuration tool, and select my website specifically "Sharepoint13" Let the servers restart, My jakarta folder gets mapped to the number "2" now instead of 1, I go to navigate to my project directory wizard, instead of a blank white page I get a Cannot display this webpage when I click the next button. I go back and remove my website from the configuration tool, the servers restart, My jakarta folder gets mapped back to the number "1" and it goes back to the blank white page when I click next.
Copy link to clipboard
Copied
So you keep posting <cfform> tags. But we verified that <form> tags DO submit data. When CF uses a <cfform> tag, it attempts to embed some javascripts from its scripts folder in order to assist in CFFORM-proprietary functionality. Is there a reason why you're using <cfform>?
As far as the '1' and '2' folder, these are numerically created each time you run the connector script. If your IIS site's jakarta folder is not mapped to an actual numeric folder, which contains an isapi_redirect.dll file, then it cannot process CF pages, and you'll get that error. Ensure this is correctly setup. Before, you arrived on page 1, which was a .cfm, and it at least showed up; this means, at this point, you have things set properly.
Any why is the ENCTYPE now being set to "text/plain"!?! This should be:
enctype="application/x-www-form-urlencoded"
If these values are NOT being set properly, the mime type of the data that is being set and sent to the action page will not be properly interpreted. A text/plain value will not encode any special characters that may have been provided. Please update the page accordingly.
As for the next step, I'm going to have to hold firm that we need to bring at least the first 2 page's of this wizard up to code. You used my code, which self-referenced and submitted data to itself. It was HTML5 valid, and you even said that it worked exactly as intended. You may want to hop into the CF Admin and take a look at the error logs to see if there's any information you can gather when you attempt your wizard, but my code proves that, if properly coded, form submission and ColdFusion were both working fine.
Copy link to clipboard
Copied
Im not sure why I was using CFform, I just thought it had to be that way, I was reading to far into things when I was visiting other websites. So this is the code to my first page. Basic yes. But I still get some errors when I check the source code Validation. But to you does this look right? I feel I dont have the eye for whats wrong if the page still displays.
Also I still get a white page when I click next, Does the second page have to be coded specifically to accept being called upon form this code?
<cfoutput><!DOCTYPE html>
<FORM ACTION="DIRECTORY.CFM" METHOD="POST" enctype="application/x-www-form-urlencoded">
<TITLE>Directory Wizard</TITLE>
<CENTER>
Welcome to the Project Directory setup program
<BR><BR>
This web-based wizard helps you to create the appropriate directories
for a particular project.
<BR><BR>
Please click Next to continue
<BR><BR>
<input type="Submit" name="formsubmit" value="NEXT">
</FORM>
</cfoutput>
VALIDATION Errors:
Line 2, Column 87: Element head is missing a required instance of child element title.
…TION="DIRECTORY.CFM" METHOD="POST" enctype="application/x-www-form-urlencoded">
Line 4, Column 7: Element title not allowed as child of element form in this context. (Suppressing further errors from this subtree.)
<TITLE>Directory Wizard</TITLE>
Line 6, Column 8: The center element is obsolete. Use CSS instead.
<CENTER>
Line 16, Column 7: End tag form seen, but there were open elements.
</FORM>
Line 6, Column 8: Unclosed element center.
<CENTER>
Line 16, Column 7: Cannot recover after last error. Any further errors will be ignored.
</FORM>
Copy link to clipboard
Copied
I just cant figure out why none of my pages want to transition from one to the next when clicking the "Next" button, Its becoming very frustrating. No matter how basic I make these test pages, they still refuse to work.
Copy link to clipboard
Copied
The reason why the code you presented is not validating stems from the following issues:
The first thing you need to output (NO CODE can exist before this, not even spaces, is the doctype, and you do this just fine with:
<cfoutput><!DOCTYPE html>
Perfect. But you then go right into creating a FORM tag, which cannot exist at that location. Here, let me help and provide comments as well...
<!--- Output the <!DOCTYPE> immediately after the <CFOUTPUT> --->
<cfoutput><!DOCTYPE html>
<!--- We need to specify the ROOT element, which for HTML, is the <html> element. --->
<html>
<!--- We need to create the <head> tag, which encapsulates all page meta, such as character encoding and the title. --->
<head>
<!--- The first thing we need to do is ensure the page encoding is set. --->
<meta charset="utf-8">
<!--- Now we can create a <title>, inside the <head>, where it belongs. --->
<title>Directory Wizard</title>
</head>
<!--- The <body> tag needs to exist, as it contains the content of the page that is not meta <head> data. --->
<body>
<!--- Here, we can create our <form> tag, though be in a habit to give it a NAME attribute. --->
<form name="wizard" action="directory.cfm" method="post" enctype="application/x-www-form-urlencoded">
<!--- I won't go into the long of it, but style properties should REALLY be stored in a CSS file.
For the time-being we will use them as inline attributes to center your text. --->
<p style="text-align: center;">Welcome to the Project Directory setup program.</p>
<hr>
<p style="text-align: center;">This web-based wizard helps you to create the appropriate directories for a particular project.</p>
<hr>
<p>Please click NEXT to continue.</p>
<hr>
<!--- And here we output our form submit button. --->
<p><input type="submit" name="formsubmit" value="NEXT"></p>
</form>
</body>
</html></cfoutput>
This code contains what content you had, but is HTML5 valid. Test it out and let me know the results (I assume directory.cfm is the SAME page as the one you're pasting this content into, right? If not, write the following code at the top of the directroy.cfm file:
<cfdump var="#FORM#" abort="1" label="This is the data posted to the directory.cfm page" />