Navigating Product Option Translations in ESHOPMAN Admin: A Temporary Exclusion Explained

As an ESHOPMAN merchant or developer, managing translations for your product catalog is crucial for reaching a global audience. Recently, some users upgrading their ESHOPMAN instance, particularly to version 2.13.0, encountered an unexpected behavior when trying to translate ProductOption and ProductOptionValue entities within the ESHOPMAN Admin UI. While these entities were correctly activated for translation in the backend, they mysteriously disappeared from the main 'Settings -> Translations' list.

The Setup Context

The issue was observed in an ESHOPMAN setup utilizing Node.js v25.2.1 and PostgreSQL 18.1, with the following core ESHOPMAN dependencies:

{
  "name": "eshopman-starter",
  "version": "0.0.1",
  "dependencies": {
    "@eshopman/admin-sdk": "2.13.0",
    "@eshopman/cli": "2.13.0",
    "@eshopman/framework": "2.13.0",
    "@eshopman/js-sdk": "2.13.0",
    "@eshopman/eshopman": "2.13.0",
    "@eshopman/ui": "4.0.14",
    "@mikro-orm/core": "6.4.16",
    "@mikro-orm/postgresql": "6.4.16",
    "pg": "^8.13.0",
    "zod": "^3.23.8"
  }
}

The Challenge

A community member reported that after enabling the Translation Module and activating both ProductOption and ProductOptionValue entities in the 'Manage translatable entities' settings, they were marked as is_active: true in the translation_settings database table. However, the ESHOPMAN Admin's dynamic list generation for translatable entities failed to display them under Settings -> Translations. This meant that users couldn't easily access the translation interface for these critical product attributes, leading to potential confusion and workflow disruption.

The Workaround

Fortunately, the same community member discovered a clever workaround: the translation bulk editor pages for these entities do exist and function perfectly when accessed directly via their specific URLs. This indicated that the backend registration was sound, and the issue resided solely in the Admin UI's display logic. For those needing to translate these entities immediately, you can use these direct paths in your ESHOPMAN Admin URL:

/app/settings/translations/edit?reference=product_option
/app/settings/translations/edit?reference=product_option_value

The ESHOPMAN Team's Clarification

The ESHOPMAN development team quickly addressed this report, clarifying that this wasn't a bug in the traditional sense, but an intentional, temporary exclusion. The ProductOption and ProductOptionValue relations were explicitly excluded from the main translation list because a significant rework of ESHOPMAN's product options feature is currently underway. This proactive measure aims to prevent complex and potentially difficult migrations for users in the near future, ensuring a smoother transition when the new product option architecture is rolled out.

What This Means for ESHOPMAN Users

This insight highlights ESHOPMAN's commitment to a robust and future-proof platform. While it might cause a minor inconvenience in the short term, the decision to temporarily exclude these entities is a strategic move to safeguard your data and simplify future upgrades. It's a testament to the platform's thoughtful approach to development, prioritizing stability and ease of migration during significant feature enhancements. For now, the direct URL workaround provides a functional path for managing these translations.

Staying Informed

As ESHOPMAN continues to evolve, especially with its seamless integration into HubSpot for storefront management and CMS deployment, staying informed about platform updates and community discussions is vital. Keep an eye on official ESHOPMAN announcements for details on the upcoming product option rework and when these entities will be fully re-integrated into the main translation interface.