Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Development
  3. Untranslatable "Tool" menu items in Infrastructure (hard-coded in database)

Untranslatable "Tool" menu items in Infrastructure (hard-coded in database)

Scheduled Pinned Locked Moved Development
2 Posts 2 Posters 86.1k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C
    C
    cold
    wrote on last edited by
    #1

    Description:
    When attempting to localize/translate the NetXMS interface, I noticed that the items under the "Tools" menu for Infrastructure objects cannot be translated.

    Upon further investigation, it appears these strings are hard-coded in the database under the `object_tools.tool_name` column, rather than being routed through the standard localization resource files.

    NetXMS Version: 6.1.1
    Operating System / Environment: Linux (Docker) [Server] / macOS [Client]

    Steps to Reproduce:

    1. Configure the NetXMS console/WebUI to use a translated language profile.
    2. Navigate to the Infrastructure tree.
    3. Select on a node or object and navigate to the Tools context menu.
    4. Observe the language of the tool names.

    Expected Behavior:
    The names of the tools should support localization, either by mapping the database entries to localization keys or by allowing translations to be defined within the object tool configuration itself.

    Actual Behavior:
    The tool names are pulled directly from `object_tools.tool_name` in the database, bypassing the UI translation mechanism and forcing them to display in their original string format regardless of the user's language settings.

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      That's due to user-configurable tool nature. If all system users use same language, you can just change tool names in server configuration. However, if different language must be supported currently there is no solution. I've registered issue in our tracker for adding localization support to object tools:
      https://github.com/netxms/netxms/issues/3243

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups