Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.hi Jennifer,
there are two validation errors on the search_pages form in XHTML 1.0 Strict. From http://validator.w3.org/
Validation Output: 2 Errors
1. Error Line 68, Column 76: value of attribute "method" cannot be "POST"; must be one of "get", "post"
… accept-charset="UTF-8" method="POST" id="-search-by-page-form" class="search
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.
2. Error Line 68, Column 82: value of attribute "id" invalid: "-" cannot start a name
…t-charset="UTF-8" method="POST" id="-search-by-page-form" class="search-by-pa
It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.
patch coming next
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | search_by_page_556820_1.patch | 1.76 KB | scottrigby |
Comments
Comment #1
scottrigbythis patch sorts out the 2 validation errors:
1st part replaces all instances of "_search_by_page_form" with "search_by_page_form" (including "_search_by_page_form_submit"), so the form id becomes "search-by-page-form" rather than id="-search-by-page-form".
2nd part replaces "POST" with "post"
Comment #2
jhodgdonGood catch, and thanks for the patch! I will add that to the code base sometime soon.
Comment #3
jhodgdonI committed your patch, plus a few other similar fixes to sub-modules (to fix validation errors on the admin screens). This is now fixed in the development branch of Search by Page (6.x-1.x), and fixes will also be in the next regular release (6.x-1.3, whenever that comes out). Commit: http://drupal.org/cvs?commit=255934
Comment #5
jhodgdonJust a note that version 6.x-1.3 is now released with this fix included.