Podcast fails validation no closing meta tag

I have been working on this and cannot figure it out. I have a podcast that passes all validation pages. Works in Feed burner and other RSS readers. Hoever when I subscribe to the podcast in itunes it is broke. When I submit a podcast it says I do not have a closing </meta> tag, but there is not meta tag in the feed. This has got to be bug in iTunes.
my feed is http://www.fairview4u.org/index.php/follow-us

Your feed includes the following tag:
<itunes:new-feed-url>http://www.fairview4u.org</itunes:new-feed-url>
This redirects iTunes, but nothing else (which is why validators are working and the feed looks OK in a browser). This is redirecting iTunes to your web page which obviously isn't going to work. You need to remove this tag.

Similar Messages

  • HTML5 Meta Tag issue

    I have a site that is built using Project 7's Affinity Page Builder in HTML5 with a meta tag that seems to cause problems with the W3C Validator.
    The meta tag is this:
    <meta http-equiv="X-UA-Compatible" content="IE=Edge">
    The Website is here:
    http://www.bobbybailbonds.net/
    Client liked the Affinity theme, Al Sparber earned his pay. But what's with the meta tag? I understand this causes Internet Exploder to not freak out when dealing with this kind of responsive layout. And I also came across a description of this as a bug in the W3C group: http://lists.w3.org/Archives/Public/public-html-admin/2013Mar/0009.html
    First question: Is there an alternative that will specifically work with Microsoft's browsers?
    Second question: Is this something that will be a known fix that is upcoming?
    Third: What happens when this is left out? What do the Microsoft browsers do?
    -Mark

    Oh, Nancy!
    I don't do Windows.
    (You did ask for this, you know)
    If you read the article, there is a php solution in the header of each page. I, personally, do like the universal solution—use it once, all pages on that web server are done.
    I had one client on an IIS server and pulled him off it. I uploaded a whole bunch of .PNG files and there were a few .PDFs that my client wanted linked. The server didn't know what the .PNG files were and didn't know what the .PDFs were, either, so it refused to serve them. Hosting provider was so slow with tech support that I pulled the site (and put it on Linux/Apache) before he got back to me. Apparently, you have to tell Windows that these are OK files to host.
    Sheesh!
    -Mark

  • RSS - 'META' tag not closed

    Hi there,
    Another newbie question for everyone. I created my own RSS
    feed in cf and, to my surprise, it seemed to work. I tested it
    locally, tweaked it to my needs, and then when I uploaded it to the
    main site, it blew up. Here's the message the feed gave:
    The following tags were not closed: META.
    Line: 0 Character: 0
    Hrmm, great. So it worked, sans message, locally, and then
    choked up in the big pond. My first thought is that it's a problem
    with my web server. Being new to this and not all that hardcore,
    that leaves me in a bit of a fix as I have no clue how to deal with
    a . Two questions. 1) Is this a common problem, and if so how do I
    resolve it? Please be detailed, if possible :) 2) Is there an
    easier way to set up a feed? See my code below for the fruit of my
    mucking about.
    Thanks in advance.

    The following tags were not closed: META.
    I think you used no license product, it will add this tag on
    the top of
    your page
    <META NAME="ColdFusionMXEdition" CONTENT="ColdFusion
    DevNet Edition -
    Not for Production Use.">
    Be carefull!!!!! That's the reson why you have that error
    It sounds like Droopers got the answer s/he needed. But for
    archive
    purposes, there is another reason that one can get a result
    like this.
    It happens if one has IIS security configured on the resource
    generating
    the RSS/webservice XML. When one access the resource directly
    it works
    correctly because the user's creditionals are provided. But
    when
    accessed remotely without these creditionals, a HTTP error
    page is
    returned and this error page is not valid XML and this type
    of error is
    reported.

  • Best practice for implementing META tags for content items?

    Hello,
    The portal site I'm responsible for managing our content (www.sers.state.pa.us) runs on the following WebCenter products:
    WebCenter Interaction 10.3.0.1
    WebCenter Publisher 6.5
    WebCenter Studio 2.2 MP1
    Content Service 10gR3
    The agency I work for is one of many for the commonwealth of PA, which use this product suite, and I'm encountering some confusion on how to apply META tags to the content items for our site, so we can have effective search results. According to the [W3C site's explanation on META tag standards|http://www.w3schools.com/tags/tag_meta.asp], the tags for description, keywords, etc, should be within the head region of the HTML document. However, with how the WebCenter suite's configuration is set up, the head section of the HTML is closed off by the end of the template code for a common header portlet. I was advised to add fields to our presentation and data entry templates for content, to add these meta fields, however, since they are then placed within the body section of the HTML as a result, these tags fail to have any positive impact on the search results. Instead, many of our content items, when searched for, the description in the search results only shows text that is displayed in the header and left navigation of our template, which come early in the body section of the HTML.
    Please advise as to possible method(s) that would be best to implement usage of META tags so we can get our pages containing content to come up in search results with this relevant data.
    Thanks in advance,
    Brian

    if i remember right the index server will capture meta tags even if they are not in the <head> section. it is not well formed html but I think i remember that we created meta tags down in the body section and the index server still picked them up. you might try this and see if it still works. i believe it worked in 10gR3. Let me know your results.

  • XML doesnt gets validated because closed element

    Hi,
    I have a working map which looks like below:
    My question is about the party part. What i do i check for every GLN value in the source is the value is bigger than zero. If that is true then map the value to the gln in the destination element AND add a qualifer value which is hardcoded in the value mapping
    functoids.  
    Everything is working fine but the end xml doesnt get validated because of the next reason:
    error btm1046: Output validation error: The element 'party' has incomplete content. List of possible elements expected: 'qual'.
    I think it has to do with the closed party tag which is caused by one of the fields in the source that has a value 0. 
    How can i fix this issue so that my xml gets validated.

    Hi,
    Please check the 'qual' field in your destination/output schema is a mandatory field. The error you are receiving is because in the output the last party tag is empty wherein it is expecting the element tag 'qual' to be present. Hence, failing in the validation.
    Check if you can set that element 'qual' non-mandatory.
    Rachit
    Please mark the post answered your question as answer, and mark other helpful posts as helpful, it'll help other users who are visiting your thread for the similar problem

  • PDF properties (meta tags) can't be changed (error 0x80040154 - class not registered)

    Hello,
    Changing PDF properties (meta tags: author, title, comment, theme etc) in  Adobe Reader as well as in Windows Explorer are disabled rsp does not funtion.
    1. In Adobe Reader "File properties", the overwriting rsp insertion of text is disabled in grey.
    2. In Windows  Explorer, following message window appears: "Properties change: Due to an unexpected error, properties can't be changed - Error  0x80040154: class not registered"
    (Sorry for the bad translation, but I am running the German version)
    Is there a technical explanation and  solution for this problem? In other PDF programms, the change of meta data does work fine.
    =====================
    Windows 7 64-bit, Acrobat Reader X 10.1.1. (Standard PDF Viewer)
    =====================
    Many thanks & best regards
    adiflis

    @MadEyes: I found out you had to set a site address in wordpress the hard way, i set it for a dns host and I couldn't get into the wp-admin page or load any sort of image or css.
    At the moment i have a server root directory with a wordpress folder on it. Eg:
        (/srv/http)/wp/
    and a  test index file in the root. Eg:
        (/srv/http)/index.html
    The index file doesn't show up publicly, but it will on the local network.
    I set the apache port back to 61669 and tested with canyouseeme.org. I got (i will email you the ip addy):
        Success: I can see your service on X.X.X.X on port (61669)       >EDIT: If I close apache, then it fails. Start it back up, it succeeds.
        Your ISP is not blocking port 61669
    I also nmap'd myself and got this:
        Host is up (0.025s latency).
        Not shown: 996 closed ports
        PORT     STATE    SERVICE
        23/tcp   open     telnet
        5989/tcp open     wbem-https
        6881/tcp filtered bittorrent-tracker
        8080/tcp open     http-proxy
    A port forward is definitely set up, so i dont know how much I can trust this (I did make 6881, but them program isn't open).
    Any of this any help?
    >EDIT: Excerpt from Webmin: "System hostname    localhost.localdomain" this doesn't seem right.
    Localhost:
    #<ip-address>   <hostname.domain.org>   <hostname>
    127.0.0.1       localhost.localdomain   localhost  ablanck
    #::1            ablanck.localdomain     localhost
    Last edited by lucytheboydog (2011-02-07 04:34:24)

  • Can't get a web page to validate with meta tags with w3c??

    I have created a website for my school projects, and every week I have to add something to it for the course, and every monday I have to submit my code in a zipped folder to the professor, after running it through the w3c validation page, and passing, This current week, I was instructed to swork on SEO for my site, and add meta tags to the site to fish for traffic, and then I have to validate it through w3c and submit. Well, I did not complete this because w3c would not validate my page until I removed every single meta tag from the code, and I cannot for the life of me understand the error that is holding me back. So, in an effort to see if I could get some help here, I have included my code, and will try to explain what is happening and the code as well as the error from the validator service. Please have a look, help me, because I am totally lost here....
    Thanks in advance!!
    zlloyd1
    This is my code:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>zlloyd on the web</title><meta name="" content="Zachariah Lloyd, basketball, computers" /><meta fttp-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <link rel="stylesheet" type="text/css" href="stylez.css" />
    </head>
    <body><div id="container"><h1>ZLLOYD ON THE WEB</h1> <div id="navbar"><a href="about.html">About me</a> <a href="OceanView.html">Ocean View</a> <a href="swimming.html">Swimming</a> <a href="gaming.html">Gaming</a> <a href="BBall.html">Basketball</a></div><div><a href="gaming.html"><img src="images/Gaming-Desktop-Configuration.jpg" width="107" height="239" alt="console" /></a><a href="BBall.html"><img src="images/300px-Basketball_pictogram.svg.png" width="82" height="76" alt="BallinGuy" /></a><a href="swimming.html"><img src="images/swimming.jpg" width="100" height="237" alt="Strokin" /></a></div></div>
    <a href="contactsupport.html">Support </a>
    </body>
    </html>
    and this is what w3c says when I try to validate the page:
    Line 5, Column 131: there is no attribute "fttp-equiv"
    …mputers, swimming" /><meta fttp-equiv="Content-Type" content="text/html; chars…

    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.
    What in the world does this mean, because I am seriously lost on this, and the only way I could get around this was to completely remove the entire line, "<meta name="" content="Zachariah Lloyd, basketball, computers" /><meta fttp-equiv="Content-Type" content="text/html; charset=UTF-8" />", which removed all of my meta tags completely, in order to validate it?? I cannot see what is setting this thing off like that, I have never gottena validation error before, and I now know that they are written as meaningless gibberish that does not even remotely explain what is wrong, at least not to me....
    Please help!!!!

    Line 4 and line 5 are trying to do the same thing. Take out the
    <meta fttp-equiv="Content-Type" content="text/html; charset=UTF-8" />
    line entirely and you will be good.

  • Invalid meta tag generated when using XHTML method

    Hi,
    I'm trying to generate an XHTML file using XSL and the XHTML output method. However, transformation results in adding the following XHTML-invalid meta tag (uppercase and non-closing) in the head tag:
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
    Is it a bug in the XDK or am I missing something? Transform is performed using the JXTransformer provided in 11g.
    Thanks in advance,
    Stephane
    input file:
    <?xml version='1.0' encoding='utf-8'?>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xml:lang='en' lang='en' xmlns='http://www.w3.org/1999/xhtml'>
    <head>
         <title>Some title</title>
    </head>
    <body></body>
    </html>
    xsl file:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="2.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:xhtml="http://www.w3.org/1999/xhtml">
         <xsl:output method="xhtml"
    doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"/>
    <xsl:template match="*">
         <xsl:element name="{local-name()}" namespace="http://www.w3.org/1999/xhtml">
              <xsl:apply-templates />
         </xsl:element>
    </xsl:template>
    </xsl:stylesheet>
    output:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    *<META http-equiv="Content-Type" content="text/html; charset=UTF-8">*
    <title>Some title</title></head><body></body></html>

    For some reason when I use MapForce tool to generate my xslt mapping source, it is generating the following statement in the xsl file.
         <xsl:namespace-alias stylesheet-prefix="n" result-prefix="#default"/>
    So at the root element of XML file, it is replacing the character n with '#default' for some reason, I don;t know the purpose of this.
    As you suggested, I changed the name space, still I experienced same problem.
    It is now resolved after removing the above xsl statement from the xsl file before creating/uploading the relevant zip file into archives folder.
    It works fine now. Thanks for the clue.

  • Are the META tags in a pdf file visible by search engines?

    I have several hundred newsletters in pdf format on a website.
    I am in the process of entering META tag information (title,description,keywords) through the Properties panel of each pdf file. Is this information that will be visible by search engines in a WordPress site?
    I ask, because every post in WordPress has a place to enter keyword tags. The problem I'm having in WordPress is that every post shows the tag information rather than making it invisible. If the properties information in the pdf file does the same thing, I won't bother with entering it again in WordPress.
    Thanks to anyone who might have insight into this question.
    Many thanks!

    It is a high order probability that your SQL's report generator is creating the PDF, not Acrobat (which by design and EULA cannot be used in as/with server).
    That the report generator outputs to an old-old version of PDF bears this out.
    Wiki articles on PDF are very nice for those high level intro summaries.
    To know / understand PDF you purchase and study the ISO Standard for PDF (ISO 32000-1:2008).
    Rather than "PDF validation" you may want to consider addressing the appearent root cause of the problem(s).
    You can change the email2fax application to one that can deal with older PDF versions.
    You can change the report generator to one that can output to the ISO Standard.
    (Perhaps the in-use application can be configured to output to the current version of PDF (i.e., the ISO Standard).
    Be well...

  • Meta tag error in site created by dreamweaver

    I recently checked my site www.bestical.com at The W3C Markup Validation Service and there are error in it
    but  added all the meta tags by standard Dreamweaver tools
    so which one is wring?

    Short answer:  You're using an HTML5 doc type which has a different set of specs for valid meta tags and other HTML syntax.
    Introduction to HTML
    Where you have this:
    <meta http-equiv="Content-Language" content="fa">
    Language must be expressed in the <html> tag like this:
    <!doctype html>
    <html lang="fa">
    <head>
    <meta charset="utf-8">
    For more on HTML5 specifications, see the W3Schools site above.
    Nancy O.

  • Added editable regions in order to insert meta tags, but get code error. What did I do wrong?

    Hi,
    Made a website based on a template, and as so many people, was afterwards struggling with optimizing my titles, descriptions and keywords for SEO. These were/are locked in the head section of the template. I found lots of useful information on the forum to unlock this section, but apparently I am doing something wrong and I can't figure out what. The code error I get is that there is a syntaxis error in the template comment. Also I do see that the color of the code is maybe not the way it should be.
    This is the code I pasted in:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" >
    <!-- TemplateBeginEditable name=”basisontwerp” -->
    <title>untitled document</title>
    <!-- TemplateEndEditable -->
    <!-- TemplateBeginEditable name="head" -->
    <meta name=”keywords” content=”keywords go here” >
    <meta name=”description” content=”description goes here” >
    <!-- TemplateEndEditable -->
    <link rel="icon" type="rel/icon" href="images/neroli_logo_mini.png" />
    <link rel="shortcut icon" href="images/neroli_logo_mini.png" />
    <style type="text/css">
    After that there is a whole bunch of stuff regarding two.Col.Elst.Lt.Hdr and style sheets etc. but there is a closing </head> tag just before my header and side bar section.
    Does anybody know what is wrong with my code? I just don't see it ...
    Thanks so much!!!

    He gek; probeer het opnieuw, nu rechtstreeks vanaf de site ipv als reply via de mail:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http_equiv="Content_Type" content="text/html" charset=utf-8" />
    <!-- TemplateBeginEditable name=”basisontwerp” -->
    <title>untitled document</title>
    <!-- TemplateEndEditable -->
    <!-- TemplateBeginEditable name="head" -->
    <meta name=”keywords” content=”keywords go here” >
    <meta name=”description” content=”description goes here” >
    <!-- TemplateEndEditable -->
    <link rel="icon" type="rel/icon" href="images/neroli_logo_mini.png" />
    <link rel="shortcut icon" href="images/neroli_logo_mini.png" />
    <style type="text/css">
    <!--
    body  {
    font: 100% Verdana, Arial, Helvetica, sans-serif;
    background: #666666;
    margin: 0; /* het is een goede gewoonte om de instellingen voor margin (marge) en padding (opvulling) van het element body op nul in te stellen en daarmee op de standaardinstellingen van de verschillende browsers */
    padding: 0;
    text-align: center; /* hiermee centreert u de container (het hoofdobject) in IE 5*-browsers Vervolgens wordt de tekst ingesteld op de standaardinstelling van links uitlijnen in de kiezer #container */
    color: #000000;
    /* Tips voor Elastic-lay-outs
    1. Aangezien de algehele grootte van de elastic-lay-outs is gebaseerd op de standaard lettertypegrootte van de gebruiker, hebben deze lay-outs een grotere mate van onvoorspelbaarheid. Bij een juist gebruik zijn ze echter wel toegankelijker voor diegenen die een groter lettertype behoeven omdat de lengte van de regel proportioneel blijft.
    2. De grootte van de div-elementen in deze lay-out is gebaseerd op een lettertypegrootte van 100% in het element body. Als u de tekstgrootte algeheel reduceert door middel van font-size: 80% voor het element body of voor #container, dient u niet te vergeten dat de complete lay-out proportioneel kleiner zal worden. Wellicht wilt u de breedtes van de verschillende div-elementen vergroten om dit te compenseren.
    3. Als de lettertypegrootte wordt gewijzigd d.m.v. verschillende waarden voor elk element div in plaats van voor het algehele ontwerp (bijv. #sidebar1 krijgt een lettertypegrootte van 70% en #mainContent krijgt een lettertypegrootte van 85%), leidt dit tot proportionele wijziging van de algehele grootte van elk van de div-elementen. Mogelijk wilt u dit aanpassen op basis van uw uiteindelijke lettertypegrootte.
    .twoColElsLtHdr #container {
    width: 46em;  /* deze breedte maakt een container (hoofdobject) die past een browservenster van 800 pixels, als de tekst wordt gehandhaafd in de standaard lettertypegroottes van de browser */
    background: #FFFFFF;
    margin: 0 auto; /* de automatische marges (d.m.v. auto), in combinatie met een breedte, centreren de pagina */
    border: 1px solid #000000;
    text-align: left; /* hiermee wordt de instelling text-align: center voor het element body genegeerd. */
    .twoColElsLtHdr #header {
    padding: 0 10px;  /* deze instelling voor padding (opvulling) komt overeen met de uitlijning links van de elementen binnen de div-elementen, die volgen op deze padding. Als een afbeelding wordt gebruikt in de #header in plaats van tekst, wilt u wellicht de padding (opvulling) verwijderen. */
    background-color: #DDDDDD;
    background-image: url(../images/achtergrond_kleur_buttons_mouse_over.png);
    border-top-color: #693;
    border-right-color: #693;
    border-bottom-color: #693;
    border-left-color: #693;
    border-top-width: thin;
    border-right-width: thin;
    border-bottom-width: thin;
    border-left-width: thin;
    .twoColElsLtHdr #header h1 {
    margin: 0; /* door de marge van het laatste element in het element div voor #header op 0 in te stellen voorkomt u het wegvallen van marges – een onverklaarbare ruimte tussen div-elementen. Als om het element div een rand loopt, is dit niet nodig aangezien dit tevens het wegvallen van de marge voorkomt */
    padding: 10px 0; /* door het gebruik van padding (opvulling) in plaats van een marge (via het element margin) kunt u het element van de randen van het element div vandaan houden */
    /* Tips voor sidebar1:
    1. Vergeet niet dat als u een waarde voor lettertypegrootte voor dit element div instelt, de algehele breedte van het element div dienovereenkomstig wordt aangepast.
    2. Aangezien we hier werken met em-waarden, verdient het de voorkeur om voor de zijbalk zelf geen padding (opvulling) te gebruiken. Deze wordt dan voor op standaards gebaseerde browsers toegevoegd aan de breedte, waardoor een nog onbekende daadwerkelijke breedte wordt gemaakt.
    3. De ruimte tussen de zijkant van het element div en de elementen erbinnen kan worden gemaakt door het aanbrengen van een linker- en rechtermarge voor dergelijke elementen, zoals wordt aangetoond door de regel ".thrColHybHdr #sidebar1 p".
    .twoColElsLtHdr #sidebar1 {
    float: left;
    width: 12em; /* de achtergrondkleur wordt weergegeven over de lengte van de inhoud in de kolom, maar niet verder */
    padding: 15px 0; /* binnen dit element div maakt de padding (opvulling) aan de onder- en bovenkant de visuele ruimte */
    background-image: none;
    background-color: #FFF;
    .twoColElsLtHdr #sidebar1 h3, .twoColElsLtHdr #sidebar1 p {
    margin-left: 10px; /* de linker- en rechtermarge moeten aan elk element worden gegeven dat in de kolommen aan de zijkant wordt geplaatst */
    margin-right: 10px;
    /* Tips voor mainContent:
    1. Als u dit element div voor #mainContent een andere waarde voor lettergrootte geeft dan het element div voor #sidebar1, worden de marges van het element div voor #mainContent gebaseerd op de lettergrootte ervan, terwijl de breedte van het element div voor #sidebar1 zal zijn gebaseerd op de lettergrootte daarvan. Mogelijk wilt u de waarden van deze div-elementen aanpassen.
    2. De ruimte tussen mainContent en sidebar1 wordt gemaakt met de linkermarge van het element div voor mainContent. De kolomruimte blijft gehandhaafd, ongeacht de hoeveelheid inhoud die het element div voor sidebar1 bevat. U kunt deze linkermarge verwijderen als u de tekst van het element div voor #mainContent de ruimte van #sidebar1 wilt laten opvullen wanneer de inhoud van #sidebar1 eindigt.
    3. Om het wegvallen van het zwevende element te voorkomen, zult u wellicht via uitproberen een schatting van de maximale grootte van de afbeelding of het element moeten bepalen, aangezien deze lay-out is gebaseerd op de lettertypegrootte van de gebruiker in combinatie met de door u ingestelde waarden. Maar als de gebruiker de lettertypegrootte van diens browser echter op kleiner dan normaal heeft ingesteld, is er in het element div voor #mainContent minder ruimte beschikbaar dan u tijdens het uitproberen ziet.
    4. In de onderstaande voorwaardelijke opmerking van Internet Explorer wordt de eigenschap zoom gebruikt om "hasLayout" mee te geven aan mainContent. Hierdoor wordt voorkomen dat zich diverse IE-specifieke bugs voordoen.
    .twoColElsLtHdr #mainContent {
    margin: 0 1.5em 0 13em; /* de rechtermarge kan worden opgegeven in em- of pixelwaarden. Deze marge maakt de ruimte langs de rechterzijde van de pagina. */
    .twoColElsLtHdr #footer {
    padding: 0 10px;
    background-color: #FFF;
    .twoColElsLtHdr #footer p {
    margin: 0; /* door de marges van het eerste element in de footer (voettekst) in te stellen op 0 vermijdt u het risico dat de marge wegvalt – een ruimte tussen div-elementen */
    padding: 10px 0; /* door het gebruik van padding (opvulling) voor dit element maakt u ruimte (op dezelfde manier als door middel van een marge), zonder het probleem van wegvallende marges */
    /* Miscellaneous classes for reuse */
    .fltrt { /* dit exemplaar van class kan worden gebruikt om een element aan de rechterzijde van uw pagina te laten zweven. Het zwevende element moet voorafgaan aan het element dat, op de pagina, naast het zwevende element moet staan. */
    float: right;
    margin-left: 8px;
    .fltlft { /* dit exemplaar van class kan worden gebruikt om een element aan de linkerzijde van uw pagina te laten zweven. */
    float: left;
    margin-right: 8px;
    .clearfloat { /* dit exemplaar van class moet op een element div of break zijn geplaatst en dient het laatste element te zijn vóór de afsluiting van een container (hoofdobject) die op zijn beurt een zwevend object volledig dient te bevatten */
    clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    .navigatie {
    color: #9F3;
    .twoColElsLtHdr #container #footer table tr td {
    font-family: Arial, Helvetica, sans-serif;
    -->
    </style><!--[if IE]>
    <style type="text/css">
    /* plaats in deze voorwaardelijke opmerking css-correcties voor alle versies van IE */
    .twoColElsLtHdr #sidebar1 { padding-top: 30px; }
    .twoColElsLtHdr #mainContent { zoom: 1; padding-top: 15px; }
    /* de bovenstaande softwaregebonden eigenschap zoom geeft IE de hasLayout die IE nodig heeft om verschillende bugs te vermijden */
    </style>
    <![endif]-->
    <script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <script type="text/javascript">
    <!--
    function MM_preloadImages() { //v3.0
      var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
        var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    //-->
    </script>
    <link href="../personoil.css" rel="stylesheet" type="text/css" />
    <link href="../SpryAssets/SpryMenuBarVertical.css" rel="stylesheet" type="text/css" />
    <link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    </head>
    <body class="twoColElsLtHdr">
    <div id="container">
      <div id="header">
        <table width="100%" border="0">
          <tr>
            <td width="25%" height="130"><img src="../images/neroli logo kleiner.gif" alt="" width="97" height="130" align="left" /></td>
            <td width="49%"><img src="../images/copy heading.png" width="344" height="35" vspace="0" align="middle" /></td>
            <td width="26%"><img src="../images/neroli logo kleiner.gif" alt="" width="97" height="130" align="right" /></td>
          </tr>
        </table>
      <!-- end #header --></div>
      <div id="sidebar1">
        <ul id="MenuBar1" class="MenuBarVertical">
          <li><a href="../index.html">Personoil</a></li>
          <li><a href="../waaromolie2.html">Waarom olie van Personoil?</a></li>
          <li><a class="MenuBarItemSubmenu" href="../ingredienten.html">De natuurlijke ingrediënten</a>
            <ul>
              <li><a href="../basisolien.html">De basisoliën</a></li>
              <li><a href="../essentieleolien.html">De essentiële oliën</a></li>
    </ul>
          </li>
          <li><a href="../huidtypes.html">Jouw huidtype</a></li>
          <li><a href="../gezichtsmassage.html">Gezichtsmassage en andere tips</a></li>
          <li><a href="../bestellen.php">Advies en bestellen</a></li>
        </ul>
    <h3> </h3>
      <!-- end #sidebar1 --></div>
      <div id="mainContent">
        <ul id="MenuBar2" class="MenuBarHorizontal">
          <li><a href="../contact.html">Contact</a>      </li>
          <li><a href="../betalen.html">Veilig betalen</a></li>
          <li><a href="../verzenden.html">Verzending</a>      </li>
          <li><a href="../voorwaarden.html">Algemene voorwaarden</a></li>
        </ul>
        <!-- TemplateBeginEditable name="editregion" -->
        <&nbsp>
        <h1> Hoofdinhoud </h1>
        <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Praesent aliquam,  justo convallis luctus rutrum, erat nulla fermentum diam, at nonummy quam  ante ac quam. Maecenas urna purus, fermentum id, molestie in, commodo  porttitor, felis. Nam blandit quam ut lacus. </p>
        <p>Quisque ornare risus quis  ligula. Phasellus tristique purus a augue condimentum adipiscing. Aenean  sagittis. Etiam leo pede, rhoncus venenatis, tristique in, vulputate at,  odio. Donec et ipsum et sapien vehicula nonummy. Suspendisse potenti. Fusce  varius urna id quam. Sed neque mi, varius eget, tincidunt nec, suscipit id,  libero. In eget purus. Vestibulum ut nisl. Donec eu mi sed turpis feugiat  feugiat. Integer turpis arcu, pellentesque eget, cursus et, fermentum ut,  sapien. Fusce metus mi, eleifend sollicitudin, molestie id, varius et, nibh.  Donec nec libero.</p>
        <h2>Kop niveau H2 </h2>
        <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Praesent aliquam,  justo convallis luctus rutrum, erat nulla fermentum diam, at nonummy quam  ante ac quam. Maecenas urna purus, fermentum id, molestie in, commodo  porttitor, felis. Nam blandit quam ut lacus. Quisque ornare risus quis  ligula. Phasellus tristique purus a augue condimentum adipiscing. Aenean  sagittis. Etiam leo pede, rhoncus venenatis, tristique in, vulputate at, odio.</p>
      <!-- TemplateEndEditable -->
      <!-- end #mainContent --></div>
    <!-- Dit wiselement dient onmiddellijk te volgen op het element div voor #mainContent om het element div voor #container te dwingen om alle zwevende elementen van een lager niveau te bevatten --><br class="clearfloat" />
       <div id="footer">
         <p> </p>
      <!-- end #footer --></div>
    <!-- end #container --></div>
    <script type="text/javascript">
    <!--
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    var MenuBar2 = new Spry.Widget.MenuBar("MenuBar2", {imgDown:"../SpryAssets/SpryMenuBarDownHover.gif", imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
    //-->
    </script>
    <script type="text/javascript">
    var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
    document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
    </script>
    <script type="text/javascript">
    try {
    var pageTracker = _gat._getTracker("UA-6508405-2");
    pageTracker._trackPageview();
    } catch(err) {}</script>
    </body>
    </html>

  • [HTML] How do meta-tags like "generator"/"author" affect anything?

    Hello guys!
    HTML meta-tags like
    <meta name="generator" content="">
    <meta name="site-created" content="">
    <meta name="expires" content="">
    <meta name="author" content="">
    <meta name="copyright" content="">
    <meta name="reply-to" content="">
    <meta name="owner" content="">
    <meta name="address" content="">
    <meta name="publisher-email" content="">
    <meta name="publisher-url" content="">
    Why would anyone need them on the page? Do they affect anything?

    Ever tried Wikipedia, or Google: "html meta tags"? Please, do your homework first!
    Closing...

  • Can I turn off Robo9 Meta Tags that are being inserted?

    We are having problems with the Robo9 meta tags and scripts that are being inserted in every file.  The problem is especially painful when converting older projects and then attemtping builds that fail because of the new tags and scripts.  Is there a way to turn these things off in Robo9?  Or, is there a template file somewhre that it uses to create new files that we can modify for our needs?  Thanks in advance.

    You cannot turn them off.
    I suspect your problems are related to your thread at http://forums.adobe.com/message/4089745#4089745
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • ZenCast -- Using / Displaying IDv3 Meta Tag Informati

    Hi there.
    Was wondering if anyone knows a way to get the Creative Zen Vision: M in the ZenCast folder to display the Meta-Tag information within the audio/video files. It clearly manages to do it in the Music Library, but rather than place my podcasts there, obviously I want them organised to the ZenCast folder section.
    For example... I download "Best of Moyles" BBC Radio podcasts and their file names are something stupid like:
    <EM>bestofmoyles_20060428-0700_40_pc.mp3</EM>
    <EM></EM>
    ...now, when I'm browsing through lots of these in the folder, I have no idea whats on them. In the ZenCast software, it actually shows what the file is about under the 'Item' column.... So basically does anyone know how to get whats in the "Item" colum to display on the player -- 'cos it works in the <EM>Music Library</EM> folder... just not in ZenCast.
    ....Oh, and if anyone is aware of hiding the file-type extensions from the Vision:M ... do let me know

    The problem is that the file stored on the device by ZenCast in the ZenCast folder is not an MP3 with an ID3 tag. It is a Motion JPEG file. I am not sure what meta info is stored in the motion jpeg by ZenCast. The ZVM doesn't show any meta info for any video file (as far as I can tell.
    They need to fix this, there has been a lot of talk in these forums about getting ZenCast to copy over an audio file, and not a Motion JPEG.
    The way I listen to podcasts is I copy them over the device after I download (or get ZenCast to download them), I then edit a playlist called "New Podcasts" and add in my newly download podcasts. Then I can quickly find my new podcasts.

  • How do I add multiple scripts from search engines to my meta tag properties?

    I currently have copied the goolge script for website varification and analytics, etc and pasted it into my meta tag properties dialog box. There is no problem as far as Google varifying the page. However, I would like to copy Bing's search engine script into my meta tag in addition to Googles script. How do I go about doing this? Do I hit the return on my keyboard under the ending of Googles script, then paste in the Bing script?
    The the last part of the Google script ending in this:
    </script>
    (paste new script from Bing here?)
    Will this cancel out each other and cause problems?
    Can someone walk me through this process, because Bing's search engine will not varify my site through two of the three other methods.
    Ben

    Adding a script after the closure of previous script is the way to go i.e. right after the </script> tag.
    So it should look something like below:
    <script>
    Google's script
    </script>
    <script>
    Bing's script
    </script>
    Cannot comment on one interfering with the other since it really depends on what exact code is there in the scripts. Google and Bing help resources will be able to help more with this.
    Thanks,
    Vikas

Maybe you are looking for