Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-4504

Task defaults are evaluated at the wrong place in import process

    • Critical
    • Hide
      translate5 - 7.20.5: FIX: Event-Handling on import may leads to import-options not being processed or being processed to late
      translate5 - 7.20.6: Fix for problem when plugin is not active
      Show
      translate5 - 7.20.5: FIX: Event-Handling on import may leads to import-options not being processed or being processed to late translate5 - 7.20.6: Fix for problem when plugin is not active

      problem

      We have 4 Major Import start points:

      • ImportService::import
      • ImportService::importSingleTask
      • WorldServer connector
      • plunet connector

      In all 4 places the defaults are evaluated at different points, and at the wrong place.

      Defaults must be evaluated after task preparation and before worker queuing.

      This must be unified and fixed.

      Due hotfixes in that area, we had the following problems: no pre-translation for language resources added by default. Using Terminology in this context, this triggered duplicate key errors due task meta usage

      Therefore we have to test

      • Proper Import and defaults usage (users / generated workflow step out of assigned users / pre-translation as mentioned from TM / MT / Terminology)
      • Im in all available Import ways:
        • Manually
        • via API (task type default)
        • Across Hotfolder
        • PlunetConnector
        • WorldserverConnector

      Best would be to have integrations tests for all of that, testing the defaults and pre-translation.

      Currently there is probably no test testing the pre-translation triggered by task defaults.

        •  

          [TRANSLATE-4504] Task defaults are evaluated at the wrong place in import process

          There are no comments yet on this issue.

            axelbecher Axel Becher
            tlauria Thomas Lauria
            Sanya Mikhliaiev, Stephan Bergmann
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: