oley.com

iddaa, Spor Toto, At Yarışı ve Çok Kazandıran Hazır Kuponlara iddaa, Oley.com'da Oynanır, Milli Piyango Bileti'de Oley.com'dan Alınır. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 08-08-2013 06:40:00  (update).

Overview Info

  • Domain Name
    oley.com
  • Favicon
  • Alexa Rank
    #35971
  • Google Page Rank
    PR 6
  • Ip Address
    195.33.231.100
  • Page Size
    73.4 KB
  • Images
    24 GIF, 33 JPG, 5 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 7 1 8 0 0

Website Meta Analysis



  • Title
    Oley.com - iddaa Bahis Sitesi, At Yarışı, Spor Toto Bahis Yap
  • Meta Description
    iddaa, Spor Toto, At Yarışı ve Çok Kazandıran Hazır Kuponlara iddaa, Oley.com'da Oynanır, Milli Piyango Bileti'de Oley.com'dan Alınır.

Technical Analysis



  • Webserver
    false
  • Ip Address
    195.33.231.100
  • Domain Age
    12 Years, 6 Months, 18 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from oley.com.

HTML Analysis

  • expires: Sat, 6 May 1995 12:00:00 GMT
  • cache-control: no-store, no-cache, must-revalidate
  • pragma: no-cache
  • content-type: text/html;charset=UTF-8
  • date: Thu, 08 Aug 2013 06:39:56 GMT
  • server: false
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 17605
  • connection: Keep-Alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
E ELEKTRONIK BAHIS OYUNLARI, A.S.
E Elektronik Bahis Oyunlari A.S.
AHI EVRAN CADDESI NO 4
MASLAK
Istanbul, TR 34398
TR
Domain Domain Name: OLEY.COM
-

-
Administrative Contact, Technical Contact:
E ELEKTRONIK BAHIS OYUNLARI, email
E Elektronik Bahis Oyunlari A.S.
AHI EVRAN CADDESI NO 4
MASLAK
Istanbul, TR 34398
TR
902123040253

Expires: 24-Jan-2020.
Created: 20-Dec-2003.
Database Updated: 11-Feb-2012 06:57:46 EST.
Name Servers:
NS1.WEBKONTROL.DORUK.NET.TR
NS2.WEBKONTROL.DORUK.NET.TR

DNS Analysis


DNS servers
ns1.webkontrol.doruk.net.tr [212.58.3.7]
ns2.webkontrol.doruk.net.tr [212.58.3.8]

DNS Records

Answer records
oley.com SOA
server: webkontrol.doruk.net.tr
email: root@webkontrol.doruk.net.tr
serial: 2012060700
refresh: 7200
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
oley.com NS  ns1.webkontrol.doruk.net.tr 600s
oley.com NS  ns2.webkontrol.doruk.net.tr 600s
oley.com A 195.33.231.100 600s
oley.com MX
preference: 10
exchange: mail.ntv.com.tr
600s

Authority records

Additional records
ns1.webkontrol.doruk.net.tr A 212.58.3.7 1175s
ns2.webkontrol.doruk.net.tr A 212.58.3.8 1178s
mail.ntv.com.tr A 212.175.15.109 600s

IP 195.33.231.100 Analysis

  • Country Code
    TR
  • Country Code3
    TUR
  • Country Name
    Turkey
  • City
    Dogus
  • Continent Code
    EU
  • Latitude
    37.1953
  • Longitude
    41.0406
  • No whois ip data for 195.33.231.100

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 135 Errors
  • 40 Warnings
Ratio Text/Html
  • 0.6883661488078597
Message Error
  • Error Line 6, Column 16: there is no attribute "NAME"
        <META NAME="description" CONTENT="iddaa, Spor Toto, At Yarışı ve Çok Kazand…

    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.

  • Error Line 6, Column 38: there is no attribute "CONTENT"
        <META NAME="description" CONTENT="iddaa, Spor Toto, At Yarışı ve Çok Kazand…

    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.

  • Error Line 6, Column 176: element "META" undefined
    …ra iddaa, Oley.com'da Oynanır, Milli Piyango Bileti'de Oley.com'dan Alınır." />

    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).
  • Error Line 7, Column 408: element "META" undefined
    …venilir, hızlı ve kolayca oynayın. Oley.com Doğuş Holding A.Ş. kuruluşudur." />

    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).
  • Error Line 8, Column 402: element "META" undefined
    …o, altılı ganyan, videoley,Yayın Saatleri, paylaşılan kuponlar, kampanyalar" />

    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).
  • Error Line 9, Column 37: element "META" undefined
        <META NAME="alexa" CONTENT="100"></META>

    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).
  • Error Line 10, Column 20: there is no attribute "property"
        <meta property="og:image" content="http://static.oley.com/v1.087/resources/…

    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.

  • Error Line 11, Column 76: element "META" undefined
        <META NAME="msvalidate.01" CONTENT="14850AD9C90373BAC6FCEA3F3E6008A0" />

    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).
  • Error Line 12, Column 52: element "META" undefined
        <META NAME="y_key" CONTENT="d11e215c72dd7820" />

    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).
  • Error Line 13, Column 98: element "META" undefined
    …gle-site-verification" CONTENT="XU1h-4Xo1yhbtrY89p6BtUHi_njVEPi688wOCp_FbwY" />

    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).
  • Error Line 14, Column 43: element "META" undefined
        <META NAME="geo.region" CONTENT="TR" />

    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).
  • Error Line 15, Column 62: element "META" undefined
        <META NAME="geo.position" CONTENT="40.979898;28.959961" />

    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).
  • Error Line 16, Column 55: element "META" undefined
        <META NAME="ICBM" CONTENT="40.979898, 28.959961" />

    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).
  • Error Line 81, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <div id=engine style="position:fixed;bottom:10px;right:10px"><img class=indic…
  • Error Line 81, Column 75: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ed;bottom:10px;right:10px"><img class=indicator src="http://static.oley.com/v1…
  • Error Line 81, Column 168: required attribute "alt" not specified
    …/static.oley.com/v1.087/resources/themes/common/images/indicator2.gif" /></div>

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

  • Error Line 104, Column 9: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
          <p>

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

  • Error Line 108, Column 9: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
          <p>

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

  • Error Line 118, Column 75: document type does not allow element "form" here; missing one of "object", "applet", "map", "iframe", "ins", "del" start-tag
    		<form method="post" id="loginForm" action="/giris" style="display:none;">

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

  • Error Line 119, Column 323: there is no attribute "autocomplete"
    …re" id="kullanici_sifre" autocomplete="off" title="Şifre" value="" /><button t…

    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.

  • Error Line 175, Column 29: an attribute value must be a literal unless it contains only name characters
                    <li><a href=/spor-toto/bahis-yap class="sm-icon" id="sst1">Bahi…

    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.

  • Error Line 226, Column 76: ID "sh5" already defined
    …f="/hesabim/hesap-hareketlerim" class="sm-icon" id="sh5">Hesap Hareketlerim</a>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 201, Column 84: ID "sh5" first defined here
    …ef="/hesabim/profilim" class="sm-icon selectorNavigation" id="sh5">Profilim</a>
  • Error Line 257, Column 131: required attribute "alt" not specified
    …asaray"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/bursa.jpg"></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>.

  • Error Line 257, Column 135: end tag for "img" omitted, but OMITTAG NO was specified
    …asaray"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/bursa.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 257, Column 65: start tag was here
    …/2013/1554/249/Bursaspor-Galatasaray"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 260, Column 142: required attribute "alt" not specified
    …ıgspor"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/kasim.jpg"></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>.

  • Error Line 260, Column 146: end tag for "img" omitted, but OMITTAG NO was specified
    …ıgspor"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/kasim.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 260, Column 76: start tag was here
    …165/Kasimpasa-Sanica Boru Elazıgspor"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 263, Column 128: required attribute "alt" not specified
    … Munih"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/mainz.jpg"></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>.

  • Error Line 263, Column 132: end tag for "img" omitted, but OMITTAG NO was specified
    … Munih"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/mainz.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 263, Column 62: start tag was here
    …mac/2013/1554/168/Mainz-Bayern Munih"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 266, Column 125: required attribute "alt" not specified
    …-Chelsea"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/new.jpg"></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>.

  • Error Line 266, Column 129: end tag for "img" omitted, but OMITTAG NO was specified
    …-Chelsea"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/new.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 266, Column 61: start tag was here
    …/mac/2013/1554/176/Newcastle-Chelsea"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 269, Column 130: required attribute "alt" not specified
    …ter Utd"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/fulh.jpg"></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>.

  • Error Line 269, Column 134: end tag for "img" omitted, but OMITTAG NO was specified
    …ter Utd"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/fulh.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 269, Column 65: start tag was here
    …/2013/1554/255/Fulham-Manchester Utd"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 272, Column 129: required attribute "alt" not specified
    …Madrid"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/grana.jpg"></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>.

  • Error Line 272, Column 133: end tag for "img" omitted, but OMITTAG NO was specified
    …Madrid"><img src="http://oley.mncdn.net/mansetler/2013/subat/02/grana.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 272, Column 63: start tag was here
    …ac/2013/1554/281/Granada-Real Madrid"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 275, Column 128: required attribute "alt" not specified
    …<img src="http://oley.mncdn.net/mansetler/2012/aralik/19/kazanctakimi.jpg"></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>.

  • Error Line 275, Column 132: end tag for "img" omitted, but OMITTAG NO was specified
    …<img src="http://oley.mncdn.net/mansetler/2012/aralik/19/kazanctakimi.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 275, Column 54: start tag was here
    …"http://oley.com/#/duyuru/detay/421/"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 278, Column 121: required attribute "alt" not specified
    …81/"><img src="http://oley.mncdn.net/mansetler/2013/ocak/25/sefmanset.jpg"></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>.

  • Error Line 278, Column 125: end tag for "img" omitted, but OMITTAG NO was specified
    …81/"><img src="http://oley.mncdn.net/mansetler/2013/ocak/25/sefmanset.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 278, Column 52: start tag was here
    …f="http://oley.com/duyuru/detay/581/"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 281, Column 125: required attribute "alt" not specified
    …/"><img src="http://oley.mncdn.net/mansetler/2013/ocak/01/pascal-mans.jpg"></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>.

  • Error Line 281, Column 129: end tag for "img" omitted, but OMITTAG NO was specified
    …/"><img src="http://oley.mncdn.net/mansetler/2013/ocak/01/pascal-mans.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 281, Column 54: start tag was here
    …"http://oley.com/kampanya/detay/457/"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 284, Column 135: required attribute "alt" not specified
    …c="http://oley.mncdn.net/mansetler/2012/haziran/22/call-center-manset.jpg"></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>.

  • Error Line 284, Column 139: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://oley.mncdn.net/mansetler/2012/haziran/22/call-center-manset.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 284, Column 54: start tag was here
    …"http://oley.com/#/duyuru/detay/581/"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 287, Column 115: required attribute "alt" not specified
    …arlar/"><img src="http://oley.mncdn.net/mansetler/2011/mayis/10/zirve.jpg"></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>.

  • Error Line 287, Column 119: end tag for "img" omitted, but OMITTAG NO was specified
    …arlar/"><img src="http://oley.mncdn.net/mansetler/2011/mayis/10/zirve.jpg"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 287, Column 49: start tag was here
    …href="#/iddaa/zirvedekiler/tutarlar/"><img src="http://oley.mncdn.net/mansetle…
  • Error Line 294, Column 79: required attribute "alt" not specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/bursa.jpg"></li>

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

  • Error Line 294, Column 84: end tag for "img" omitted, but OMITTAG NO was specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/bursa.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 294, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/bursa.jpg">…
  • Error Line 295, Column 79: required attribute "alt" not specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/kasim.jpg"></li>

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

  • Error Line 295, Column 84: end tag for "img" omitted, but OMITTAG NO was specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/kasim.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 295, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/kasim.jpg">…
  • Error Line 296, Column 79: required attribute "alt" not specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/mainz.jpg"></li>

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

  • Error Line 296, Column 84: end tag for "img" omitted, but OMITTAG NO was specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/mainz.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 296, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/mainz.jpg">…
  • Error Line 297, Column 77: required attribute "alt" not specified
    …					<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/new.jpg"></li>

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

  • Error Line 297, Column 82: end tag for "img" omitted, but OMITTAG NO was specified
    …					<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/new.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 297, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/new.jpg"></…
  • Error Line 298, Column 78: required attribute "alt" not specified
    …				<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/fulh.jpg"></li>

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

  • Error Line 298, Column 83: end tag for "img" omitted, but OMITTAG NO was specified
    …				<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/fulh.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 298, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/fulh.jpg"><…
  • Error Line 299, Column 79: required attribute "alt" not specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/grana.jpg"></li>

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

  • Error Line 299, Column 84: end tag for "img" omitted, but OMITTAG NO was specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/grana.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 299, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2013/subat/02/grana.jpg">…
  • Error Line 300, Column 87: required attribute "alt" not specified
    …img src="http://oley.mncdn.net/mansetler/2012/aralik/19/kazanctakimi.jpg"></li>

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

  • Error Line 300, Column 92: end tag for "img" omitted, but OMITTAG NO was specified
    …img src="http://oley.mncdn.net/mansetler/2012/aralik/19/kazanctakimi.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 300, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2012/aralik/19/kazanctaki…
  • Error Line 301, Column 82: required attribute "alt" not specified
    …<li><img src="http://oley.mncdn.net/mansetler/2013/ocak/25/sefmanset.jpg"></li>

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

  • Error Line 301, Column 87: end tag for "img" omitted, but OMITTAG NO was specified
    …<li><img src="http://oley.mncdn.net/mansetler/2013/ocak/25/sefmanset.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 301, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2013/ocak/25/sefmanset.jp…
  • Error Line 302, Column 84: required attribute "alt" not specified
    …i><img src="http://oley.mncdn.net/mansetler/2013/ocak/01/pascal-mans.jpg"></li>

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

  • Error Line 302, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …i><img src="http://oley.mncdn.net/mansetler/2013/ocak/01/pascal-mans.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 302, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2013/ocak/01/pascal-mans.…
  • Error Line 303, Column 94: required attribute "alt" not specified
    …="http://oley.mncdn.net/mansetler/2012/haziran/22/call-center-manset.jpg"></li>

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

  • Error Line 303, Column 99: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://oley.mncdn.net/mansetler/2012/haziran/22/call-center-manset.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 303, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2012/haziran/22/call-cent…
  • Error Line 304, Column 79: required attribute "alt" not specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2011/mayis/10/zirve.jpg"></li>

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

  • Error Line 304, Column 84: end tag for "img" omitted, but OMITTAG NO was specified
    …			<li><img src="http://oley.mncdn.net/mansetler/2011/mayis/10/zirve.jpg"></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 304, Column 13: start tag was here
     							<li><img src="http://oley.mncdn.net/mansetler/2011/mayis/10/zirve.jpg">…
  • Error Line 337, Column 96: document type does not allow element "div" here; assuming missing "li" start-tag
    …x"><div style="padding:10px 0 0 10px;"><img src="http://static.oley.com/v1.087…
  • Error Line 337, Column 183: required attribute "alt" not specified
    …tic.oley.com/v1.087/resources/themes/common/images/indicator2.gif"></div></ul> 

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

  • Error Line 337, Column 189: end tag for "img" omitted, but OMITTAG NO was specified
    …tic.oley.com/v1.087/resources/themes/common/images/indicator2.gif"></div></ul> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 337, Column 97: start tag was here
    …"><div style="padding:10px 0 0 10px;"><img src="http://static.oley.com/v1.087/…
  • Error Line 337, Column 194: end tag for "li" omitted, but OMITTAG NO was specified
    …tic.oley.com/v1.087/resources/themes/common/images/indicator2.gif"></div></ul> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 337, Column 61: start tag was here
    …ahisleriTabs" class="tabBox clearfix"><div style="padding:10px 0 0 10px;"><img…
  • Error Line 349, Column 23: an attribute specification must start with a name or name token
    					<li class="first""><a href="#pk_0" rel="">bütün üyeler</a></li>

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

  • Warning Line 356, Column 184: cannot generate system identifier for general entity "d"
    …b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resource…

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

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

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

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

  • Error Line 356, Column 184: general entity "d" not defined and no default entity
    …b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resource…

    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.

  • Warning Line 356, Column 185: reference not terminated by REFC delimiter
    …9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 356, Column 185: reference to external entity in attribute value
    …9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 356, Column 185: reference to entity "d" for which no system identifier could be generated
    …9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 362, Column 181: reference not terminated by REFC delimiter
    …6e074c0e76b7e5ad64579bb03056a7d?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 362, Column 181: reference to external entity in attribute value
    …6e074c0e76b7e5ad64579bb03056a7d?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 362, Column 181: reference to entity "d" for which no system identifier could be generated
    …6e074c0e76b7e5ad64579bb03056a7d?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 368, Column 182: reference not terminated by REFC delimiter
    …72f9759fe83abfccce198ef11b55be7?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 368, Column 182: reference to external entity in attribute value
    …72f9759fe83abfccce198ef11b55be7?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 368, Column 182: reference to entity "d" for which no system identifier could be generated
    …72f9759fe83abfccce198ef11b55be7?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 374, Column 183: reference not terminated by REFC delimiter
    …2107900b8480bb8504baf91df21060f?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 374, Column 183: reference to external entity in attribute value
    …2107900b8480bb8504baf91df21060f?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 374, Column 183: reference to entity "d" for which no system identifier could be generated
    …2107900b8480bb8504baf91df21060f?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 380, Column 185: reference not terminated by REFC delimiter
    …e5e92c3a092c170f89a0d50dca56c08?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 380, Column 185: reference to external entity in attribute value
    …e5e92c3a092c170f89a0d50dca56c08?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 380, Column 185: reference to entity "d" for which no system identifier could be generated
    …e5e92c3a092c170f89a0d50dca56c08?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 386, Column 181: reference not terminated by REFC delimiter
    …6e074c0e76b7e5ad64579bb03056a7d?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 386, Column 181: reference to external entity in attribute value
    …6e074c0e76b7e5ad64579bb03056a7d?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 386, Column 181: reference to entity "d" for which no system identifier could be generated
    …6e074c0e76b7e5ad64579bb03056a7d?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 396, Column 186: reference not terminated by REFC delimiter
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 396, Column 186: reference to external entity in attribute value
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 396, Column 186: reference to entity "d" for which no system identifier could be generated
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 402, Column 186: reference not terminated by REFC delimiter
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 402, Column 186: reference to external entity in attribute value
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 402, Column 186: reference to entity "d" for which no system identifier could be generated
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 408, Column 187: reference not terminated by REFC delimiter
    …e3652f15437dd3d72aa7644b956fe0c?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 408, Column 187: reference to external entity in attribute value
    …e3652f15437dd3d72aa7644b956fe0c?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 408, Column 187: reference to entity "d" for which no system identifier could be generated
    …e3652f15437dd3d72aa7644b956fe0c?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 414, Column 182: reference not terminated by REFC delimiter
    …00f964cc96947cbc2f40ef27ea85f63?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 414, Column 182: reference to external entity in attribute value
    …00f964cc96947cbc2f40ef27ea85f63?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 414, Column 182: reference to entity "d" for which no system identifier could be generated
    …00f964cc96947cbc2f40ef27ea85f63?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 420, Column 182: reference not terminated by REFC delimiter
    …00f964cc96947cbc2f40ef27ea85f63?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 420, Column 182: reference to external entity in attribute value
    …00f964cc96947cbc2f40ef27ea85f63?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 420, Column 182: reference to entity "d" for which no system identifier could be generated
    …00f964cc96947cbc2f40ef27ea85f63?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 426, Column 190: reference not terminated by REFC delimiter
    …8b676aade684fbade028a1feb82a232?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 426, Column 190: reference to external entity in attribute value
    …8b676aade684fbade028a1feb82a232?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 426, Column 190: reference to entity "d" for which no system identifier could be generated
    …8b676aade684fbade028a1feb82a232?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 436, Column 185: reference not terminated by REFC delimiter
    …f15f30df4a578abe13753db22f6c849?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 436, Column 185: reference to external entity in attribute value
    …f15f30df4a578abe13753db22f6c849?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 436, Column 185: reference to entity "d" for which no system identifier could be generated
    …f15f30df4a578abe13753db22f6c849?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 442, Column 187: reference not terminated by REFC delimiter
    …0e52e0d9d7da54eb06d3727c9a3e100?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 442, Column 187: reference to external entity in attribute value
    …0e52e0d9d7da54eb06d3727c9a3e100?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 442, Column 187: reference to entity "d" for which no system identifier could be generated
    …0e52e0d9d7da54eb06d3727c9a3e100?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 448, Column 186: reference not terminated by REFC delimiter
    …79d748b920f811ffce73fc5363687d8?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 448, Column 186: reference to external entity in attribute value
    …79d748b920f811ffce73fc5363687d8?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 448, Column 186: reference to entity "d" for which no system identifier could be generated
    …79d748b920f811ffce73fc5363687d8?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 454, Column 186: reference not terminated by REFC delimiter
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 454, Column 186: reference to external entity in attribute value
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 454, Column 186: reference to entity "d" for which no system identifier could be generated
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 460, Column 183: reference not terminated by REFC delimiter
    …387b846c231fc7fdbab92003850fd7d?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 460, Column 183: reference to external entity in attribute value
    …387b846c231fc7fdbab92003850fd7d?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 460, Column 183: reference to entity "d" for which no system identifier could be generated
    …387b846c231fc7fdbab92003850fd7d?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Warning Line 466, Column 186: reference not terminated by REFC delimiter
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 466, Column 186: reference to external entity in attribute value
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 466, Column 186: reference to entity "d" for which no system identifier could be generated
    …59358b62dac56bc356ce74476ed1868?s=48&d=http://static.oley.com/v1.087/resources…

    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.

  • Info Line 356, Column 183: entity was defined here
    …/b9541d1208c09982b6fc10052df87152?s=48&d=http://static.oley.com/v1.087/resourc…
  • Error Line 496, Column 31: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                <p><a style="color:#666666;font:12px/18px Arial;tex…

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

  • Error Line 548, Column 138: required attribute "alt" not specified
    …oley.com/v1.087/resources/assets/campaignMadrid2-mainpage.jpg" width="355"></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>.

  • Error Line 548, Column 142: end tag for "img" omitted, but OMITTAG NO was specified
    …oley.com/v1.087/resources/assets/campaignMadrid2-mainpage.jpg" width="355"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 548, Column 40: start tag was here
    …       <a href="/kampanya/detay/457/"><img src="http://static.oley.com/v1.087/…
  • Error Line 561, Column 155: end tag for "br" omitted, but OMITTAG NO was specified
    …240px;text-align:left;"><a href="/video/liste">tümünü göster</a></span></p><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 561, Column 151: start tag was here
    …240px;text-align:left;"><a href="/video/liste">tümünü göster</a></span></p><br>
  • Error Line 585, Column 35: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <p><a style="color:#666666;font:12px/18px Arial…

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

  • Error Line 590, Column 35: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <p><a style="color:#666666;font:12px/18px Arial…

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

  • Error Line 595, Column 35: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <p><a style="color:#666666;font:12px/18px Arial…

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

  • Error Line 600, Column 35: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <p><a style="color:#666666;font:12px/18px Arial…

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

  • Error Line 673, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        		 <a target=_blank href="http://www.facebook.com/oleycom" style="margin-ri…
  • Error Line 674, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        		 <a target=_blank href="http://twitter.com/oleycom" style=""><img src="ht…
  • Error Line 682, Column 23: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        				<li><a target=_blank href="/at-yarisi/muhtemeller">Muhtemel</a></li>
  • Error Line 683, Column 23: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        				<li><a target=_blank href="/at-yarisi/sonuclari">Sonuçlar</a></li>    	…
  • Error Line 714, Column 96: required attribute "alt" not specified
    …://static.oley.com/v1.087/resources/themes/default/images/sportoto.png" /></td>

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

  • Error Line 715, Column 129: required attribute "alt" not specified
    …ttp://static.oley.com/v1.087/resources/themes/default/images/iddaa.gif" /></td>

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

  • Error Line 716, Column 102: required attribute "alt" not specified
    …tic.oley.com/v1.087/resources/themes/default/images/mp-logo-footer.png" /></td>

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

  • Error Line 728, Column 69: ID "kullanici_id" already defined
    …sername tBox" name="kullanici_id" id="kullanici_id" autocomplete="off" title="…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 119, Column 107: ID "kullanici_id" first defined here
    …ength(1-50)]" name="kullanici_id" id="kullanici_id" title="E-posta ya da kulla…
  • Error Line 729, Column 76: ID "kullanici_sifre" already defined
    …word tBox" name="kullanici_sifre" id="kullanici_sifre" autocomplete="off" titl…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 119, Column 293: ID "kullanici_sifre" first defined here
    …th(6-16)]" name="kullanici_sifre" id="kullanici_sifre" autocomplete="off" titl…
  • Error Line 748, Column 148: required attribute "alt" not specified
    …7/resources/themes/common/images/indicator20-0-56C9F6-FFFFFF.gif'></p></center>

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

  • Error Line 748, Column 152: end tag for "img" omitted, but OMITTAG NO was specified
    …7/resources/themes/common/images/indicator20-0-56C9F6-FFFFFF.gif'></p></center>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 748, Column 16: start tag was here
        <center><p><img style="padding-bottom:10px;" src='http://static.oley.com/v1…
  • Error Line 857, Column 68: document type does not allow element "br" here
    …"Sadece üyelerimiz bilet alabilir.<br/>Lütfen giriş yaparak devam edin.",onSuc…

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

  • Error Line 866, Column 117: document type does not allow element "b" here
    …akımı Ortak Kupon","desc":"Oley.com <b>Kazanç Takımı<\/b>'nın seçimlerinden ol…

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

  • Warning Line 866, Column 131: character "<" is the first character of a delimiter but occurred as data
    …pon","desc":"Oley.com <b>Kazanç Takımı<\/b>'nın seçimlerinden oluşturulmuştur<…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 866, Column 174: end tag for "br" omitted, but OMITTAG NO was specified
    …'nın seçimlerinden oluşturulmuştur<br>","count":31,"odds":4.56,"gain":9.13,"id…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 170: start tag was here
    …\/b>'nın seçimlerinden oluşturulmuştur<br>","count":31,"odds":4.56,"gain":9.13…
  • Warning Line 866, Column 964: character "<" is the first character of a delimiter but occurred as data
    …":"Düello Kuponu","desc":"<b>Oley.com <\/b>editörlerinin seçimlerinden oluştur…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 866, Column 1016: end tag for "br" omitted, but OMITTAG NO was specified
    …inin seçimlerinden oluşturulmuştur<br>","count":28,"odds":5.49,"gain":10.97,"i…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 1012: start tag was here
    …rlerinin seçimlerinden oluşturulmuştur<br>","count":28,"odds":5.49,"gain":10.9…
  • Warning Line 866, Column 1787: character "<" is the first character of a delimiter but occurred as data
    … Süper Lig","desc":"<b>\u200BOley.com <\/b>uzmanlarının<b> Süper Lig <\/b>orta…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 866, Column 1818: character "<" is the first character of a delimiter but occurred as data
    …ey.com <\/b>uzmanlarının<b> Süper Lig <\/b>ortak kuponu<br>","count":3,"odds":…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 866, Column 1839: end tag for "br" omitted, but OMITTAG NO was specified
    …nın<b> Süper Lig <\/b>ortak kuponu<br>","count":3,"odds":3.6,"gain":7.21,"id":…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 1835: start tag was here
    …larının<b> Süper Lig <\/b>ortak kuponu<br>","count":3,"odds":3.6,"gain":7.21,"…
  • Warning Line 866, Column 2602: character "<" is the first character of a delimiter but occurred as data
    …":"Premier Lig","desc":"<b>Premier Lig<\/b>'e özel kupon<br>","count":3,"odds"…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 866, Column 2624: end tag for "br" omitted, but OMITTAG NO was specified
    …:"<b>Premier Lig<\/b>'e özel kupon<br>","count":3,"odds":4.46,"gain":8.93,"id"…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 2620: start tag was here
    …esc":"<b>Premier Lig<\/b>'e özel kupon<br>","count":3,"odds":4.46,"gain":8.93,…
  • Warning Line 866, Column 3574: character "<" is the first character of a delimiter but occurred as data
    …":"İspanya La Liga","desc":"<b>La Liga<\/b>'ya özel kupon<br>","count":1,"odds…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 866, Column 3597: end tag for "br" omitted, but OMITTAG NO was specified
    …sc":"<b>La Liga<\/b>'ya özel kupon<br>","count":1,"odds":3.53,"gain":7.05,"id"…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 3593: start tag was here
    …,"desc":"<b>La Liga<\/b>'ya özel kupon<br>","count":1,"odds":3.53,"gain":7.05,…
  • Warning Line 866, Column 4558: character "<" is the first character of a delimiter but occurred as data
    …anya Bundesliga","desc":"<b>Bundesliga<\/b>'ya özel kupon<br>","count":3,"odds…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 866, Column 4581: end tag for "br" omitted, but OMITTAG NO was specified
    …:"<b>Bundesliga<\/b>'ya özel kupon<br>","count":3,"odds":3.36,"gain":6.73,"id"…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 4577: start tag was here
    …esc":"<b>Bundesliga<\/b>'ya özel kupon<br>","count":3,"odds":3.36,"gain":6.73,…
  • Warning Line 866, Column 5356: character "<" is the first character of a delimiter but occurred as data
    …e":"İtalya Serie A","desc":"<b>Serie A<\/b>'ya özel kupon<br>","count":0,"odds…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 866, Column 5379: end tag for "br" omitted, but OMITTAG NO was specified
    …sc":"<b>Serie A<\/b>'ya özel kupon<br>","count":0,"odds":3.43,"gain":6.86,"id"…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 5375: start tag was here
    …,"desc":"<b>Serie A<\/b>'ya özel kupon<br>","count":0,"odds":3.43,"gain":6.86,…
  • Error Line 874, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
        </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 5346: start tag was here
    …1,"longname":"İtalya Serie A","desc":"<b>Serie A<\/b>'ya özel kupon<br>","coun…
  • Error Line 874, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
        </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 4545: start tag was here
    …ongname":"Almanya Bundesliga","desc":"<b>Bundesliga<\/b>'ya özel kupon<br>","c…
  • Error Line 874, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
        </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 3564: start tag was here
    …,"longname":"İspanya La Liga","desc":"<b>La Liga<\/b>'ya özel kupon<br>","coun…
  • Error Line 874, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
        </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 2588: start tag was here
    …l":1,"longname":"Premier Lig","desc":"<b>Premier Lig<\/b>'e özel kupon<br>","c…
  • Error Line 874, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
        </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 1804: start tag was here
    …":"<b>\u200BOley.com <\/b>uzmanlarının<b> Süper Lig <\/b>ortak kuponu<br>","co…
  • Error Line 874, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
        </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 1769: start tag was here
    …ngname":"Spor Toto Süper Lig","desc":"<b>\u200BOley.com <\/b>uzmanlarının<b> S…
  • Error Line 874, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
        </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 952: start tag was here
    …:1,"longname":"Düello Kuponu","desc":"<b>Oley.com <\/b>editörlerinin seçimleri…
  • Error Line 874, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
        </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 115: start tag was here
    … Takımı Ortak Kupon","desc":"Oley.com <b>Kazanç Takımı<\/b>'nın seçimlerinden …

Visitor Analysis

Daily Visitor
  • 4.200 visits

In Page Analysis