Große Auswahl an Produkten in den Kategorien Allgemeine Seiten, Music Store, Blätterkataloge, Wegbeschreibung, Impressum, Datenschutz, AGB, JobsAllgemeine Seiten., bei Music Store ...

musicstore.de
  • Domain Name
    musicstore.de
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #21766
  • Page Size
    124.2 KB
  • Ip Address
    195.14.229.169
  • Heading
    H1: 0, H2: 1, H3: 28, H4: 0, H5: 0, H6: 0
  • Images
    17 GIF, 32 JPG, 9 PNG

Website Meta Analysis

  • Title
    MUSIC STORE professional - Home
  • Meta Keyword
    Allgemeine Seiten, Music Store, Blätterkataloge, Wegbeschreibung, Impressum, Datenschutz, AGB, Jobs, Shop, kaufen, Musikinstrumente, Music Store, MusicStore
  • Meta Description
    Große Auswahl an Produkten in den Kategorien Allgemeine Seiten, Music Store, Blätterkataloge, Wegbeschreibung, Impressum, Datenschutz, AGB, JobsAllgemeine Seiten., bei Music Store

Technical Analysis

  • Webserver
    Apache/2.0.61 (Unix) mod_ssl/2.0.61 OpenSSL/0.9.7g
  • Ip Address
    195.14.229.169
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from musicstore.de.

HTML Analysis

  • date: Sun, 28 Apr 2013 04:49:42 GMT
  • server: Apache/2.0.61 (Unix) mod_ssl/2.0.61 OpenSSL/0.9.7g
  • cache-control: no-cache,no-store,must-revalidate
  • pragma: no-cache
  • expires: Thu, 01 Dec 1994 16:00:00 GMT
  • vary: User-Agent
  • content-encoding: gzip
  • accept-ranges: bytes
  • content-length: 19511
  • content-type: text/html;charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% Copyright (c) 2010 by DENIC
% Version: 2.0
%
% Restricted rights.
%
% Terms and Conditions of Use
%
% The data in this record is provided by DENIC for informational purposes only.
% DENIC does not guarantee its accuracy and cannot, under any circumstances,
% be held liable in case the stored information would prove to be wrong,
% incomplete or not accurate in any sense.
%
% All the domain data that is visible in the whois service is protected by law.
% It is not permitted to use it for any purpose other than technical or
% administrative requirements associated with the operation of the Internet.
% It is explicitly forbidden to extract, copy and/or use or re-utilise in any
% form and by any means (electronically or not) the whole or a quantitatively
% or qualitatively substantial part of the contents of the whois database
% without prior and explicit written permission by DENIC.
% It is prohibited, in particular, to use it for transmission of unsolicited
% and/or commercial and/or advertising by phone, fax, e-mail or for any similar
% purposes.
%
% By maintaining the connection you assure that you have a legitimate interest
% in the data and that you will only use it for the stated purposes. You are
% aware that DENIC maintains the right to initiate legal proceedings against
% you in the event of any breach of this assurance and to bar you from using
% its whois service.
%
% The DENIC whois service on port 43 never discloses any information concerning
% the domain holder/administrative contact. Information concerning the domain
% holder/administrative contact can be obtained through use of our web-based
% whois service available at the DENIC website:
% http://www.denic.de/en/background/whois-service/webwhois.html
%

Domain: musicstore.de
Nserver: dns1.netcologne.de
Nserver: dns2.netcologne.de
Nserver: dns5.netcologne.de
Status: connect
Changed: 2008-05-27T16:17:02+02:00

[Tech-C]
Type: ROLE
Name: hostmaster NETCOLOGNE
Organisation: NetCologne Ges. fuer Telekommunikation mbH
Address: Am Coloneum 9
PostalCode: 50829
City: Koeln
CountryCode: DE
Phone: +49 221 2222 0
Fax: +49 221 2222 620
Email: email
Remarks: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Remarks: + email is contact for criminal use, spam, etc. +
Remarks: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Changed: 2006-11-16T12:52:10+01:00

[Zone-C]
Type: ROLE
Name: hostmaster NETCOLOGNE
Organisation: NetCologne Ges. fuer Telekommunikation mbH
Address: Am Coloneum 9
PostalCode: 50829
City: Koeln
CountryCode: DE
Phone: +49 221 2222 0
Fax: +49 221 2222 620
Email: email
Remarks: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Remarks: + email is contact for criminal use, spam, etc. +
Remarks: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Changed: 2006-11-16T12:52:10+01:00

DNS Analysis


DNS servers
dns5.netcologne.de [134.95.100.211]
dns2.netcologne.de
dns1.netcologne.de


DNS Records

Answer records
musicstore.de SOA
server: dns1.netcologne.de
email: hostmaster@netcologne.de
serial: 2013010400
refresh: 10800
retry: 3600
expire: 3600000
minimum ttl: 3600
3600s
musicstore.de NS  dns2.netcologne.de 3600s
musicstore.de NS  dns1.netcologne.de 3600s
musicstore.de NS  dns5.netcologne.de 3600s
musicstore.de A 195.14.228.190 600s
musicstore.de MX
preference: 10
exchange: mailrelay.netcologne.de
7200s
musicstore.de TXT v=spf1 include:emsmtp.com include:emarsys.net ~all 3600s

Authority records

Additional records

IP 195.14.229.169 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 195.14.229.169

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 155 Errors
  • 46 Warnings
Ratio Text/Html
  • 0.817221968898882
Message Error
  • Error Line 59, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

    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 59, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  • Error Line 257, Column 10: ID "v-menu3" already defined
    <div id="v-menu3" class="v-menu nb038">

    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 218, Column 10: ID "v-menu3" first defined here
    <div id="v-menu3" class="v-menu" style="display: none; position: absolute; top:…
  • Error Line 263, Column 60: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    	<div style="width: 170px!important;" class="inputBoxStyle">

    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 273, Column 70: ID "LoginForm_Login" already defined
    …text" class="inputText" name="LoginForm_Login" id="LoginForm_Login" value="" />

    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 234, Column 70: ID "LoginForm_Login" first defined here
    …text" class="inputText" name="LoginForm_Login" id="LoginForm_Login" value="" />
  • Error Line 278, Column 78: ID "LoginForm_Password" already defined
    …assword" class="inputText" name="LoginForm_Password" id="LoginForm_Password" />

    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 239, Column 78: ID "LoginForm_Password" first defined here
    …assword" class="inputText" name="LoginForm_Password" id="LoginForm_Password" />
  • Error Line 331, Column 13: there is no attribute "align"
    <span align="right" classs="nb216" onclick="showElement('v-menu');"><img src="/…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 331, Column 28: there is no attribute "classs"
    <span align="right" classs="nb216" onclick="showElement('v-menu');"><img src="/…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 331, Column 182: required attribute "alt" not specified
    …icStore-MusicStoreShop-Site/-/de_DE/images/closesmall.gif" border="0" /></span>

    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 334, Column 8: document type does not allow element "tr" here; assuming missing "table" start-tag
    				<tr>
  • Error Line 356, Column 35: value of attribute "align" cannot be "middle"; must be one of "left", "center", "right", "justify", "char"
    					<td colspan="3" align="middle">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 359, Column 142: required attribute "alt" not specified
    …oreShop-Site/-/de_DE/images/paymenticons/basket_features.gif" class="nb214" /> 

    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 365, Column 144: required attribute "alt" not specified
    …reShop-Site/-/de_DE/images/paymenticons/pp_standard_80x35.gif" class="nb217" />

    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 368, Column 140: required attribute "alt" not specified
    …cStoreShop-Site/-/de_DE/images/paymenticons/lockbox_81x35.png" class="nb217" />

    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 404, Column 120: there is no attribute "autocomplete"
    …pleSearch_NameOrID" id="WFSimpleSearch_NameOrID" value="" autocomplete="off" />

    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 443, Column 23: ID "header" already defined
    <div class="area" id="header">

    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 205, Column 10: ID "header" first defined here
    <div id="header" class="area">
  • Error Line 444, Column 30: there is no attribute "role"
    <div class="navigation" role="navigation">

    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 453, Column 22: there is no attribute "onMouseOver"
    					<li onMouseOver="loadBrandImages('n2DVqHzp8c4AAAEZAHotK5qL', '1W7VqHzpyhgA…

    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 592, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 727, Column 11: ID "flyout-nav" already defined
    	<div id="flyout-nav">

    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 472, Column 11: ID "flyout-nav" first defined here
    	<div id="flyout-nav">
  • Error Line 730, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 735, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 820, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 939, Column 11: ID "flyout-nav" already defined
    	<div id="flyout-nav">

    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 472, Column 11: ID "flyout-nav" first defined here
    	<div id="flyout-nav">
  • Error Line 942, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 947, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1023, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1124, Column 11: ID "flyout-nav" already defined
    	<div id="flyout-nav">

    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 472, Column 11: ID "flyout-nav" first defined here
    	<div id="flyout-nav">
  • Error Line 1127, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 1132, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1163, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1217, Column 11: ID "flyout-nav" already defined
    	<div id="flyout-nav">

    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 472, Column 11: ID "flyout-nav" first defined here
    	<div id="flyout-nav">
  • Error Line 1220, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 1225, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1292, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1393, Column 11: ID "flyout-nav" already defined
    	<div id="flyout-nav">

    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 472, Column 11: ID "flyout-nav" first defined here
    	<div id="flyout-nav">
  • Error Line 1396, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 1401, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1459, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1554, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 1559, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1653, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1770, Column 11: ID "flyout-nav_r" already defined
    	<div id="flyout-nav_r" >

    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 1551, Column 11: ID "flyout-nav_r" first defined here
    	<div id="flyout-nav_r" >
  • Error Line 1773, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 1778, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1854, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 1966, Column 11: ID "flyout-nav_r" already defined
    	<div id="flyout-nav_r" >

    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 1551, Column 11: ID "flyout-nav_r" first defined here
    	<div id="flyout-nav_r" >
  • Error Line 1969, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 1974, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2050, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2149, Column 11: ID "flyout-nav_r" already defined
    	<div id="flyout-nav_r" >

    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 1551, Column 11: ID "flyout-nav_r" first defined here
    	<div id="flyout-nav_r" >
  • Error Line 2152, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 2157, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2215, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2305, Column 11: ID "flyout-nav_r" already defined
    	<div id="flyout-nav_r" >

    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 1551, Column 11: ID "flyout-nav_r" first defined here
    	<div id="flyout-nav_r" >
  • Error Line 2308, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 2313, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2425, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2560, Column 11: ID "flyout-nav_r" already defined
    	<div id="flyout-nav_r" >

    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 1551, Column 11: ID "flyout-nav_r" first defined here
    	<div id="flyout-nav_r" >
  • Error Line 2563, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 2568, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2689, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2842, Column 11: ID "flyout-nav_r" already defined
    	<div id="flyout-nav_r" >

    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 1551, Column 11: ID "flyout-nav_r" first defined here
    	<div id="flyout-nav_r" >
  • Error Line 2845, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 2850, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2890, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 2953, Column 11: ID "flyout-nav_r" already defined
    	<div id="flyout-nav_r" >

    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 1551, Column 11: ID "flyout-nav_r" first defined here
    	<div id="flyout-nav_r" >
  • Error Line 2956, Column 12: ID "flyout-navcontainer" already defined
    		<div id="flyout-navcontainer">

    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 475, Column 12: ID "flyout-navcontainer" first defined here
    		<div id="flyout-navcontainer">
  • Error Line 2961, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 3019, Column 14: ID "flyout-nav-ul" already defined
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">

    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 480, Column 14: ID "flyout-nav-ul" first defined here
    					<ul id="flyout-nav-ul" class="flyout-nav-ul">
  • Error Line 3593, Column 38: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p style="margin: 0px; padding: 0px;"><span style="color: #b80008; font-size: 1…

    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 3597, Column 38: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p style="margin: 0px; padding: 0px;"><span style="color: #b80008;">Unser Katal…

    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 3600, Column 38: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p style="margin: 0px; padding: 0px;"><span style="color: #b80008;">Prominente<…

    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 3603, Column 38: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p style="margin: 0px; padding: 0px;"><span style="color: #b80008;">Online Kata…

    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 3609, Column 44: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …yle="margin: 3px 0 0 0; padding: 0px;">&Uuml;ber<br /><span style="font-size: …

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

  • Warning Line 3677, Column 9: multiple comments in comment declaration
    <!------------------------------------- CSS -----------------------------------…
  • Warning Line 3677, Column 13: multiple comments in comment declaration
    <!------------------------------------- CSS -----------------------------------…
  • Warning Line 3677, Column 17: multiple comments in comment declaration
    <!------------------------------------- CSS -----------------------------------…
  • Warning Line 3677, Column 21: multiple comments in comment declaration
    <!------------------------------------- CSS -----------------------------------…
  • Warning Line 3677, Column 25: multiple comments in comment declaration
    <!------------------------------------- CSS -----------------------------------…
  • Warning Line 3677, Column 29: multiple comments in comment declaration
    <!------------------------------------- CSS -----------------------------------…
  • Warning Line 3677, Column 33: multiple comments in comment declaration
    <!------------------------------------- CSS -----------------------------------…
  • Warning Line 3677, Column 37: multiple comments in comment declaration
    <!------------------------------------- CSS -----------------------------------…
  • Error Line 3677, Column 39: invalid comment declaration: found name character outside comment but inside comment declaration
    <!------------------------------------- CSS -----------------------------------…
  • Info Line 3677, Column 1: comment declaration started here
    <!------------------------------------- CSS -----------------------------------…
  • Error Line 3678, Column 143: document type does not allow element "link" here
    …store.de/intershop/banner/MS_Startseite_slider/css/style_StartseiteSlider.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).

  • Error Line 3678, Column 144: end tag for "link" omitted, but OMITTAG NO was specified
    …store.de/intershop/banner/MS_Startseite_slider/css/style_StartseiteSlider.css">

    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 3678, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="http://images.musicstore.de/inters…
  • Warning Line 3679, Column 9: multiple comments in comment declaration
    <!------------------------------------- THE CONTENT ---------------------------…
  • Warning Line 3679, Column 13: multiple comments in comment declaration
    <!------------------------------------- THE CONTENT ---------------------------…
  • Warning Line 3679, Column 17: multiple comments in comment declaration
    <!------------------------------------- THE CONTENT ---------------------------…
  • Warning Line 3679, Column 21: multiple comments in comment declaration
    <!------------------------------------- THE CONTENT ---------------------------…
  • Warning Line 3679, Column 25: multiple comments in comment declaration
    <!------------------------------------- THE CONTENT ---------------------------…
  • Warning Line 3679, Column 29: multiple comments in comment declaration
    <!------------------------------------- THE CONTENT ---------------------------…
  • Warning Line 3679, Column 33: multiple comments in comment declaration
    <!------------------------------------- THE CONTENT ---------------------------…
  • Warning Line 3679, Column 37: multiple comments in comment declaration
    <!------------------------------------- THE CONTENT ---------------------------…
  • Error Line 3679, Column 39: invalid comment declaration: found name character outside comment but inside comment declaration
    <!------------------------------------- THE CONTENT ---------------------------…
  • Info Line 3679, Column 1: comment declaration started here
    <!------------------------------------- THE CONTENT ---------------------------…
  • Error Line 3686, Column 99: there is no attribute "alt"
    …-alle-news-videos" title="NAMM NEWS 2013" alt="NAMM NEWS 2013" target="_blank">

    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 3687, Column 105: required attribute "alt" not specified
    ….musicstore.de/intershop/banner/MS_Startseite_slider/images/MS_namm-2013.jpg"/>

    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 3693, Column 114: required attribute "alt" not specified
    …re.de/intershop/banner/MS_Startseite_slider/images/MS_mobile-shop-2013_DE.jpg">

    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 3693, Column 115: end tag for "img" omitted, but OMITTAG NO was specified
    …re.de/intershop/banner/MS_Startseite_slider/images/MS_mobile-shop-2013_DE.jpg">

    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 3693, Column 4: start tag was here
    	  <img src="http://images.musicstore.de/intershop/banner/MS_Startseite_slider/…
  • Error Line 3700, Column 208: end tag for "img" omitted, but OMITTAG NO was specified
    …nner/MS_Startseite_slider/images/MS_Musikersuche/MS_Musikersuche_img11917.jpg">

    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 3700, Column 4: start tag was here
    		 <img alt="Music Store - Musikersuche - Finde Musiker und Bands in Deiner Sta…
  • Error Line 3708, Column 153: end tag for "img" omitted, but OMITTAG NO was specified
    …store.de/intershop/banner/MS_Startseite_slider/images/GIT_JJL-Rimowa_2013.jpg">

    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 3708, Column 4: start tag was here
    		 <img alt="Jan-Josef Liefers reist mit RIMOWA" src="http://images.musicstore.…
  • Error Line 3715, Column 116: end tag for "img" omitted, but OMITTAG NO was specified
    …sicstore.de/intershop/banner/MS_Startseite_slider/images/MS_Kleinanzeigen.jpg">

    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 3715, Column 4: start tag was here
    		 <img alt="" src="http://images.musicstore.de/intershop/banner/MS_Startseite_…
  • Warning Line 3741, Column 11: multiple comments in comment declaration
      <!----------------- -------------------->
  • Warning Line 3741, Column 15: multiple comments in comment declaration
      <!----------------- -------------------->
  • Warning Line 3741, Column 19: multiple comments in comment declaration
      <!----------------- -------------------->
  • Error Line 3741, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
      <!----------------- -------------------->
  • Info Line 3741, Column 3: comment declaration started here
      <!----------------- -------------------->
  • Error Line 3766, Column 184: end tag for "img" omitted, but OMITTAG NO was specified
    …Mustang I Combo " title="FENDER Mustang I Combo" border="0" style="border: 0;">

    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 3766, Column 4: start tag was here
    			<img src="http://images.musicstore.de/intershop/banner/_megadeals/GIT0020101…
  • Error Line 3769, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb136">

    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 3776, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb138">

    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 3800, Column 216: end tag for "img" omitted, but OMITTAG NO was specified
    …" title="JACK &amp; DANNY GG Rock Pack Wine Red" border="0" style="border: 0;">

    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 3800, Column 4: start tag was here
    			<img src="http://images.musicstore.de/intershop/banner/_megadeals/GIT0016692…
  • Error Line 3803, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb136">

    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 3810, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb138">

    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 3834, Column 232: end tag for "img" omitted, but OMITTAG NO was specified
    …" title="YAMAHA FG 730 S Tobacco Brown Sunburst" border="0" style="border: 0;">

    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 3834, Column 4: start tag was here
    			<img src="http://images.musicstore.de/intershop/banner/_megadeals/GIT0007261…
  • Error Line 3837, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb136">

    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 3844, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb138">

    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 3868, Column 227: end tag for "img" omitted, but OMITTAG NO was specified
    …D RGBW" title="lightmaXX Platinum Tour Spot PRO" border="0" style="border: 0;">

    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 3868, Column 4: start tag was here
    			<img src="http://images.musicstore.de/intershop/banner/_megadeals/LIG0008285…
  • Error Line 3871, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb136">

    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 3878, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb138">

    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 3902, Column 217: end tag for "img" omitted, but OMITTAG NO was specified
    …/1&quot;, 2-weg" title="YAMAHA MSR 400 Aktivbox" border="0" style="border: 0;">

    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 3902, Column 4: start tag was here
    			<img src="http://images.musicstore.de/intershop/banner/_megadeals/PAH0003324…
  • Error Line 3905, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb136">

    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 3912, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb138">

    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 3936, Column 267: end tag for "img" omitted, but OMITTAG NO was specified
    …udio #BK, inkl. HW, Becken, Hocker &amp; Sticks" border="0" style="border: 0;">

    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 3936, Column 4: start tag was here
    			<img src="http://images.musicstore.de/intershop/banner/_megadeals/DRU131_DE.…
  • Error Line 3939, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb136">

    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 3946, Column 19: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<p class="nb138">

    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 4072, Column 70: ID "LoginForm_Login" already defined
    …text" class="inputText" name="LoginForm_Login" id="LoginForm_Login" value="" />

    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 234, Column 70: ID "LoginForm_Login" first defined here
    …text" class="inputText" name="LoginForm_Login" id="LoginForm_Login" value="" />
  • Error Line 4077, Column 78: ID "LoginForm_Password" already defined
    …assword" class="inputText" name="LoginForm_Password" id="LoginForm_Password" />

    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 239, Column 78: ID "LoginForm_Password" first defined here
    …assword" class="inputText" name="LoginForm_Password" id="LoginForm_Password" />
  • Error Line 4368, Column 43: end tag for "input" omitted, but OMITTAG NO was specified
    value="X53A4280C6C3D29BF56842FB548A0C4DB">

    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 4367, Column 10: start tag was here
    "_blank"><input name="shop_id" type="hidden" 
  • Error Line 4370, Column 41: there is no attribute "bordercolor"
    "border-collapse: collapse" bordercolor="#111111" width="170"

    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 4380, Column 8: there is no attribute "valign"
    valign="middle"><tr><td width="80"><div align="center">

    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 4385, Column 44: there is no attribute "border"
    <p align="left"><input type="image" border="0" src=

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 4388, Column 31: there is no attribute "width"
    name="I1" align="right" width="70" height="70"><a target="_blank"

    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 4388, Column 43: there is no attribute "height"
    name="I1" align="right" width="70" height="70"><a target="_blank"

    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 4388, Column 48: end tag for "input" omitted, but OMITTAG NO was specified
    name="I1" align="right" width="70" height="70"><a target="_blank"

    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 4385, Column 17: start tag was here
    <p align="left"><input type="image" border="0" src=
  • Error Line 4454, Column 129: there is no attribute "align"
    …RightPanel=true"  class="nb103" align="center">Auslandsversandinfo hier</a>)</…

    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 4740, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    …p.static/WFS/MusicStore-MusicStoreShop-Site/-/de_DE/images/boxes/CallBack.gif">

    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 4740, Column 4: start tag was here
    			<img width="156" border="0" title="Kostenlosen Rückruf erbitten" alt="Kosten…
  • Error Line 4918, Column 38: ID "toggle3" already defined
    <span class="newtop"><a href="#" id="toggle3" title="Sign up for Newsletter." o…

    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 256, Column 38: ID "toggle3" first defined here
    <span class="newtop"><a href="#" id="toggle3" title="Sign up for Newsletter." o…
  • Error Line 4919, Column 10: ID "v-menu3" already defined
    <div id="v-menu3" class="v-menu nb038">

    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 218, Column 10: ID "v-menu3" first defined here
    <div id="v-menu3" class="v-menu" style="display: none; position: absolute; top:…
  • Error Line 4925, Column 60: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    	<div style="width: 170px!important;" class="inputBoxStyle">

    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 4935, Column 70: ID "LoginForm_Login" already defined
    …text" class="inputText" name="LoginForm_Login" id="LoginForm_Login" value="" />

    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 234, Column 70: ID "LoginForm_Login" first defined here
    …text" class="inputText" name="LoginForm_Login" id="LoginForm_Login" value="" />
  • Error Line 4940, Column 78: ID "LoginForm_Password" already defined
    …assword" class="inputText" name="LoginForm_Password" id="LoginForm_Password" />

    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 239, Column 78: ID "LoginForm_Password" first defined here
    …assword" class="inputText" name="LoginForm_Password" id="LoginForm_Password" />
  • Warning Line 4981, Column 44: cannot generate system identifier for general entity "CatalogUUID"
    … "CatalogCategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandIma…

    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 4981, Column 44: general entity "CatalogUUID" not defined and no default entity
    … "CatalogCategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandIma…

    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 4981, Column 55: reference not terminated by REFC delimiter
    …CategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandImages=true",

    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.

  • Error Line 4981, Column 55: reference to entity "CatalogUUID" for which no system identifier could be generated
    …CategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandImages=true",

    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 4981, Column 43: entity was defined here
    …: "CatalogCategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandIm…
  • Warning Line 4981, Column 72: cannot generate system identifier for general entity "loadBrandImages"
    …CategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandImages=true",

    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 4981, Column 72: general entity "loadBrandImages" not defined and no default entity
    …CategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandImages=true",

    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 4981, Column 87: reference not terminated by REFC delimiter
    …CategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandImages=true",

    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.

  • Error Line 4981, Column 87: reference to entity "loadBrandImages" for which no system identifier could be generated
    …CategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandImages=true",

    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 4981, Column 71: entity was defined here
    …CategoryID="+catalogRootId+"&CatalogUUID="+catalogUUID+"&loadBrandImages=true",

Visitor Analysis

Daily Visitor
  • 5.483 visits
Daily Visitor