WooCommerce, Easy Digital Download, and WP e-Commerce plugins

Say What? Pro

Awesome — Steve
This has become one of my favorite plugins. Easy to use and gives you so much customization options for text.
Great Timely Accurate Support — Rob
I was having trouble finding some phrases in woocommerce to translate that were not related to his product. Lee immediately helped me resolve the issues I was having. He also followed up to make sure everything was okay. He provided great support! Well worth the cost.
Its great! — Sana
It does what it says! And it is lightweight! Thank you!

Change text on your WordPress site without hacking files, and without setting up complicated translation tools and files.

Love it!
I thought I would find a translation myself but after 2 hours I opted for the PRO version and I had managed to translate my sentence in less than 30 seconds. It is really worth it!
— Yannick

Say What? offers a simple easy to use tool that lets you set up replacements for strings used by WordPress, and your favourite plugins. Want to rename your “cart” to a “basket”? or “checkout” to “buy now”? – then look no further.

An upgrade from the hugely popular free version, the Pro version:

lets you easily find the right string to override with string discovery and autocompletion
supports string discovery of Javascript-rendered translatable strings, e.g. Gutenberg editor, WooCommerce blocks etc. (requires WordPress 5.7 or higher)
supports setting up of different replacements for different languages using multi-lingual replacements
- WPML, Babble, Polylang, WPGlobus, and Weglot are all currently supported.
allows easily backup and sharing of common string changes with export & import feature (online or using WP-CLI)
features improved performance compared to the free plugin using domain-specific filters

Find out more…

Super easy to use
I have used the LocoTranslate and String Locator plugins before and found Say What much easier to use than both of them. I was able to locate and replace some text on my website within seconds without having to do any complex steps that made me nervous I might break something.
— Ashley

TAG : change, override, text, translation, WordPress
CATEGORY : Easy Digital Downloads, Featured, WooCommerce, WordPress, WP e-Commerce

5.0.1

Fix: Resolve issue with database structure incorrect if plugin installed on v5.0.0

5.0.0

New: Support for disabling replacements
Fix: Broaden file types accepted for import to avoid issues with browsers sending incorrect MIME types

4.0.2

Fix: Remove dependency on lodash solving some plugin conflicts

4.0.1

Fix: Resolve issue where the plugin wouldn't run on PHP versions older than v7.3

4.0.0

New: Supports string discovery of Javascript-rendered translatable strings (requires WordPress 5.7)
New: Supports overriding of Javascript-rendered translatable strings (requires WordPress 5.7)

3.0.1

Fix: Resolve issue where listing table not rendered on narrow screen widths

3.0.0

Change: Use domain-specific filters when available for improved performance

2.8.0

New: Add support for searching replacements list
Fix: String Discovery suggestions that differ only in case sometimes weren't shown
Fix: Some strings in the plugin not marked up for translation
Fix: Resolve issue where bulk actions didn't redirect properly on completion

2.7.1

Order replacement suggestions by length for ease of use

2.7.0

New: Allow language-specific translations to be set without multi-lingual plugin installed
New: Support for admin-area user-locales when determining multi-lingual replacements

2.6.1

Fix deprecated function calls when sorting replacement list

2.6.0

Fix issue where locale not always detected correctly with Polylang

2.5.5

General maintenance updates

2.5.4

New: When importing replacements, unrecognised IDs will be treated as INSERTs, not ignored

2.5.3

New: Add settings link on WordPress plugins page

2.5.2

Fix: PHP minimum version checks didn't always fire correctly.
New: Online imports can now do insert or replace if ID provided
New: Include POT file for easy translation of the plugin

2.5.1

Better autocomplete admin behaviour when no matches / suggestions found
Internal reworking, and test improvements

2.5.0

Allow String Discovery to search for strings by translated version, not just original
Admin UI cleanups

2.4.0

If using multi-lingual, sort active languages to the top of the language list.

2.3.0

Add new "wildcard" feature for replacing a fragment in all strings on a site
Allow bulk actions for bulk deleting on admin screens

2.7

Enable multilingual features if Weglot is active

2.2.6

Better on-boarding where the plugin is installed as an upgrade to the free version.

2.2.4

Fix importer issues with odd Windows mime types
Fix issue where autocomplete suggestions that differed in case would only show one version

2.2.3

Fix issue where imports could fail and / or raise warnings under some circumstances

2.2.2

Fix issues where export would sometimes fail with "Headers already sent" message

2.2.1

Fix issue where "English (United States)" isn't available as a choice when setting up multi-lingual strings.

2.2

Fix performance issues that showed up on some configurations with the 2.1 release.

2.1

Multi-language support - allow different replacements to be set per-language.

2.0.1

Fix issues with double encoding on admin screens for some strings

2.0

Import and export through the admin screens
REQUIRES PHP 5.3 or higher.

1.9

Fixes, and better support for multi-line strings.

1.8

Fix user interface issues in admin area when used with a RTL language.

1.7

Add support for pluralised replacements : _n() and _nx()

1.6

Remove unneeded output on plugin admin screen.

1.5

Introduce filter that allows back compatibility for plugins that change their text-domain.

1.4

Responsive table support for WordPress 4.3
Clearer, more consistent row actions on admin table.

1.3

Fix issues saving string replacements with HTML / HTML entities in them.

1.2

Fix autocomplete for sites running in subfolders.
Avoid duplicates in the available table being returned in autocomplete suggestions.

1.1

Fix issues with string autocomplete on older MySQL releases

1.0

Initial release