Sözleşme
Burada yer alan genel kurallar ve şartlar dahilinde, tüketiciler; iş ilişkileri ticari nitelikte kurulmamış olan, ya da iş ilişkilerini işveren sıfatıyla bu kişiler üzerinden yürütmeyen herhangi gerçek kişilerdir. Burada yer alan genel kurallar ve şartlar dahilinde girişimciler; iş ilişkileri ticari amaçlar ya da işveren sıfatıyla hareket etmek üzere kurulmuş olan herhangi gerçek ya da tüzel kişi ya da herhangi tüzel ortaklık veya şirket olmayan firmalardır. Burada yer alan genel kurallar ve şartlar dahilinde müşteriler; tüketiciler ve girişimcilerdir.
Uzaktan Satış Anlaşmasını Fesih Hakkı ( BGB m.312)
-Tüketici, (Alman Medeni Kanunu m.13) uzaktan satış anlaşmasını fesih hakkı (Alman Medeni Kanunu m. 355) ile yetkilendirilmelidir. Tüketici herhangi bir neden gösterme zorunluluğu olmadan anlaşmayı, emredici hükümlere bağlı malların makbuzunu takiben 2(iki) hafta içinde feshedebilir. Bu şekilde bir anlaşma feshi, yazılı olarak ya da malları geri göndererek yapılır. Sözleşmeyi vaktinde feshetmek için, malların vaktinde aşağıdaki adrese gönderilmesi yeterlidir:
webme GmbH
Richard-Wagner-Strasse 2
91054 Erlangen
Germany
-Eğer iade edilen mallar sipariş edilen mallar ile aynı ise, ve malların fiyatı 40 Avro’yu geçmiyor ise, ya da tüketici fesih anında ya da herhangi bir sözleşmeye dayalı, üzerinde anlaşılmış taksitli ödemede, malların 40 Avro’dan daha yüksek bir fiyatta olduğunu bilmiyor ise, tüketici malların iade masraflarına katlanır. Eğer sayılan durumlardan birisi yoksa, webme GmbH iade masraflarını üstlenir. İade masrafları webme GmbH tarafından yalnızca en düşük maliyetli şekilde ödenir (Deutsche Post AG-Alman Postası standart koli ücreti). Tüketici, ödemelerin geri ödenmesi için fesih bildirimini gönderdiği günden itibaren bütün sorumluluklarını yerine getirmekle yükümlüdür.
-Eğer, mallardaki değer azalması yalnızca malı test etmek için yapılmamışsa, mallarda öngörülen amaçta kullanıma bağlı bir değer azalması tüketici tarafından karşılanır. Malda değer azalmasından, malın özenle tutulması ve içeriğinin yalnızca yetkili ve teknik servis tarafından kullanıma hazır hale getirilmesiyle kaçınılabilir.
- Yazılım, yazılım lisansları ve tüketici tarafından yeniden etiketlenen DVD’ler için sözleşmeyi fesih hakkı yoktur. Tüketicinin kendi talimatları doğrultusunda üretilmiş mallar için de sözleşmeyi fesih hakkı yoktur. Sözleşmeyi fesih hakkı, girişimcinin, fesih süresinin bitiminden önce derhal beyan ettiği rızasıyla, servisleriyle hizmet etmeye başlamış olması ya da tüketicinin kendisinin başlamış olması halinde de yoktur.
1. Genel
webme GmbH servislerine katılım aşağıdaki şartlara ve webme GmbH’nın koşullarına tabidir. Gerek webme GmbH’nın servislerini, gerekse diğer servisleri kullanırken, kullanıcı, bu servisleri yürürlükteki hukuka ve burada yer alan Genel Şartlar ve Kurallara uygun olarak kullanacağını taahhüt eder.
2. Başvuru Koşulları
www.bedava-sitem.com’dan sunulan servisi kullanmak için öncelikle başvuru işleminin tamamlanmış olması gerekmektedir. Başvuru formunu eksiksiz ve doğru bilgi (başvuru bilgileri) ile dolduran her kişi (kullanıcı adı).tr.gg şeklinde ücretsiz bir web sitesi elde eder. Müşteri, kendisine e-posta yoluyla gönderilecek bir takma ismi ve şifreyi de ücretsiz olarak elde eder (kullanıcı bilgisi). Müşteriye gönderilen bu e-postada yer alan kişisel linke tıklandığında, başvuruda bulunan kişinin e-posta adresi doğrulanmış olur. www.bedava-sitem.com’a başvuran her kişi, tam ve doğru başvuru bilgisi vermekle ve bu bilgilerini zamanla yenilemekle yükümlüdür. Söz konusu kullanıcı bilgileri üye tarafından gizli tutulmalıdır. Başvuru ücretsizdir. Üye, www.bedava-sitem.com’a ait haber mektubunun ulaştırılmasını kabul eder. Üyelik veya üyelikle ilgili herhangi bir servis yalnızca kişisel amaçla kullanılır ve başkasına devredilemez.
3. Servislerin Faaliyet Alanı
webme GmbH müşterilerine, webme GmbH sunucularında web programcılığı veya sunucu teknolojileri konusunda uzmanlığı ya da derin bilgiye sahip olmayı gerektirmeden bir web sitesi oluşturabilme teknik imkanını sunar.
4. Ödemelerin Maliyetleri ve Süreleri
Yukarıda yer alan üzerinde anlaşılmış içerikten farklı olmamak kaydıyla, www.bedava-sitem.com’dan sunulan servisler ücretsizdir. Bir maliyet karşılığında sunulan servisler ölçüsünde, üye, söz konusu servisin maliyeti ve ödeme koşulları hakkında, kullanımdan önce ayrıca bilgilendirilecektir. www.bedava-sitem.com’un internet sayfasından, üçüncü kişiler tarafından sunulan ücrete tabi servisler için üçüncü kişi ile derhal bir anlaşma yapılır. Malların veya servislerin www.bedava-sitem.com’un servislerinin üyeleri aracılığıyla sunulması halinde müşteri ile bu ticari işlemlerin sağlayıcıları arasında her türlü anlaşma ayrıca yapılmalıdır.
5. Bilgi Gizliliği
Kişisel müşteri bilgilerinin toplanması ve bunlar ile ilgili işlemler Federal Bilgi Gizliliği Hukuku (Federal Data Privacy Law-BDSG) ve Teleservis Bilgi Koruma Hukuku (Teleservices Data Protection Law-TDDSG)’nun emredici hükümleri doğrultusunda ayrıca yapılamalıdır. Sözleşme ilişkisine bağlı her kişisel müşteri bilgisi, bir servis anlaşmasının kurulması ve yürürlüğe girmesi için gerektiği ölçüde, yalnızca toplanır, işlem görür ve kullanılır. Anlaşmaların elektronik işlemlerle yapıldığı durumlarda, kullanıcı işlemleri ile ilgili bilgiler yalnızca, söz konusu sözleşmelerle ilgili işlere dahil edilen webme GmbH çalışanları tarafından saklanır ve onlarca ulaşılabilir olmaktadır.
6. Üçüncü Kişilerin Sınai Mülkiyet Hakları
Üye, webme GmbH’nın link üzerinde etkisi olduğundan kendi web sayfasının içeriğinin kontrolünden ve güvenliğinden sorumludur. Ancak, webme GmbH’nın bağımsız alanların yardımıyla kurulan linklerin ulaştırdığı web sayfasının içeriğinin üzerinde bir etkisi yoktur. Her üye, kendi sayfasının yürürlükteki tüm hukuka uygun olmasından sorumludur.
Ayrıca, aşağıda yer alan içeriklere izin verilmez:
1. Eser sahibinin ya da işletme hakkı sahibinin derhal izni olmadan, kullanılacak her türlü telif hakkı olan basım; telif hakkı olan müzik, video ya da üçüncü kişilerin yazılımlarının indirilmesi ya da herhangi başka şekilde kopyalanması söz konusu telif hakkı sahiplerinin derhal rızası olmasızın teklif edilemez.
2. Dağıtımları hukuken yasaklanmış içeriklerin yayılması.
3. Pornografik içerikli görüntü ve malzemelerin yayılması.
4. Herhangi bir suç işlemeye ya da suça ortak olmaya herhangi şekilde davet.
5. Diğer insanları kötüleme, iftira, hakaret ya da tehdit içeren herhangi bir malzeme.
Yukarıda sayılan durumların ihlali sonucunda ortaya çıkan zararların ya da ihtarın webme GmbH’ye karşı ileri sürüldüğü durumlarda, bağımsız alana başvuruda bulunmuş kişi (taraf), bu türlü ihtar ve zararlara karşı bizim zararımızı karşılamakla yükümlüdür.
7. Hiperlinkler
webme GmbH ya da her hangi üçüncü kişiler diğer web sayfalarına ya da kaynaklara bağlanan link oluşturabilirler. webme GmbH’nın bu diğer siteler üzerinde kontrolü yoktur ve bu tür harici sitelerin ve kaynakların kurallara uygunluğu hakkında herhangi bir sorumluluğu ya da yükümlülüğü yoktur; bu site ve kaynaklardan ulaşılan içerik üzerinde herhangi bir egemenlik hakkı da yoktur. Bu tür harici site ve kaynaklarda ulaşılabilir olan içerikler üzerinde de herhangi bir hakimiyeti ya da sorumluluğu yoktur; ya da; webme GmbH, bu tür site ya da kaynakların içeriklerinin hukuka aykırı olduğunun farkında değilse, bu tür sitelerle ilgili herhangi bir yükümlülük, yetki ve sorumluluk taşımaz. Kullanıcılar tarafından oluşturulan linkler en büyük miktara ulaşabilir. Sayıca fazla olmalarına bağlı olarak webme GmbH çalışanlarının tüm bağlantıları kontrol etmesi ve denetlemesi teknik olarak mümkün değildir. Eğer webme GmbH sayfalarından, üçüncü kişilerin hukuka aykırı olarak yayımladığı içeriklere sahip harici sitelere link varsa, böyle bir servis sağlayıcısı, söz konusu hukuk dışı içeriğe sahip siteye bağlanan linki istek üzerine kaldırmalıdır. webme GmbH, herhangi bir bağlantı yapılmış sayfadaki artan doluluk hacminden dolayı sorumluluk ya da herhangi bir yükümlülük taşımaz.
www.bedava-sitem.com kullanıcıları, harici bir sayfaya bir link kurmadan önce, söz konusu sayfanın sağlayıcılarının, harici bir sayfayla link kurulmasına herhangi bir itirazı olmadığını temin etmek zorundadır. Daha sonra ayrıca, kullanıcı, harici linklerin içeriklerini yeni bir çerçeveye yerleştirerek bu linkleri tanıtır.
webme GmbH’ye karşı söz konusu harici linkler sonucu bir zarar iddiasında bulunulursa, ilgili üye bizi bu türden zarar iddialarına karşı ilk talep üzerine tazmin eder. webme GmbH, ilgili sayfanın sağlayıcısı söz konusu linke karşı herhamgi bir itirazda bulunur bulunmaz webme GmbH, linkin kaldırılmasının haklı olup olmadığına bakmaksızın linki kaldırır. Üyenin hiçbir şekilde hukuka ya da ahlaka aykırı olan, ırkçılığı özendiren, şiddeti yücelten, öven ya da küçülten (Alman Medeni Kanunu m.131), savaşı öven, çocukların ya da gençlerin ahlaklarını maddi bakımdan tehdit etmeye elverişli olan ya da onların refahını etkileyen, webme GmbH’nın ününe zarar verecek olan, pornografik içerikli ya da adı geçen şekillere benzer içerikler bulunan sayfalara link yapılmasına izin verilmez.
8. Sözleşmenin Sona Ermesi
Sağlayıcının, hiçbir neden göstermeksizin hesapları iptal etme, hiçbir neden bildirmeksizin ve önceden ihbarda bulunmaksızın sözleşmesel ilişkiyi sona erdirme hakkı saklıdır. Web sayfalarının yedek kopyalarının yapılmasının nedeni budur. Eğer sözleşme sona erdirilmemiş ise, belirsiz bir tarihe kadar devam eder ve iki tarafın rızasıyla sona erdirilebilir. Sağlayıcı, hesabın sona erdirilmesini takiben en az 6 (altı) aylık bir süre için, alanların webme GmbH ya da onların hissedarlarınca yeni kayıt yapılmadığını taahhüt eder.
9. Koruma Hükmü
Eğer bu Genel Kurallar ve Şartların herhangi bir hükmünün bir kısmının ya da tamamının geçersizliği ileri sürülürse, söz konusu geçersiz hüküm, geri kalan hükümlerin geçerliliğini etkilemez.
10. Yargılamaya Yetkili Mahkemeler
Eğer müşteriler, bir girişimci, bir kamu hukuku tüzel kişisi ya da kamu özel şirketiyse, müşteri ve webme GmbH arasında sözleşmesel ilişkiden kaynaklanan herhangi bir anlaşmazlık olursa, davalar, webme GmbH’nın merkezinin bulunduğu yerdeki Adliye mahkemelerinde açılır.
webme GmbH, ayrıca, müşterinin ikametgahında dava açmaya da yetkilidir. Bu sözleşme, yalnızca Federal Almanya Cumhuriyeti Hukukuna tabidir.
Validation Output: 59 Errors
Line 11, Column 41: character "&" is the first character of a delimiter but occurred as data
…itle>Kodarsivim.tr.gg | Html Kodlar & Css Tasarımlar & JavaScript KodlarThis message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
- Line 11, Column 63: character "&" is the first character of a delimiter but occurred as data
…| Html Kodlar & Css Tasarımlar & JavaScript Kodlar - Html Kodlar</title>This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 475, Column 17: Attribute "height" exists, but can not be used for this element.
<table height="27">You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
- Line 491, Column 24: document type does not allow element "style" here
<style type="text/css">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).
- Line 537, Column 110: cannot generate system identifier for general entity "categoryID"
…2f855d5-bb6a-4764-9fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" heigAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 537, Column 110: general entity "categoryID" not defined and no default entity
…2f855d5-bb6a-4764-9fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" heigThis 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.
- Line 537, Column 120: reference not terminated by REFC delimiter
…6a-4764-9fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" height="600px"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.
- Line 537, Column 120: reference to external entity in attribute value
…6a-4764-9fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" height="600px"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 '&'.
- Line 537, Column 120: reference to entity "categoryID" for which no system identifier could be generated
…6a-4764-9fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" height="600px"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.
Line 537, Column 108: entity was defined here
…=02f855d5-bb6a-4764-9fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" he- Line 537, Column 123: cannot generate system identifier for general entity "sizeID"
…4764-9fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" height="600px" frAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 537, Column 123: general entity "sizeID" not defined and no default entity
…4764-9fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" height="600px" frThis 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.
- Line 537, Column 129: reference not terminated by REFC delimiter
…fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" height="600px" frameborIf 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.
- Line 537, Column 129: reference to external entity in attribute value
…fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" height="600px" frameborThis 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 '&'.
- Line 537, Column 129: reference to entity "sizeID" for which no system identifier could be generated
…fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" height="600px" frameborThis 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.
- Line 537, Column 121: entity was defined here
…a-4764-9fd3-8b319a86607a&categoryID=8&sizeID=6" width="120px" height="600px" - Line 540, Column 84: document type does not allow element "a" here
…/bilgisayar-internet-webtasarim.htm">Bilgisayar İnternet WebTasarımThe 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).
- Line 554, Column 33: ID "header" already defined
<div class="header"><h1 id="header"><span>Kodarsivim.tr.gg | Html Kodlar & CAn "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).
- Line 494, Column 10: ID "header" first defined here
<div id="header"> - Line 554, Column 78: character "&" is the first character of a delimiter but occurred as data
…span>Kodarsivim.tr.gg | Html Kodlar & Css Tasarımlar & JavaScript KodlarThis message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
- Line 554, Column 100: character "&" is the first character of a delimiter but occurred as data
…| Html Kodlar & Css Tasarımlar & JavaScript Kodlar</span></h1></div>This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
- Line 558, Column 53: document type does not allow element "style" here
…eading"><span><style type="text/css"> <!-- td.nav {visibility:hidThe 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).
- Line 574, Column 13: ID "content" already defined
<div id="content">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).
- Line 516, Column 10: ID "content" first defined here
<div id="content"> - Line 1563, Column 156: required attribute "alt" not specified
…webme.com/pic/y/yaristurkiye/yt.jpg"></a></center></div> <div id="sidebar_cThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. - Line 1563, Column 160: end tag for "img" omitted, but OMITTAG NO was specified
…e.com/pic/y/yaristurkiye/yt.jpg"></a></center></div> <div id="sidebar_contaYou may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 1563, Column 87: start tag was here
…href="http://www.yaristurkiye.tr.gg"><img border="0" src="http://img.webme.co - Line 1576, Column 62: character "&" is the first character of a delimiter but occurred as data
…ss-validator/check/referer">CSS</a> & <a href="http://validator.w3.org/check?This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
- Line 1588, Column 169: required attribute "alt" not specified
…f" style="border: 0px solid #000000"></a> <a href="http://www.webservis.gen.tThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. - Line 1588, Column 173: end tag for "img" omitted, but OMITTAG NO was specified
…tyle="border: 0px solid #000000"></a> <a href="http://www.webservis.gen.tr/KaYou may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 1588, Column 79: start tag was here
…ank" href="http://www.haninerde.com"><img src="http://www.haninerde.com/img/r - Line 1589, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<img src=http://logo.webservis.gen.tr/logo/1.gif alt="WebTasarım" border="0 - Line 1589, Column 16: NET-enabling start-tag not immediately followed by null end-tag
<img src=http://logo.webservis.gen.tr/logo/1.gif alt="WebTasarım" border="0This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).
- Line 1589, Column 16: required attribute "alt" not specified
<img src=http://logo.webservis.gen.tr/logo/1.gif alt="WebTasarım" border="0The 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. - Line 1589, Column 16: end tag for "img" omitted, but OMITTAG NO was specified
<img src=http://logo.webservis.gen.tr/logo/1.gif alt="WebTasarım" border="0You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
- Line 1589: start tag was here
0<img src=http://logo.webservis.gen.tr/logo/1.gif alt="WebTasarım" border="0 - Line 1590, Column 30: required attribute "type" not specified
<script language="javascript"> var wuser="kodarsivim", wbanner="1";</script>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. - Line 1591, Column 72: required attribute "type" not specified
…http://logo.webservis.gen.tr/web.js"></script><!--LiveInternet counter--><scrThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. - Line 1600, Column 208: end tag for element "span" which is not open
…l=www.kodarsivim.tr.gg" /></a></span>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
- Line 1604, Column 18: Attribute "LANGUAGE" is not a valid attribute. Did you mean "language"?
<SCRIPT LANGUAGE='JavaScript'>You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
- Line 1604, Column 30: element "SCRIPT" undefined. Did you mean "script"?
<SCRIPT LANGUAGE='JavaScript'>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).
- Line 1644, Column 99: cannot generate system identifier for general entity "auth1"
…sten.de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae8696f8fb68bdb1d3d9&auAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 1644, Column 99: general entity "auth1" not defined and no default entity
…sten.de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae8696f8fb68bdb1d3d9&auThis 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.
- Line 1644, Column 104: reference not terminated by REFC delimiter
…de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae8696f8fb68bdb1d3d9&auth2=dIf 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.
- Line 1644, Column 104: reference to external entity in attribute value
…de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae8696f8fb68bdb1d3d9&auth2=dThis 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 '&'.
- Line 1644, Column 104: reference to entity "auth1" for which no system identifier could be generated
…de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae8696f8fb68bdb1d3d9&auth2=dThis 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.
- Line 1644, Column 97: entity was defined here
…kasten.de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae8696f8fb68bdb1d3d9& - Line 1644, Column 138: cannot generate system identifier for general entity "auth2"
…h1=927ca0a65a48ae8696f8fb68bdb1d3d9&auth2=d4b5fc0614a2d2801537111a37fb10ae&auAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 1644, Column 138: general entity "auth2" not defined and no default entity
…h1=927ca0a65a48ae8696f8fb68bdb1d3d9&auth2=d4b5fc0614a2d2801537111a37fb10ae&auThis 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.
- Line 1644, Column 143: reference not terminated by REFC delimiter
…7ca0a65a48ae8696f8fb68bdb1d3d9&auth2=d4b5fc0614a2d2801537111a37fb10ae&auth3=6If 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.
- Line 1644, Column 143: reference to external entity in attribute value
…7ca0a65a48ae8696f8fb68bdb1d3d9&auth2=d4b5fc0614a2d2801537111a37fb10ae&auth3=6This 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 '&'.
- Line 1644, Column 143: reference to entity "auth2" for which no system identifier could be generated
…7ca0a65a48ae8696f8fb68bdb1d3d9&auth2=d4b5fc0614a2d2801537111a37fb10ae&auth3=6This 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.
- Line 1644, Column 136: entity was defined here
…uth1=927ca0a65a48ae8696f8fb68bdb1d3d9&auth2=d4b5fc0614a2d2801537111a37fb10ae& - Line 1644, Column 177: cannot generate system identifier for general entity "auth3"
…h2=d4b5fc0614a2d2801537111a37fb10ae&auth3=64ef34f6d37e78b67d8c0782433d22d8&auAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 1644, Column 177: general entity "auth3" not defined and no default entity
…h2=d4b5fc0614a2d2801537111a37fb10ae&auth3=64ef34f6d37e78b67d8c0782433d22d8&auThis 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.
- Line 1644, Column 182: reference not terminated by REFC delimiter
…b5fc0614a2d2801537111a37fb10ae&auth3=64ef34f6d37e78b67d8c0782433d22d8&auth4=4If 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.
- Line 1644, Column 182: reference to external entity in attribute value
…b5fc0614a2d2801537111a37fb10ae&auth3=64ef34f6d37e78b67d8c0782433d22d8&auth4=4This 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 '&'.
- Line 1644, Column 182: reference to entity "auth3" for which no system identifier could be generated
…b5fc0614a2d2801537111a37fb10ae&auth3=64ef34f6d37e78b67d8c0782433d22d8&auth4=4This 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.
- Line 1644, Column 175: entity was defined here
…uth2=d4b5fc0614a2d2801537111a37fb10ae&auth3=64ef34f6d37e78b67d8c0782433d22d8& - Line 1644, Column 216: cannot generate system identifier for general entity "auth4"
…h3=64ef34f6d37e78b67d8c0782433d22d8&auth4=40b074b2111be6176c44e71d79f9882a&auAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 1644, Column 216: general entity "auth4" not defined and no default entity
…h3=64ef34f6d37e78b67d8c0782433d22d8&auth4=40b074b2111be6176c44e71d79f9882a&auThis 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.
- Line 1644, Column 221: reference not terminated by REFC delimiter
…ef34f6d37e78b67d8c0782433d22d8&auth4=40b074b2111be6176c44e71d79f9882a&auth5=9If 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.
- Line 1644, Column 221: reference to external entity in attribute value
…ef34f6d37e78b67d8c0782433d22d8&auth4=40b074b2111be6176c44e71d79f9882a&auth5=9This 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 '&'.
- Line 1644, Column 221: reference to entity "auth4" for which no system identifier could be generated
…ef34f6d37e78b67d8c0782433d22d8&auth4=40b074b2111be6176c44e71d79f9882a&auth5=9This 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.
- Line 1644, Column 214: entity was defined here
…uth3=64ef34f6d37e78b67d8c0782433d22d8&auth4=40b074b2111be6176c44e71d79f9882a& - Line 1644, Column 255: cannot generate system identifier for general entity "auth5"
…h4=40b074b2111be6176c44e71d79f9882a&auth5=9b9531e5af39dff040c14d4370c3ab59&moAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 1644, Column 255: general entity "auth5" not defined and no default entity
…h4=40b074b2111be6176c44e71d79f9882a&auth5=9b9531e5af39dff040c14d4370c3ab59&moThis 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.
- Line 1644, Column 260: reference not terminated by REFC delimiter
…b074b2111be6176c44e71d79f9882a&auth5=9b9531e5af39dff040c14d4370c3ab59&mode=trIf 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.
- Line 1644, Column 260: reference to external entity in attribute value
…b074b2111be6176c44e71d79f9882a&auth5=9b9531e5af39dff040c14d4370c3ab59&mode=trThis 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 '&'.
- Line 1644, Column 260: reference to entity "auth5" for which no system identifier could be generated
…b074b2111be6176c44e71d79f9882a&auth5=9b9531e5af39dff040c14d4370c3ab59&mode=trThis 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.
- Line 1644, Column 253: entity was defined here
…uth4=40b074b2111be6176c44e71d79f9882a&auth5=9b9531e5af39dff040c14d4370c3ab59& - Line 1644, Column 294: cannot generate system identifier for general entity "mode"
…h5=9b9531e5af39dff040c14d4370c3ab59&mode=track" style="display:none;width:1pxAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 1644, Column 294: general entity "mode" not defined and no default entity
…h5=9b9531e5af39dff040c14d4370c3ab59&mode=track" style="display:none;width:1pxThis 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.
- Line 1644, Column 298: reference not terminated by REFC delimiter
…b9531e5af39dff040c14d4370c3ab59&mode=track" style="display:none;width:1px;heiIf 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.
- Line 1644, Column 298: reference to external entity in attribute value
…b9531e5af39dff040c14d4370c3ab59&mode=track" style="display:none;width:1px;heiThis 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 '&'.
- Line 1644, Column 298: reference to entity "mode" for which no system identifier could be generated
…b9531e5af39dff040c14d4370c3ab59&mode=track" style="display:none;width:1px;heiThis 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.
- Line 1644, Column 292: entity was defined here
…uth5=9b9531e5af39dff040c14d4370c3ab59&mode=track" style="display:none;width:1 - Line 11, Column 41: XML Parsing Error: xmlParseEntityRef: no name
…itle>Kodarsivim.tr.gg | Html Kodlar & Css Tasarımlar & JavaScript Kodlar - Line 11, Column 63: XML Parsing Error: xmlParseEntityRef: no name
…| Html Kodlar & Css Tasarımlar & JavaScript Kodlar - Html Kodlar</title> - Line 537, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…com/advEngine.aspx?accountID=02f855d5-bb6a-4764-9fd3-8b319a86607a&categoryID=… - Line 537, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…com/advEngine.aspx?accountID=02f855d5-bb6a-4764-9fd3-8b319a86607a&categoryID=… - Line 554, Column 78: XML Parsing Error: xmlParseEntityRef: no name
…span>Kodarsivim.tr.gg | Html Kodlar & Css Tasarımlar & JavaScript Kodlar - Line 554, Column > 80: XML Parsing Error: xmlParseEntityRef: no name
…an>Kodarsivim.tr.gg | Html Kodlar & Css Tasarımlar & JavaScript Kodlar</… - Line 1563, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1563 and a
…ter><a href="http://www.yaristurkiye.tr.gg"><img border="0" src="http://img.w… - Line 1563, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 1563 and center
…ter><a href="http://www.yaristurkiye.tr.gg"><img border="0" src="http://img.w… - Line 1563, Column > 80: XML Parsing Error: Opening and ending tag mismatch: center line 1563 and div
…ter><a href="http://www.yaristurkiye.tr.gg"><img border="0" src="http://img.w… - Line 1576, Column 62: XML Parsing Error: xmlParseEntityRef: no name
…ss-validator/check/referer">CSS</a> & <a href="http://validator.w3.org/check? - Line 1588, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1588 and a
…nk" href="http://www.haninerde.com"><img src="http://www.haninerde.com/img/re… - Line 1589, Column 9: XML Parsing Error: AttValue: " or ' expected
<img src=http://logo.webservis.gen.tr/logo/1.gif alt="WebTasarım" border="0 - Line 1589, Column 9: XML Parsing Error: attributes construct error
<img src=http://logo.webservis.gen.tr/logo/1.gif alt="WebTasarım" border="0 - Line 1589, Column 9: XML Parsing Error: Couldn't find end of Start Tag img line 1589
<img src=http://logo.webservis.gen.tr/logo/1.gif alt="WebTasarım" border="0 - Line 1600, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 1588 and span
…"http://www.googlepagerankchecker.com/"><img border="0" alt="Pagerank" src="h… - Line 1644, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…/www.homepage-baukasten.de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae86… - Line 1644, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…/www.homepage-baukasten.de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae86… - Line 1644, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…/www.homepage-baukasten.de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae86… - Line 1644, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…/www.homepage-baukasten.de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae86… - Line 1644, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…/www.homepage-baukasten.de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae86… - Line 1644, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…/www.homepage-baukasten.de/cookie.php?visit=kodarsivim&auth1=927ca0a65a48ae86… - Line 1651, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 493 and body
</body> - Line 1652, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 474 and html
</html> - Line 1652, Column 7: XML Parsing Error: Premature end of data in tag html line 2
</html>