Hi,

I prepared a small patch for J2Commerce that improves the translation of language constants used for product filters and product options in the administrator panel.
Currently, these values can be translated correctly on the frontend, but in the administrator panel they are displayed as raw language keys, for example MATERIAL_BRASS instead of the translated label. This makes product editing less convenient in multilingual stores.
The patch applies Joomla language translation in the backend, without changing the original values stored in the database. The technical keys remain unchanged, so existing product data, imports, exports, CSV workflows and integrations should not be affected.

The translation was applied in the following administrator views:

- view=filtergroups
- view=options
- view=products
- view=article, for product filters and product options

After applying the patch, the administrator interface follows the selected backend language and displays translated labels for filter and option variables.
The package also includes a comparison list showing the modified files and changes, so the patch can be reviewed more easily.
Please consider adding this improvement to J2Commerce core.

https://piekielko.com/download/j2commerce-661-filters-and-options-patch.zip

best regards,
Chris / KK

Hi Adam,

Sure — Falang setup with J2Commerce v6 is actually quite straightforward.

Since J2Commerce products are based on Joomla articles/content, Falang can translate the main product content without any real problems. For basic article and product description translations, the free version of Falang should be enough.

That said, I would personally recommend the Basic version, because it gives access to translation assistance using available AI/translation services such as DeepL and other supported engines. This makes the workflow much faster, especially when translating many products.

You can download Falang here:
https://www.faboba.com/en/composants/falang/donwload.html

The basic documentation is available here:
https://www.faboba.com/en/composants/falang/documentation.html

In practice, the setup is simple: install the full Falang package; configure your site languages; enable the required Falang plugins/modules; use Falang instead of Joomla’s standard multilingual content system; translate product articles, categories, tags, menu items and meta descriptions from the Falang interface; when using translation assistance, select the fields you want to translate and apply the translation tool.

One important thing to remember: Falang does not translate J2Commerce custom fields automatically. For custom store fields, it is better to use Joomla language constants/overrides.

Best,
Krzysztof

Falang may seem a little difficult at first, mainly because you need to configure everything properly at the beginning. But honestly, it is definitely not as difficult as configuring and understanding the store itself — so I am sure you will manage it without any problem. Once it is set up, it is actually a very convenient translation system. Joomla’s native multilingual system, on the other hand, is a total mess in my opinion — for me, it has always been a bit of a nightmare... ;-)

Thank you for the suggestion. A GitHub PR is definitely the correct way to submit language strings, but I am not able to prepare it properly at the moment.

My store is already running in production and making sales, but during the launch and early production use I ran into quite a lot of issues, including payment-related problems connected with multilingual use.

The main issue in my case was the Stripe payment flow. When customers used a language different from the site’s default language, the payment process did not behave consistently. Some Stripe payment options were displayed in the wrong language, and in some cases the payment was not correctly linked back to the J2Commerce order during finalization.

Right now my time is focused on fixing these issues quickly, so customers do not see those bugs in the live store. After my local fixes, the shop currently works in a multilingual setup, including payments, but the modifications are quite extensive.

Because of that, I cannot simply prepare a clean PR immediately. My changes may not align directly with what you are currently working on upstream. When a new J2Commerce version is released, I will need to compare it carefully with my local changes to make sure I do not overwrite the fixes I have already made in my production store.

So yes, I understand the value of contributing through GitHub, but for now my priority is keeping the live shop stable and working correctly for customers. Once things settle down, I may be able to review the changes properly and see what can be contributed back in a clean way.

KK