Hi
I have html editor 2007 and am running on windows xp.

I don't know how to fix this validation on a photo slideshow I created in a google web album. It said to copy and paste this in my webpage:
<embed type="application/x-shockwave-flash" src="http://picasaweb.google.com/s/c/bin/slideshow.swf"
width="600" height="400" flashvars="host=picasaweb.google.com&amp;noautoplay=1&amp;RGB=0x000000&amp;feed=http%3A%2F%2Fpicasaweb.google.com%2Fdata%2Ffeed%2Fapi%2Fuser%2FLauriefwc1%2Falbumid%2F5257947290441391569%3Fkind%3Dphoto%26alt%3Drss%26authkey%3DOwQfRhfsK5I"
pluginspage="http://www.macromedia.com/go/getflashplayer"></embed>

Below is the validation errors I got, not sure what to do??

Validation Output: 7 Errors
Line 95, Column 12: there is no attribute "TYPE".
<embed type="application/x-shockwave-flash" src="http://picasaweb.google.com/s/c✉

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.

Line 95, Column 48: there is no attribute "SRC".
…="application/x-shockwave-flash" src="http://picasaweb.google.com/s/c/bin/sli✉

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.

Line 96, Column 7: there is no attribute "WIDTH".
width="600" height="400" flashvars="host=picasaweb.google.com&amp;noautoplay=1&✉

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.

Line 96, Column 20: there is no attribute "HEIGHT".
width="600" height="400" flashvars="host=picasaweb.google.com&amp;noautoplay=1&✉

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.

Line 96, Column 36: there is no attribute "FLASHVARS".
width="600" height="400" flashvars="host=picasaweb.google.com&amp;noautoplay=1&✉

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.

Line 97, Column 14: there is no attribute "PLUGINSPAGE".
pluginspage="http://www.macromedia.com/go/getflashplayer"></embed>✉

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.

Line 97, Column 59: element "EMBED" undefined.
pluginspage="http://www.macromedia.com/go/getflashplayer"></embed>✉

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).

Laurie,

One interesting thing about validation is that the first error can effect the rest of the document causing false errors to be listed. Also is the fact that the first error may not have been the first error in the document.

The first error in your document was the doctype. Since you are using frames you need to use the doctype for framesets. So assuming you are using HTML, change your doctype to:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frameset.dtd">

You can find all the proper doctypes at: http://www.w3.org/QA/2002/04/valid-dtd-list.html

After that making the doctype change, see how your code validates.

If you are actually using XHTML, be sure all your tags are lowercase and get the XHTML frameset doctype at the link I gave for doctypes.

Then you can begin tackling any errors that are left. Also understand that if you want to use some specific code, it may not validate (<embed> may not validate).

Standard flash code has never passed validation with the W3C. The only way to get your page to validate with flash is to use javascript code and a little java to play the flash, so that the flash code stays hidden. That way, the java passes the validation test.
The easiest way to accomplish this:
In the photo gallery settings tab,
put checkmark in the "fix for active content" box.
save your file

Now look at the code provided. It won't be the same code, and you will have to upload all the files including the "swfobject.js" file, which is the javascript that will handle displaying the flash on your page. The new code that you put onto your page will validate, providing you have changed your doctype and followed the other suggestions from Bill R.

Morning
Thank you for your quick reply. This is what is at the top of my page in my website:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

Do I only change this page header to what you're saying or do I change all my other web pages? All other pages validate fine right now. It's just my Photo page with this new google embed web album slideshow that doesn't validate.
Thank you again for your quick response.

I am jumping back in here to correct a missunderstanding...I hope..

Bill R. You stated about changing the doctype based on the first error. It's not the doctype that is the error, but the word "type" in the code for the flash application. The validator has picked up on this word incorrectly, and assumed that the web page may be using a different doctype other than what is stated. It is a common error of the validator to pick on the wrong "fix" if it doesn't know what needs to be fixed.

In my opinion, Laurie, you don't need to change the doctype at all, yours if fine.
I also missunderstood, and thought you had used the CoffeeCup Photo Gallery as your slide show, and that's why I suggested using the "fix for active content" checkbox, which is probably not a feature of the program you used.

Laurie, your choices are to just leave it the way it is...it won't hurt your page, the code works fine, millions of other websites use the exact same code, including big companies because there's no easy way around it.
or
do a google for swfobject.js, find a website with good instructions and implement all the changes they suggest, using the swfobject.js file to handle your flash slideshow, and any other flash you use on your pages.

One last note: there are a lot of cheap gimmicky "solutions" for fixing active content that say they validate...they (almost) all have flaws, mess things up and don't really work well at all. The only one I trust is swfobject.js

Thanks so much Cliff. I will leave it as is....I have learnt so much here but am far from being an expert on html. You guys helped me out back in april with a similar issue with google video and the embed deal. I am helping a friend with a hockey website and trying to keep it as simple as possible and my time for updating it is free so thought using the google storage area was easier than tying up bandwith etc with video. Now they have this web album slideshow so thought I would try it. You sent me a link to a great article by Liz castro on the "bye bye embed" and I reviewed it thinking it would help me with the photo slideshow but didn't relate totally but worked with the video validation.

Thanks again, your ROCK!!

Cliff,

You may be correct. I know that a lot of pages have frames from Google, and the last paragraph in the first message stated:

"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)"

I may well have jumped to an incorrect conclusion.

It really would help to have a link to the site to actually see what is happening. Even a link to the validation for the site would have shown the exact wording on the message and what triggered the message.

With a closer reading of the first message, I think I agree with you.

Hi Bill
I haven't uploaded it yet because of the invalid validation. I am about to do it now and see what happens.

http://www.stoneycreekjrsabres.ca/photos.html
this is where it is.

I wouldn't let the validation thing stop you from using flash or google slideshows on your site. I often click the "W3C validated" logo at the bottom of some web pages, only to find that they have "57 errors", but they still put the validation logo and link on their site to say that they use compliant code. Just because the W3C does not validate, does not really mean that it is wrong or that it will fail. All modern web browsers support standard flash code, but that code will not validate because of the <embed> tag.
I think the W3C should change it's standards, which would correct millions of websites from not validating because of how flash needs to be coded differently for I.E. than it does for any other web browser.

BTW, nice pictures.