Deprecating the Search Banner theme component

[lindsey (Lindsey Fogle)]

I’ll let my colleague who created the script help with the first part of your question, but for the last two questions:

@pfaffman

So for people who don’t understand how to do this, they just lose all of their old settings and customized text, right?

No.

The script is one option; manual migration is another option. That is why we provided very clear descriptions of how the theme component’s settings / strings map to the welcome banner’s settings / strings.

@lindsey

Manual migration

Here’s a map of how the Search Banner theme component’s site texts and settings relate to the same features for the core welcome banner:

Setting description	Search Banner theme component	Welcome Banner core feature
The heading text shown on the welcome banner.	search_banner.headline site text	js.welcome_banner.header.anonymous_members and js.welcome_banner.header.logged_in_members site texts
The subheading text shown on the welcome banner.	search_banner.subhead site text	js.welcome_banner.subheader.anonymous_members and js.welcome_banner.subheader.logged_in_members site texts
The text used for the search button on the banner. *	search_banner.search_button_text site text	js.welcome_banner.search_placeholder site text
Setting to determine which pages display the welcome banner.	show on theme component setting	Welcome banner page visibility site setting
Setting to determine where on the page the welcome banner appears.	plugin outlet theme component setting	Welcome banner location site setting
Background image used on the welcome banner.	background image light theme component setting	Welcome banner image site setting

@pfaffman

What about the people who don’t upgrade again until March? They can still run those rake tasks then? I’m not clear what the importance of 15 December is.

December 15 is when we are completing our migration of hosted customers and when we will officially stop supporting / maintaining the Search Banner component. We are recommending that other users of this component migrate before then so they’re not caught off guard when the theme component becomes incompatible with Discourse core in the future.

If folks choose to wait until later, they should still be able to run these tasks or perform the migration manually, but in the meantime they will be running an unsupported theme component.