Bug #38095
Invalides HTML bei Standard-Template
| Status: | Resolved | Start date: | 2012-06-15 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
Das Standardtemplate erzeugt invalides HTML. Insbesondere führen (abgesehen von einem fehlenden <b>-Tag) fehlerhafte ID-Attribute an Stelle von class-Attributen hier zu Fehlern.
Auch sollte die Suchbox besser mit class-Attributen versehen werden, damit man eine Suchbox in die Navigation, und eine zusäzliche auf der Suchen-Seite einfügen kann.
Anbei der Sermon des W3-Validators (http://validator.w3.org):
Validation Output: 12 Errors
Error Line 256, Column 134: end tag for element "b" which is not open
…arch_pi1[sword]" value="Suchbegriff" onfocus=" searchboxFocus(this); " /></b>
✉
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.
Error Line 279, Column 24: ID "xajax_form_kesearch_pi1" already defined
<form method="get" id="xajax_form_kesearch_pi1" name="xajax_form_kesearch_pi1" …
✉
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 251, Column 24: ID "xajax_form_kesearch_pi1" first defined here
<form method="get" id="xajax_form_kesearch_pi1" name="xajax_form_kesearch_pi1" …
Error Line 284, Column 26: ID "ke_search_sword" already defined
<input type="text" id="ke_search_sword" name="tx_kesearch_pi1[sword]" 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 256, Column 26: ID "ke_search_sword" first defined here
<input type="text" id="ke_search_sword" name="tx_kesearch_pi1[sword]" value=…
Error Line 284, Column 134: end tag for element "b" which is not open
…arch_pi1[sword]" value="Suchbegriff" onfocus=" searchboxFocus(this); " /></b>
✉
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.
Error Line 285, Column 27: ID "kesearch_submit" already defined
<input type="image" id="kesearch_submit" src="typo3conf/ext/ke_search/res/img…
✉
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 257, Column 27: ID "kesearch_submit" first defined here
<input type="image" id="kesearch_submit" src="typo3conf/ext/ke_search/res/img…
Error Line 289, Column 13: ID "pagenumber" already defined
<input id="pagenumber" type="hidden" name="tx_kesearch_pi1[page]" value="1" />
✉
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 261, Column 13: ID "pagenumber" first defined here
<input id="pagenumber" type="hidden" name="tx_kesearch_pi1[page]" value="1" />
Error Line 290, Column 13: ID "resetFilters" already defined
<input id="resetFilters" type="hidden" name="tx_kesearch_pi1[resetFilters]" va…
✉
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 262, Column 13: ID "resetFilters" first defined here
<input id="resetFilters" type="hidden" name="tx_kesearch_pi1[resetFilters]" va…
Error Line 291, Column 13: ID "sortByField" already defined
<input id="sortByField" type="hidden" name="tx_kesearch_pi1[sortByField]" valu…
✉
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 263, Column 13: ID "sortByField" first defined here
<input id="sortByField" type="hidden" name="tx_kesearch_pi1[sortByField]" valu…
Error Line 292, Column 13: ID "sortByDir" already defined
<input id="sortByDir" type="hidden" name="tx_kesearch_pi1[sortByDir]" 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 264, Column 13: ID "sortByDir" first defined here
<input id="sortByDir" type="hidden" name="tx_kesearch_pi1[sortByDir]" value=""…
Error Line 294, Column 11: ID "kesearch_filters" already defined
<div id="kesearch_filters"></div>
✉
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 266, Column 11: ID "kesearch_filters" first defined here
<div id="kesearch_filters"></div>
Error Line 297, Column 11: ID "kesearch_updating_filters" already defined
<div id="kesearch_updating_filters"><center><img id="kesearch_spinner_filters"…
✉
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 269, Column 11: ID "kesearch_updating_filters" first defined here
<div id="kesearch_updating_filters"><center><img id="kesearch_spinner_filters"…
Error Line 297, Column 55: ID "kesearch_spinner_filters" already defined
…ch_updating_filters"><center><img id="kesearch_spinner_filters" src="typo3conf…
✉
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 269, Column 55: ID "kesearch_spinner_filters" first defined here
…ch_updating_filters"><center><img id="kesearch_spinner_filters" src="typo3conf…
History
Updated by Caroli 11 months ago
Irgendein Cache-Fehler hat zu den Duplizierungen geführt. Der Fehler mit dem <b>-Tag bleibt bestehen.
Außerdem wäre es nett, qzwecks Einbindung einer zusätzlichen Search-Box in der Navigation entweder auf class-Attribute umzu steigen bzw. Vorschlag #38096 umzusetzen.
Updated by Christian Buelter 11 months ago
- Status changed from New to Accepted
Updated by Christian Buelter 10 months ago
- Status changed from Accepted to Resolved
The validating issues have been fixed in revision 64826.
Issue 38096 is not a ke_search issue ("Use dispatcher for setup extension").
If you want to style two different searchbox on your site differently by now, you can use your own HTML template and change the attributes.
Updated by Christian Buelter 10 months ago
Please note that you cannot have two searchboxes on one page in AJAX mode. Please use the static mode instead.