Change "Proceed to checkout" Button

@chrisgeist:
Hi Chris,
thanks for your feedback!

“Codestyling Localization” is not compatible with WooCommerce, see FAQ of my plugin https://www.ads-software.com/plugins/woocommerce-de/faq/ –> Nr. 20

I guess this button comes from your theme — because in my translations it is included (as “Zur Kasse gehen”). If it comes from your theme, what I believe, then it needs own translation, THIS ONE should work with Codestyling plugin then ??

The helper functions doesn’t work here!

Since this string is filterable in WooCommerce, you have to try theme translation first, if not possible, use own templates (change hardcoded…) or maintain own plugin translations for WooCommerce.

Thanks, Dave ??

hi dave

thanks for the fast answer. i will ask the theme authors.
anyway: where do i have to put the “helper” file or code to work?

thanks,

chris

Hi Chris,

the code of the helper functions goes in your functions.php of the theme or child theme – but make backup of that file before!

And don’t copy the opening “<? php”, leave that out ??

This should help.

–Dave ??

Hi Chris,

Probably your theme use _e( 'Proceed to Checkout' ), while the .po file use Proceed to Checkout →.

Replace _e( 'Proceed to Checkout' ) with _e( 'Proceed to Checkout →' ) and it should work ??

@carloskk:
Issue already resolved ??

Regarding your suggestion: it may work if using WooCommerce 2.1.x with older, custom templates via your theme. But it is not recommended, as WooCommerce 2.1.x changed all strings with arrows markup to remove this markup which is good. So future proof way is to update your templates as well as translations. At least that’s my opinion based on experiences with clients… ??

Hi Dave,

same problem here:
‘Proceed to Checkout →’ is not translated.

As the domain of the _e function is ‘woocommerce’ I assume it should be translated by your plugin, or am I wrong?

<?php _e( 'Proceed to Checkout &rarr;', 'woocommerce' ); ?>

Thanks!

@wkrt:
The correct answer is already in my answer to the other user above ??

WooCommerce removed all “→” markup from strings therefore, my translations for WooCommerce 2.1.x will not work in this case.

Better change textdomain to that of your theme’s! And then translate the theme. This is more future proof!

Themes relying on the “woocommerce” textdomain do it wrong, as for the tiniest change in WooCommerce it will not work any longer.

Thanks, Dave ??