Hi, great module.

Is there a plan for multi-language options?

Do you have suggestions for translating the custom paths for a checkout page?

Comments

Cezar created an issue. See original summary.

Cezar’s picture

Title: Translate the custom paths for a checkout page » Translate custom paths for a checkout page
valentine94’s picture

Version: 7.x-1.4 » 7.x-1.x-dev

Hi Cezar.

Thanks for the request. Could you describe in more detail what specially you mean?

Thanks.

Cezar’s picture

For a multi-language site I want to translate the checkout paths for each language.

Something like:
/en/shop/details
/de/kaufhaus/beiwerk
/fr/boutique/renseignements

valentine94’s picture

Status: Active » Needs work

Hmm...sounds like a good idea.

Let's discuss here how it would be better to implement in back-end and admin UI things.

valentine94’s picture

Probably we should create a some sub-module for this feature, because this functionality can be isn't required for somebody.

Cezar’s picture

Maybe it could be integrated with Variable which is by default compatible with Internationalization that has a variable translation (i18n_variable) sub-module.

This way there would not be necessary a sub-module for Commerce Checkout Paths neither any admin UI things and the multilingual options would be silently optional. You just make the variables aware of translations in variable translation admin UI.

valentine94’s picture

Sounds good. Did you've tested this solution?

Cezar’s picture

I've used variable translation on all my multi-language sites but I have not done any module development involving the Variable API.

_shy’s picture

Status: Needs work » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Everyone can apply the patch above (not tested by the maintainers, tested by the community) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.