Make WordPress Core

Opened 10 years ago

Closed 10 years ago

#30113 closed enhancement (wontfix)

Twenty Fifteen: Translation-ready search form

Reported by: sdavis2702's profile sdavis2702 Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.1
Component: Bundled Theme Keywords: has-patch dev-feedback
Focuses: Cc:

Description

Twenty Fifteen is translation-ready, of course. But no default theme has included a searchform.php template file since Twenty Eleven. I don't understand why.

With search form markup being part of core and going so far as to intentionally use the HTML5 form in Twenty Fifteen, which puts the search input field placeholder text right on the screen, I think the search form should be translation-ready using the theme's text domain.

Attachments (1)

searchform.diff (1.1 KB) - added by sdavis2702 10 years ago.
search form template file

Download all attachments as: .zip

Change History (6)

@sdavis2702
10 years ago

search form template file

#1 @voldemortensen
10 years ago

  • Component changed from I18N to Bundled Theme
  • Keywords has-patch dev-feedback added

#2 @SergeyBiryukov
10 years ago

I think the goal is for bundled themes to use the core functionality where possible instead of overriding it with custom templates.

We could probably add a new argument for get_search_form() to provide a custom placeholder string, but what's wrong with using the core string?

#3 @sdavis2702
10 years ago

I thought about that not too long after opening this ticket. I think I associate get_search_form() with the theme so much because of how often it's used in themes and the fact that it's almost always front-facing on every site.

But if get_search_form() needed to be overwritten in a theme for the translation purposes, so would comment_form(), the protected post password form, etc. So no... after more thought, I actually disagree with my own ticket now.

Feel free to close!

This ticket was mentioned in Slack in #core-themes by iandstewart. View the logs.


10 years ago

#5 @iandstewart
10 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.