philip1989
Members
-
Joined
-
Last visited
Everything posted by philip1989
-
I set the max cost per click for my ad to be 50 cents but then they've got a results page saying website clicks and it shows as $1. Isn't that just a con? Cost per click should be the click to your website shouldn't it?
-
with the 2 forward steps and a backward step, or even more than 2 forward steps if needed. Off the top of my head then ExpressionEngine or Craft will do this with out of the box tools, all you'd need to do is set up your data entries and add data fro each town (including video clip, descriptions, variable, values, related forward steps etc. Personally I could set up the basic content structure in ExpressionEngine in 10 minutes. Thank you very much Blue Dreamer, It's ok i won't do all the towns, i'd just do say, manchester and london, make about 20 videos clips and that's it. It probably wouldn't work, i just didn't know what to call that idea that i had and if anything was out there, i'm greatful for your links and i'll have a look tommorrow. I might just do a simple film in their local area which would entice them to watch the film. If it's a Failure then i still have footage for my other website that is a clips for sale sort of place.
-
Hello guys I'm trying to make a sort of film/game thriller, which will have nearly every town in the UK, basically the person will have to get from one point to the other. They'll select which way to go out of 2 choices, then during the video walking they'll come to another point where they have to decide whether to do something else. this will end up either they are safe or they are not. Then they'll progress further into the website. I'll film in locations on a tripod and have an actor with green screen. I'm just wanting to know what software i would need/how much, i'm happy to learn new things to keep costs down. I basically have the oldest web software, web serif from 2007 around abouts. I am always sceptical about spending more than $60 for software.
-
Thank you James
-
I used serif webplus (2007-ish) OK I've cleaned up the HTML But now I have 15 errors (down from 30) Validation Output: 15 Errors Line 94, Column 14: end tag for "map" which is not finished </map></p><img src="_wp_generated/wp140a2763.png" width="359" height="7… ✉ Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p> Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on. Line 95, Column 74: there is no attribute "onload" …" id="art_1" name="art_1" title="" alt="wp140a2763.png" onload="OnLoadPngFix()" ✉ 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 101, Column 49: there is no attribute "webkitallowfullscreen" …frameborder="0" webkitallowfullscreen="" mozallowfullscreen="" allowfullscreen… ✉ 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 101, Column 71: there is no attribute "mozallowfullscreen" …frameborder="0" webkitallowfullscreen="" mozallowfullscreen="" allowfullscreen= ✉ 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 102, Column 11: there is no attribute "allowfullscreen" ""></iframe> ✉ 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 115, Column 23: required attribute "id" not specified <map name="map1"> ✉ 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>. Line 116, Column 76: required attribute "alt" not specified <area shape="poly" coords="83,0,0,0,0,42,83,42" href="page5.html" /> ✉ 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>. Line 126, Column 23: required attribute "id" not specified <map name="map2"> ✉ 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>. Line 128, Column 48: required attribute "alt" not specified "mailto:philip@shiresvideography.com" /> ✉ 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>. Line 257, Column 27: there is no attribute "data-show-count" data-show-count="false" data-lang="en">Follow @@philipshires1</a> <sc… ✉ 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 257, Column 45: there is no attribute "data-lang" … data-show-count="false" data-lang="en">Follow @@philipshires1</a> <script … ✉ 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 264, Column 23: there is no attribute "data-pin-do" data-pin-do="buttonPin" data-pin-config="above"><img src= ✉ 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 264, Column 51: there is no attribute "data-pin-config" data-pin-do="buttonPin" data-pin-config="above"><img src= ✉ 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 265, Column 81: required attribute "alt" not specified … "//assets.pinterest.com/images/pidgets/pinit_fg_en_rect_gray_20.png" /></a> ✉ 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>. Line 267, Column 49: there is no attribute "async" <script type="text/javascript" async="" src= Thanks