Hello Blocksy Support,<\/p>\n\n\n\n
I’m using the free version of Blocksy with the Blocksy Companion plugin.<\/p>\n\n\n\n
My current versions are:<\/p>\n\n\n\n
I have a simple custom Amazon search form in the Header Builder \u2192 HTML element<\/strong>. This was working correctly before the most recent Blocksy\/Blocksy Companion update.<\/p>\n\n\n\n The form is a basic Amazon search: Before the recent update, the form displayed correctly in the header and the Amazon search worked correctly.<\/p>\n\n\n\n After updating Blocksy and Blocksy Companion, the Search button still appears, but the I initially thought this was a CSS problem, so I tested it extensively. However, I checked the actual HTML source of the published page and the I also performed a controlled test using three completely different input elements: On the published frontend, the resulting HTML contains the textarea and button, but all three The resulting HTML is essentially: There is no I have also confirmed that the original form works correctly when placed in a normal WordPress page. The same form also appears correctly inside the Customizer preview for the Header HTML element.<\/p>\n\n\n\n So the problem appears to occur specifically when Blocksy saves\/renders the HTML element for the live frontend.<\/p>\n\n\n\n Could you please investigate whether Blocksy 2.1.58 or Blocksy Companion 2.1.58 introduced a change to the sanitization or output processing of the Header HTML element that removes If this is intentional, is there a recommended way to place a custom HTML form containing If it is a regression, could you please advise whether there is a workaround or fix?<\/p>\n\n\n\n I have deliberately not added any CSS workaround because the Thank you.<\/p>\n","protected":false},"template":"","class_list":["post-19035371","topic","type-topic","status-publish","hentry","topic-tag-form","topic-tag-header","topic-tag-update"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19035371","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":1,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19035371\/revisions"}],"predecessor-version":[{"id":19035392,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19035371\/revisions\/19035392"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=19035371"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<form action=\"https:\/\/www.amazon.com\/s\" method=\"get\" target=\"_blank\"> <input type=\"text\" name=\"k\" required placeholder=\"Search Amazon...\"> <button type=\"submit\">Search<\/button> <\/form><\/code><\/p>\n\n\n\n<input><\/code> field disappears completely from the published frontend<\/strong>.<\/p>\n\n\n\n<input><\/code> element is not present in the generated HTML at all.<\/p>\n\n\n\n<div style=\"background:#eee;padding:8px;border:1px solid #ddd\"> TEST 1: <input type=\"text\" value=\"TEXT INPUT\"> TEST 2: <input value=\"PLAIN INPUT\"> TEST 3: <input type=\"search\" value=\"SEARCH INPUT\"> TEST 4: <textarea rows=\"1\">TEXTAREA<\/textarea> <button type=\"button\">BUTTON<\/button> <\/div><\/code><\/p>\n\n\n\n<input><\/code> elements have been removed<\/strong>.<\/p>\n\n\n\n<div style=\"background:#eee;padding:8px;border:1px solid #ddd\"> TEST 1: TEST 2: TEST 3: TEST 4: <textarea rows=\"1\">TEXTAREA<\/textarea> <button type=\"button\">BUTTON<\/button> <\/div><\/code><\/p>\n\n\n\n<input><\/code> element in the published HTML.<\/p>\n\n\n\n<input><\/code> elements?<\/p>\n\n\n\n<input><\/code> fields in the Blocksy free header?<\/p>\n\n\n\n<input><\/code> element is actually missing from the generated HTML rather than merely being hidden by CSS.<\/p>\n\n\n\n