Rename from OpenTM2 to t5memory in UI

XMLWordPrintable

    • Critical
    • Hide
      For API using clients: When creating T5memory language resources via API from now on the serviceType must be editor_Services_T5Memory. Same for the resourceId. Currently opentm2 values are converted automatically to t5memory and warning is logged - so old styled calls should still work
      Show
      For API using clients: When creating T5memory language resources via API from now on the serviceType must be editor_Services_T5Memory. Same for the resourceId. Currently opentm2 values are converted automatically to t5memory and warning is logged - so old styled calls should still work
    • Hide
      7.33.2: convert the serviceType OpenTM2 automatically to T5Memory and create deprecation warning into the log when creating language resources via API and use old serviceType name
      7.33.0: Rename OpenTM2 to T5Memory
      Show
      7.33.2: convert the serviceType OpenTM2 automatically to T5Memory and create deprecation warning into the log when creating language resources via API and use old serviceType name 7.33.0: Rename OpenTM2 to T5Memory

      Problem

      OpenTM2 is simply a wrong name meanwhile because of all the rework and new functionality done in the last 5 years.

      We need to rename it in the UI to t5memory, as it is called under the hood since years.

      Solution

      Just do it. But only for UI-texts. Class-names in code stay for now, as effort and risk would be to big. This will be done with moving code to postgres.

       

            Assignee:
            Sanya Mikhliaiev
            Reporter:
            Marc Mittag [Administrator]
            Leon Kiz
            Stephan Bergmann, Sylvia Schumacher
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: